Re: [Standards] Call for Experience: XEP-0363: HTTP File Upload
I think there are two questions hidden in this: 1. what mechanism should be used for transferring URIs (of uploaded files)? 2. should 0363 require that the mechanism in 1 be used? The current de facto mechanism appears to be OOB, but that can (and should) change in the future, so it should be left open, but there's also nothing wrong with outlining what's currently in use. HTTP File Upload is a general mechanism for obtaining a URI to an uploaded file, which can then be used for 'something' - currently, the most common case is to transfer a file from one user to another (possibly multiple), but that's not to say it couldn't find other uses. A future XEP might upload one or more files and then make them available through its own wrapping (e.g. a gallery of photos), so requiring that each URI is transferred separately or with a particular mechanism seems limiting and inflexible. Some guidance on the current best practice is probably a good thing though (Informational XEP?) ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
Re: [Standards] Call for Experience: XEP-0363: HTTP File Upload
Am Mittwoch, den 21.10.2020, 16:28 +0100 schrieb Dave Cridland: > > This specification is primarily intended for, and used for, the > purpose of transferring a file from one user to another. > > In practise, the clients upload a file, thereby obtaining a URL, and > pass that URL somehow to the other party. > > My question - and it is a question - is whether we ought to be > advancing this specification when its usage is contingent on the > proper definition of that "somehow". > > I can see arguments both ways - this can be used independently, after > all, but it's primary use is as part of the "complete breakfast" of > file transfer. Advancing something to Final which is habitually only > used with a somewhat undocumented use of OOB (XEP-0066) feels a bit > wrong, but there's technically nothing incorrect by process in doing > so. > > So what do we feel as a group? I was going to raise similar question, even drafted the response. because I've seen this challenge while implementing client side. But then re-read the spec, thought it over again, and removed the question. Because it has nothing to do with this spec. It's more to OOB itself. --rr ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
Re: [Standards] Call for Experience: XEP-0363: HTTP File Upload
Personally I think it's correct as is. I don't like the current way most clients I've used send images (OOB and the URL in the body) and in my own clients I wouldn't want to do that because I personally expect to be able to send a separate message along with an image like most commercial messengers, MMS, etc. let you do. Since this wouldn't cause problems if I do it slightly different from Conversations, I don't think it's worth specifying (other than maybe mentioning that OOB is the current widely used option but that this might change in the future). —Sam On Wed, Oct 21, 2020, at 11:28, Dave Cridland wrote: > > > On Tue, 20 Oct 2020 at 15:33, Jonas Schäfer > wrote: > > If you have any comments about advancing XEP-0363 from Draft to > > Final, please provide them by the close of business on 2020-11-03. > > After the Call for Experience, this XEP might undergo revisions to > > address feedback received, after which it will be presented to the > > XMPP Council for voting to a status of Final. > > This specification is primarily intended for, and used for, the > purpose of transferring a file from one user to another. > > In practise, the clients upload a file, thereby obtaining a URL, and > pass that URL somehow to the other party. > > My question - and it is a question - is whether we ought to be > advancing this specification when its usage is contingent on the > proper definition of that "somehow". > > I can see arguments both ways - this can be used independently, > after all, but it's primary use is as part of the "complete > breakfast" of file transfer. Advancing something to Final which is > habitually only used with a somewhat undocumented use of OOB (XEP- > 0066) feels a bit wrong, but there's technically nothing incorrect > by process in doing so. > > So what do we feel as a group? > > Dave. > ___ > Standards mailing list Info: > https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: Standards- > unsubscr...@xmpp.org > ___ > -- Sam Whited ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
Re: [Standards] Call for Experience: XEP-0363: HTTP File Upload
On Tue, 20 Oct 2020 at 15:33, Jonas Schäfer wrote: > If you have any comments about advancing XEP-0363 from Draft to Final, > please provide them by the close of business on 2020-11-03. After the > Call for Experience, this XEP might undergo revisions to address > feedback received, after which it will be presented to the XMPP > Council for voting to a status of Final. > This specification is primarily intended for, and used for, the purpose of transferring a file from one user to another. In practise, the clients upload a file, thereby obtaining a URL, and pass that URL somehow to the other party. My question - and it is a question - is whether we ought to be advancing this specification when its usage is contingent on the proper definition of that "somehow". I can see arguments both ways - this can be used independently, after all, but it's primary use is as part of the "complete breakfast" of file transfer. Advancing something to Final which is habitually only used with a somewhat undocumented use of OOB (XEP-0066) feels a bit wrong, but there's technically nothing incorrect by process in doing so. So what do we feel as a group? Dave. ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
Re: [Standards] Call for Experience: XEP-0363: HTTP File Upload
Am Dienstag, den 20.10.2020, 14:31 + schrieb Jonas Schäfer: > The XEP Editor would like to Call for Experience with XEP-0363 before > presenting it to the Council for advancing it to Final status. > > > During the Call for Experience, please answer the following > questions: > > 1. What software has XEP-0363 implemented? Please note that the > protocol must be implemented in at least two separate codebases (at > least one of which must be free or open-source software) in order to > advance from Draft to Final. > libpurple plugin (client): https://github.com/Junker/purple-xmpp-http-upload (by Dmitry Kosenkov) djabberd plugin (server): https://github.com/rufferson/DJabberd-Plugin-HTTPUpload > 2. Have developers experienced any problems with the protocol as > defined in XEP-0363? If so, please describe the problems and, if > possible, suggested solutions. No > > 3. Is the text of XEP-0363 clear and unambiguous? Are more examples > needed? Is the conformance language (MAY/SHOULD/MUST) appropriate? > Have developers found the text confusing at all? Please describe any > suggestions you have for improving the text. There's one sentence which is a bit ambiguous: > Implementors should keep in mind, that without additional end-to-end- > encryption, files uploaded to a service described in this document > may be stored in plain text. Not quite clear what it tries to say, perhaps that file will be *transferred* in a _plain text_ (unencrypted)? As end-to-end encryption (https) has little impact on how the file is stored. > If you have any comments about advancing XEP-0363 from Draft to > Final, > please provide them by the close of business on 2020-11-03. After the > Call for Experience, this XEP might undergo revisions to address > feedback received, after which it will be presented to the XMPP > Council for voting to a status of Final. > > > You can review the specification here: > > https://xmpp.org/extensions/xep-0363.html > > Please send all feedback to the standards@xmpp.org discussion list. > ___ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > ___ > ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
[Standards] Call for Experience: XEP-0363: HTTP File Upload
The XEP Editor would like to Call for Experience with XEP-0363 before presenting it to the Council for advancing it to Final status. During the Call for Experience, please answer the following questions: 1. What software has XEP-0363 implemented? Please note that the protocol must be implemented in at least two separate codebases (at least one of which must be free or open-source software) in order to advance from Draft to Final. 2. Have developers experienced any problems with the protocol as defined in XEP-0363? If so, please describe the problems and, if possible, suggested solutions. 3. Is the text of XEP-0363 clear and unambiguous? Are more examples needed? Is the conformance language (MAY/SHOULD/MUST) appropriate? Have developers found the text confusing at all? Please describe any suggestions you have for improving the text. If you have any comments about advancing XEP-0363 from Draft to Final, please provide them by the close of business on 2020-11-03. After the Call for Experience, this XEP might undergo revisions to address feedback received, after which it will be presented to the XMPP Council for voting to a status of Final. You can review the specification here: https://xmpp.org/extensions/xep-0363.html Please send all feedback to the standards@xmpp.org discussion list. ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
