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
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
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
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
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
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
