Hi, I think there is some confusion about the use of 0066. We do not communicate that an image should be shown inline. It is a hacky way of communicating that the URL links to a file that was specifically uploaded by a user, or a user wants to share.
This is so clients can differentiate between random links a user found on the internet and posts into a chat and uploaded content from the user. The first could lead to users accidentally sending dangerous files to their contacts if we automatically download it and show it inline. So we add a oob tag to the message to tell other clients this file was uploaded by the user (or a deliberate action to share some content) and not some copy paste link. If the client acts on this information differently is up to the client. So because we make uploads known with 0066 (Which is what this XEP is for to deliberately share a URL), we have to also think about clients not supporting 0066 and that leads to putting the url also into the body. 385 adds more metadata than 0066, but other than that it does exactly the same. regards Philipp Am Do., 7. März 2019 um 08:07 Uhr schrieb Timothée Jaussoin < [email protected]>: > What about using a proper XEP like SIMS ( > https://xmpp.org/extensions/xep-0385.html) for that case? > > This look like a hack to me. >
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
