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 UX. I was under the assumption that SIMS is not about adding metadata, but about displaying media inline. Sharing an URL to a (media) file does not imply that it should be displayed inline. >> Fetching files from untrusted third-party servers is a privacy >> nightmare. [...] > Sounds like configuration, and not something that would ever be universal. I think this is something we should make an effort to solve, not just with configuration, but at the protocol level. "By using this software, you agree that your personal data (IP address) is shared with arbitrary unknown third parties, who, under their respective privacy policy, may process that personal data as they please" doesn't really sound great. We already have an issue here and I'm not very keen to make it even bigger. > Also, at least in my web client, the images are shown asynchronously > after the message has been sent, and they're shown via <img> tags, so > the browser is responsible for fetching the image and caching it, not my > client. Just to get the message across: I am not against lifting the requirement to have the file hash in here, I just fear the UX this might result in. I totally understand that as a web client you may not be able to actually fetch and compute the hash of the media due to cross-origin restrictions - however the same probably applies to HTTP headers. Web currently is in the process of receiving a proper system for sharing files across apps (both web and native). See https://web.dev/web-share-target/. This currently is not available on most Desktop OS, just because those OS don't have a proper system yet (whereas mobile OS are typically much more modern and thus do support such system). Also, I kinda feel that we are talking about users with different expertise levels here: I'm thinking of the people that ask to search an event on Facebook rather than sending a link to the Facebook event page. I also hardly see video files being linked directly outside my tech bubble (instead links are to YouTube, Dropbox or Google Drive with their web video player). But, I also agree that, especially within tech people, sharing an URL is common, thus what you propose may make sense for those. Marvin _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
