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

On 03.07.21 20:35, JC Brand wrote: > If you're behind a corporate firewall, [...] I was rather thinking of company internal servers that are only reachable from within the local network. > Given that users already share URLs, I would like to have better > metadata so that I can provide a better

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

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

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

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

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

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

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

On Fri, Jul 2, 2021 at 1:22 PM Florian Schmaus wrote: > On 02.07.21 12:15, JC Brand wrote: > > So, my proposal is that XEP-0385 be updated so that the XEP-0300 hash > > requirement gets relaxed to a SHOULD > > +1. I would even make the hash OPTIONAL as SHOULD is already pretty strong. > > I'd be

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

Am 2. Juli 2021 13:41:26 MESZ schrieb Tobias Markmann : >On Fri, Jul 2, 2021 at 1:22 PM Florian Schmaus >wrote: > >> On 02.07.21 12:15, JC Brand wrote: >> > So, my proposal is that XEP-0385 be updated so that the XEP-0300 >hash >> > requirement gets relaxed to a SHOULD >> >> +1. I would even

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

On 02.07.21 12:15, JC Brand wrote: > So, my proposal is that XEP-0385 be updated so that the XEP-0300 hash > requirement gets relaxed to a SHOULD +1. I would even make the hash OPTIONAL as SHOULD is already pretty strong. > and that the inclusion of the Etag > header be documented as an

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

Sorry, I see now that Thunderbird has completely mangled the stanza that it showed so nicely to me in the email editor. I guess because I have it configured to send out only plaintext. Here it is again:     Look at this funny cat picture     type='data'>                                    

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

On 02.07.21 12:42, Sergey Ilinykh wrote: What about a slightly different scenario? Romeo sees a funny picture on funnypics.com , copies it to a messenger's input field. The messenger prefetches the whole picture, generates a thumbnail (at least it's impossible to have

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

What about a slightly different scenario? Romeo sees a funny picture on funnypics.com, copies it to a messenger's input field. The messenger prefetches the whole picture, generates a thumbnail (at least it's impossible to have a thumbnail without fetching everything), computes hashes and then

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

Hi everyone I've been reading XEP-0385 SIMS with an eye towards potentially implementing it, when I noticed that a XEP-0300 hash is required, in order to allow integrity checking and caching. In the introduction of SIMS, the following is written: "This proposal aims to provide a protocol