Am 14.01.2020 um 22:41 schrieb Jonas Schäfer:
This message constitutes notice of a Last Call for comments on XEP-0363. The
Last Call was restarted after the Council election, because the previous
Council did not vote on the ongoing LC.
Title: HTTP File Upload
Abstract:
This specification
14 Jan 2020 10:41:23 pm Jonas Schäfer :
> This message constitutes notice of a Last Call for comments on XEP-0363. The
> Last Call was restarted after the Council election, because the previous
> Council did not vote on the ongoing LC.
>
> Title: HTTP File Upload
> Abstract:
> This
On Tue, 14 Jan 2020 at 21:41, Jonas Schäfer wrote:
> This message constitutes notice of a Last Call for comments on XEP-0363.
> The
> Last Call was restarted after the Council election, because the previous
> Council did not vote on the ongoing LC.
>
> Title: HTTP File Upload
> Abstract:
> This
* Jonas Schäfer [2020-01-14 22:41]:
> 1. Is this specification needed to fill gaps in the XMPP protocol
> stack or to clarify an existing protocol?
As far as I can see, it's currently our only solution for media sharing
that works reliably with offline recipients, multiple devices, and group
On Tue, 14 Jan 2020 at 22:42, Jonas Schäfer wrote:
> This message constitutes notice of a Last Call for comments on XEP-0363.
> The
> Last Call was restarted after the Council election, because the previous
> Council did not vote on the ongoing LC.
>
> Title: HTTP File Upload
> Abstract:
> This
The previous last call for this was mostly ignored; which I’m
interpreting as most people are generally happy with this XEP. However
for due process I think we need to collect some feedback so let me
start with mine.
Am Di., 14. Jan. 2020 um 21:43 Uhr schrieb Jonas Schäfer :
> 1. Is this
This message constitutes notice of a Last Call for comments on XEP-0363. The
Last Call was restarted after the Council election, because the previous
Council did not vote on the ongoing LC.
Title: HTTP File Upload
Abstract:
This specification defines a protocol to request permissions from
This message constitutes notice of a Last Call for comments on
XEP-0363.
Title: HTTP File Upload
Abstract:
This specification defines a protocol to request permissions from
another entity to upload a file to a specific path on an HTTP server
and at the same time receive a URL from which that file
Hi,
I'm developer of Salut à Toi and HTTP Upload is implemented there, here are
my feedbacks:
> 1. Is this specification needed to fill gaps in the XMPP protocol
> stack or to clarify an existing protocol?
Well it's hard to answer. I would say no because Jingle is already doing
that in a
This message constitutes notice of a Last Call for comments on
XEP-0363.
Title: HTTP File Upload
Abstract:
This specification defines a protocol to request permissions from
another entity to upload a file to a specific path on an HTTP server
and at the same time receive a URL from which that file
Re-reading this and other feedback, I'm going to push back on moving
this to Draft until substantial improvements are done to Security
Considerations in particular, and normative language use in general.
On 12 December 2017 at 11:07, Dave Cridland wrote:
> On 11 December 2017
On Tue, Dec 12, 2017, at 15:49, Ruslan N. Marchenko wrote:
> Yes, I don't like the approach with wide open PUT limited by certain
> high-level content constraints and (luckily) headers in the latest
> revision.
> At least content hash (as in jingle) would be beneficial. Shall we say
> slot path
On 29.11.2017 20:16, Jonas Wielicki (XSF Editor) wrote:
This message constitutes notice of a Last Call for comments on
XEP-0363.
Title: HTTP File Upload
Abstract:
This specification defines a protocol to request permissions from
another entity to upload a file to a specific path on an HTTP
On 29 November 2017 at 20:16, Jonas Wielicki wrote:
> This message constitutes notice of a Last Call for comments on
> XEP-0363.
>
> Title: HTTP File Upload
> Abstract:
> This specification defines a protocol to request permissions from
> another entity to upload a file to a
On 11 December 2017 at 20:15, Kevin Smith wrote:
> On 29 Nov 2017, at 19:16, Jonas Wielicki (XSF Editor)
> wrote:
>> This message constitutes notice of a Last Call for comments on
>> XEP-0363.
>>
>> Title: HTTP File Upload
>> Abstract:
>> This
On 12 December 2017 at 09:10, Daniel Gultsch wrote:
> 2017-12-11 21:15 GMT+01:00 Kevin Smith :
>> On 29 Nov 2017, at 19:16, Jonas Wielicki (XSF Editor)
>> wrote:
>>> 4. Do you have any security concerns related to this
2017-12-11 21:15 GMT+01:00 Kevin Smith :
> On 29 Nov 2017, at 19:16, Jonas Wielicki (XSF Editor)
> wrote:
>> 4. Do you have any security concerns related to this specification?
>
> Should probably mention that you’re going to be handing out your IP to
On 29 Nov 2017, at 19:16, Jonas Wielicki (XSF Editor)
wrote:
> This message constitutes notice of a Last Call for comments on
> XEP-0363.
>
> Title: HTTP File Upload
> Abstract:
> This specification defines a protocol to request permissions from
> another entity to upload a
This message constitutes notice of a Last Call for comments on
XEP-0363.
Title: HTTP File Upload
Abstract:
This specification defines a protocol to request permissions from
another entity to upload a file to a specific path on an HTTP server
and at the same time receive a URL from which that file
19 matches
Mail list logo