5 ms·
It amazes me how many people think that ending GChat/XMPP federation was the result of some kind of cigar smoking, moustache-twirling "evil". I worked at Googl
by mike_hearn 10y ago
It amazes me how many people think that ending GChat/XMPP federation was the result of some kind of cigar smoking, moustache-twirling "evil".
I worked at Google at the time. It was killed for engineering reasons, that boiled down to:
1. Nobody used federation.
2. Except spammers. They used it a lot. Trying to keep federation alive whilst fighting spammers took a lot of effort.
3. It complicated the code a lot. Features that existed in GChat but didn't map well to XMPP were harder to implement.
4. The XMPP protocol sucked on mobile and sucked in web clients, and therefore Google's own clients were not using it any more. New extensions like Jingle were more like entirely separate protocols than small upgrades.
Federated chat protocols are the sort of thing that intuitively sound nice, but networks that implement them inevitably end up being killed off by closed, proprietary competitors that are simply a whole lot better. Email hangs on, kinda, but I passively await the day that the email system is killed off by a closed network. It already happened for personal correspondence (facebook) and I'm sure at some point it'll happen for work correspondence too.
Moxie Marlinspike has written some thoughts on why federated protocols are yesterday's solution here:
https://whispersystems.org/blog/the-ecosystem-is-moving/ https://whispersystems.org/blog/the-ecosystem-is-moving/
Put simply, in a world where clients are all free and the identifier of choice is the phone number, federation doesn't add much value.
- herbst 10y agoI may live in a nerd specific environment but gchat was our goto product for a long while. We had our notifications build in trough XMPP just like people do with slack now. Some of us used their own XMPP servers, and pretty much everyone was reachable trough it beeing google and everybody having a gmail and/or android phone at least. There were also several cool mobile and web apps that worked very well for XMPP, though not with high load thats true. When you removed XMPP and forced to hangout it died off pretty fast, no API and the Hangout thingy was not even working on Linux (not sure if it does these days, i never tried). I see your points, but i cant stop to think about this as the probably most evil step google did to my workflow. Edit:// I use hangout now to transport links from phone to desktop and the other way around. It totally lost its purpose :/
- cm3 10y ago> It already happened for personal correspondence (facebook) and I'm sure at some point it'll happen for work correspondence too. I don't know the numbers but I'm part of the population that never used Facebook, so I'm unconvinced you can generalize like that. > Put simply, in a world where clients are all free and the identifier of choice is the phone number, federation doesn't add much value. I didn't really understand Moxie's arguments, but he may know more due to the projects he's involved in. But how is interoperability achieved? The beauty of HTTP, NNTP and SMTP are that you're not bound to one (or maybe two) client experiences or server implementations. I don't understand the desire to leave achievements like that on the floor just for temporary comfort. It's a slippery slope and will lead us into a long time of silo'd communication. To me the current proposals look like if I had to use 4 different post offices depending on whom I want to send a package to. There's a reason addresses are universal.
- mike_hearn 10y agoMoxie's argument is that interop takes place at the level of the operating system's notification tray. If you want to make a better WhatsApp, all you have to do is ... build a better app. The traditional obstacles are largely gone in the mobile world: • You can access the same social graph just by requesting the contacts permission on your mobile phone: it's not like Facebook where the social network is locked away. • You don't have to go through some slow moving standards process which takes years to get the features into the most widely used clients like you would if trying to improve XMPP. • There's no cost to the user having multiple messaging apps installed thanks to Google/Apple's push networks: it's not like Windows/MacOS/Linux where having an app running in the background uses resources and requires permanent on-screen reminders of the resource wastage. So it's easy to get the user to set up your app. • Notifications will appear in the same place the user is looking for them no matter what. • You can (on Android) register for the right intents and whenever a friends phone number is invoked, your app will be offered as an option, so there's no lockin there either. These things together mean the traditional reasons for pursuing federated networks for chat (the avoidance of lockin) are largely irrelevant.
- cm3 10y ago
- Freak_NL 10y ago> […] in a world where clients are all free and the identifier of choice is the phone number […] To me this translates to: “Please run our proprietary software to participate and use a high-value nearly unique identifier to identify yourself — we really like to know that john.doe@gmail.com is the same person as feetfetish33 so we can better quantify you for targeted advertising.” I am willing to entertain the notion that federation is not a solution, but seeing how you now either place yourself in this panopticon or you don't and 'miss out' on things makes me feel that we should at least attempt to figure out a way to put communication back in the hands of the people. For all its warts and issues, email is still effectively federated, and will stay like that for quite a while due to the needs of many (not all, I certainly grant you that) businesses and local, regional, and national governments to control their own email infrastructure (mainly due to legislation and control).
- tdkl 10y ago> we should at least attempt to figure out a way to put communication back in the hands of the people. What to do if people (majority) don't care ? Because that's the side result of bringing uneducated (regarding IT) masses online. They sell on instant gratification, cute shit (emojis, gifs galore) and hype. In return they don't hesitate to give their data and conversations. No wonder everyone want's their own silo.
- mike_hearn 10y agoI have yet to encounter a chat network that uses targeted advertising, so you're well off into the realm of conspiracy theories there. Chat networks are all moving to the use of phone numbers because users mobile phonebooks are a vendor neutral, open access social network of high value contacts that almost everyone has and for which there are simple APIs available. Phone numbers have other advantages. They are difficult to register in bulk (it can be done but it costs a lot more than bulk registering web accounts protected only by a CAPTCHA). Regulations in many part of the world enforce the ability to do number porting which makes mobile numbers truly user owned - unlike email or jabber ids which are ultimately owned by the organisation after the @ symbol. There is a simple remote attestation protocol: you can prove you own the identifier by simply providing a challenge code. Everyone understands them. And it outsources identity management costs to the telcos who have large branch/shop networks to help people who e.g. lose their device/SIM. Building out and staffing account recovery infrastructures is a significant driver of costs for large web platforms. For instance if you have a contract then you can recover your identity by physically walking into a local telco shop with your passport, you will walk out with a replacement SIM (and the prior SIM remotely deactivated) a few minuets later. It's partly by shifting these costs to the telco networks that WhatsApp was able to scale to hundreds of millions of users with only 50 employees. When I look at how things work done this way vs a traditional internet federated network like email, Jabber, IRC etc, I have to agree with Moxie - it's not so bad, actually. I'm not normally a big supporter of government regulations, but making number porting obligatory is a relatively low cost rule that makes the use of phone numbers as the universal id a lot more palatable, because it's truly user owned at that point. Switching mobile networks and switching chat networks is a lot easier than switching email/xmpp providers because forwarding has always been an afterthought in such protocols, is legally optional, and at any rate is always going to be more complicated than just re-assigning ownership of a truly provider independent code.