I also spot "That’s the website, you can’t scroll further." in large, helpful letters. These people seem to have a pretty solid sense of humour. Mild enough it is difficult to take offence to, playful enough to add character.
Hope they do well; I dislike closed source chat programs.
Rather than open or closed source programs, let's have interoperability. Then everyone can choose. I believe Facebook was aiming for something like that with Threads, and was playing to have WhatsApp and Facebook Messenger be open to a specific standard as well?
Proprietary services are interoperable in the beginning and then stop.
Both facebook and google supported XMPP but that's no longer the case. Slack supported XMPP and IRC, but that's no longer the case.
It's completely pointless to expect proprietary stuff to be interoperable. It requires constant reverse engineering and remember that they have money to throw away to hire developers to make breaking changes to the protocol constantly.
One of the highest confidence outcomes I predict from LLM use in software dev is more use of open protocols. It is going to become difficult to maintain a network if you don't use them.
XMPP isn't dead either. Here's an open source project of an XMPP based Slack - https://prose.org/ (I have no association to this, was amazed how much digging it took me looking for Slack/Discord alternatives to find it.)
The most damage to open communications software probably came from the closed mobile app stores. The barrier to maintaining a working app simultaneously on iOS and Android is high. Almost every iOS game I bought 10 years ago is inaccessible and no longer downloadable. Those barriers are in the process of being torn down too, with or without AI's help.
Facebook never federated so their implementation was just an API they couldn't control to them:
> Facebook Messages are evolving to allow people to share rich content beyond text: photos, videos, audio and even stickers. We want to ensure the best possible send and receive experience where all these rich forms of content are reliably and consistently available on every platform. XMPP doesn't support all these (and future) content types, and it's difficult to ensure an XMPP client is rendering them appropriately. As such we've decided to sunset the XMPP Chat API.
> XMPP doesn't support all these (and future) content types, and it's difficult to ensure an XMPP client is rendering them appropriately. As such we've decided to sunset the XMPP Chat API.
This is such a lame excuse, and reveals how much they're control freaks. One of the main points of an open, federated protocol is that people can choose clients that behave the way they want and render things the way they want. "Oooohhh, we can't guarantee with an iron fist that our stupid 'stickers' render correctly on all clients, therefore we can't deal with it!"
This same mentality infests the web, and is why companies insist on slathering JavaScript into everything to force browsers to render their pages exactly as designed, rather than just letting the user agent serve the user's needs.
The push for messenger interoperability is a reaction to the EUs Digital Markets Act (DMA), which requires certain gatekeeper services to allow interoperability with smaller platforms.
Threads is working on implementing ActivityPub for interoperability with other platforms that already use it. ActivityPub is an open standard for implementing the Fediverse, a group of federated social platforms heavily based in the open source community.
Not like it's new, though? The Internet is literally interoperating networks, emails hop from server to server until they reach the user-specified destination server, DNS delegates zones to other servers. These are protocols older than I am, and I've had a driver's license for longer than Matrix exists. Their push is amazing but not by any means unique
Should be mandatory. Things like facebook took off because of network effects not because of the quality of the platform. Being able to migrate all your contacts/ chat/ tweets/ etc somewhere else seemlessly should be enforced by the gov to allow for actual competition. else you end up with first player advantage and network effects being unsurmountable and creating de facto monopolies with 0 benefit for the customer, in an environment that has low set up costs and you should see fierce competition.
And if you are nerd/privacy conscious enough, though their app and cloud service is proprietary, it’s based on Matrix and open source bridges which you can have a full list here : https://github.com/beeper
They did it with XMPP and Windows live messenger in the 2000s.
At the end of the day these companies have no incentive to be responsible stewards of open protocols. The moment they have a tough quarter they’ll eviscerate it if it means they’ll make a buck.
Hope they do well; I dislike closed source chat programs.