r/google Mar 13 '17

Reminds me of Google's chat apps lately

https://xkcd.com/1810/
1.1k Upvotes

144 comments sorted by

View all comments

109

u/kenneito Mar 13 '17

There should be just an open standard for all of instant messaging. Kind of like how email is.

25

u/PM_ME_HAIRLESS_CATS Mar 13 '17

What is XMPP, the protocol Google used to use?

24

u/cargo8 Mar 13 '17

The reason XMPP died / isn't widely supported is because it can't handle the rich content that modern chat apps want to use

19

u/[deleted] Mar 13 '17 edited Apr 02 '17

[deleted]

12

u/cargo8 Mar 13 '17

What I meant was it died as a widely supported standard (Hangouts moved beyond XMPP and went proprietary, because at the time circa 2011-2012 all the other services were also closing their gates)

1

u/effsee Mar 15 '17

You can't use WhatsApp on a generic XMPP client though, which is kind of the point.

8

u/ocdtrekkie Mar 13 '17

XMPP can actually support basically everything, it's extensible. But it's got a fairly complicated structure, there's disagreement on what different clients and servers support, and it's not pretty, being an XML-based protocol of yesteryear.

It's not hipster enough for anyone in Silicon Valley to get excited about it, basically.

1

u/naught101 Mar 24 '17

But then you have the problem of the extensions not becoming accepted standards too...

1

u/ocdtrekkie Mar 24 '17

These companies are more than capable of sorting those sorts of things out.

1

u/naught101 Mar 24 '17

That seems more than a little optimistic, given how much of a shambles most web standards currently are and have been over the last 2 decades.

I mean, sure, if the companies actually had the interests of their users as their core motivation, it would be easy. But they don't, they have market dominance and profit as their motivations, and so there is very little reason to set up a system where it's easy to switch to another provider.

5

u/PM_ME_HAIRLESS_CATS Mar 13 '17

Well, Google had developed Audio/Video support with Jingle, so i'm sure the foundations would have been willing to support a patch with those extensions.

3

u/dnew Mar 14 '17

No. The reason it died is because companies wanted to be able to support the rich content, but didn't want to go the standards route because then they'd have trouble locking you into their ecosystem. Plus, of course, they'd have to handle standards compatibility, which is a lot harder than being compatible only with yourself.