Google defends dropping chat federation with inaccurate comments
Unfortunately, the guy responds with his own misinformations.<p>Google said: "For example, mobile has several requirements around bandwidth and battery that are simply not part of the standard"<p>He says: "This glances over the the fact that the X in XMPP stands for eXtensible, which still results in proposals for new protocol extensions every month."<p>His misinformation is this: XMPP is XML based. The bandwidth that Google most likely refers to is a result of verbosity of XML. You can't eliminate that by extending XMPP, something that a guy who serves on XMPP Council should know.<p>The only way to fix that specific problem is to change the protocol. Which is what Google did.<p>This is an example a bad advocacy: badmouthing companies that decided to no longer use something you work on.<p>I also find troubling the pounding Google gets for every little mis-step.<p>When it comes to using and promoting open technologies Google is seemingly from another planet compared to other tech giants (Apple, Microsoft, Facebook, Amazon, you name it).<p>And yet the furor is not about Microsoft using completely secret protocol (Skype), not about Apple promising to publish their secret protocol (Facetime) and then not doing it, not about Apple preventing fair browser competition in iOS etc. but about Google no longer using XMPP.<p>A lack of perspective.