This blog post by Ploum, who was part of the original XMPP efforts long ago, describes how Google killed one great federated service, which shows why the Fediverse must not give Meta the chance
I’m gonna throw this out there:
If Meta is going to join the fediverse (or implement something with activitypub) there is absolutely nothing we can do to stop them.
It’s an open protocol. They can use it.
The only thing we can do is force them to follow the AGPL and/or fork the code if they get crazy with change requests.
deleted by creator
One thing we can do is encourage the Instagram users in our lives to open a fediverse account and use Instagram from the other side.
I red tha article and I think there is a problem in who it was managed at the time, if Google or Meta wants to join they should to us not us to them so if they break federation we should not care and continue implement our stuff, if something usable comes out of them joining we could use that but we are not their slaves, they are going to play in our home so we establish the rules.
Plus I think that if we don’t become meta’s costumer support and I don’t think we will, we are not that dumb, meta joining the fediverse would only benefit us because we could see all the posts from Meta while being on a private add free server, people wouldn’t have to choose between Instagram where all their friends are mad pixelfed ecc.
What do you guys think? Open to talk.
Can anyone with expertise explain the structural difference between Matrix and XMPP?
The X in Xmpp is for extensible. I find issue that a protocol that is supposed to be extensible was killed by being extended.
