Great episode, guys.
The thing with images in XMPP is that clients and servers are doing things in completely non-standard ways anyway. I’ve experimented with a lot of combinations of XMPP clients and servers and the conclusion is that you never know whether the other party has received the embedded image or not. For example, try sending an embedded image from Conversations to Psi+ or Gajim and it won’t work at all. Gajim will show you the link to the location the image is stored in, but Psi+ fails silently. Add OTR or OpenPGP for E2E encryption into the mix and everything breaks in million pieces. One of the nastiest clients is Zom, a “user-friendly” version of ChatSecure, which implements Telegram-like stickers which only can be understood by Zom, of course. Sometimes these things don’t even work when two parties are using the exact same client but have their accounts on different servers, usually because of how each server is configured. So I wouldn’t expect Google to do anything to fix compatibility between their proprietary XMPP server and stock XMPP clients when not even real XMPP servers and clients understand each other.
And now onto a small thought about XMPP. XMPP is for sure the best protocol for IM out there and the proof is that everyone is building their own proprietary IM protocols on top of XMPP, but its descentralized nature produces a lot of problems that you really don’t want to happen in your communicate with people. That’s why Telegram has become so popular: the fact that the server is centralized and closed has made its adoption very, very easy. Yes, there are third-party clients, besides the official ones, but you have one single server you must be sure your client talks correctly to.
I want to wish @bryanlunduke’s activist action will be helpful… Let’s cross fingers…
(BTW, I want you to talk about hamburgers… There’s this Brazilian hamburgers place here in the neighborhood I live in in Barcelona and you’ve made me want go buy one of their AMAZING burgers).