Re: [Standards] Thoughts on XEP-0385 Stateless Inline Media Sharing

2021-07-03 Thread JC Brand
On 03.07.21 17:44, Linus Jahn wrote: Hello, I just wanted to note that there's also XEP-0447: Stateless file sharing [1] which has some improvements over SIMS (like multiple files in one message and a little simpler API (no need to use character counting / the References XEP) and later

Re: [Standards] Thoughts on XEP-0385 Stateless Inline Media Sharing

2021-07-03 Thread JC Brand
Hi Marvin On 03.07.21 17:01, Marvin W wrote: Hi, Remember that URLs are not guaranteed to be globally reachable (examples: restricted to company network or requiring authentication). For most users it's not easily understandable if a URL can be reached by the recipient client or not. Thus

Re: [Standards] Thoughts on XEP-0385 Stateless Inline Media Sharing

2021-07-03 Thread Marvin W
Hi, XEP-0447 currently lacks a content-disposition information to clarify if a (media) file should be displayed inline or not. This is on my TODO. XEP-0447 does not allow for mixed content which XEP-0385 supports. Including the hash is already "only" RECOMMENDED for XEP-0447. However it is

Re: [Standards] Thoughts on XEP-0385 Stateless Inline Media Sharing

2021-07-03 Thread Linus Jahn
Hello, I just wanted to note that there's also XEP-0447: Stateless file sharing [1] which has some improvements over SIMS (like multiple files in one message and a little simpler API (no need to use character counting / the References XEP) and later attaching of additional sources). Not sure

Re: [Standards] Thoughts on XEP-0385 Stateless Inline Media Sharing

2021-07-03 Thread Marvin W
Hi, Remember that URLs are not guaranteed to be globally reachable (examples: restricted to company network or requiring authentication). For most users it's not easily understandable if a URL can be reached by the recipient client or not. Thus sending an URL of funnypics.com instead of