So Facebook tries the old EEE - Embrace Extend Extinguish. 1.A big company is Embracing an open source standard ("we're friendly, see?) They get a lot of users that way - even the open source savvy types. 2.they start Extending that standard "to make it even better" - but not talking about these changes with the rest of the community first. They cannot react quickly enough and become incompatible with the new version of this standard. 3.Extinguish. When all the users are effectively using the big companies platform with something that isn't the original standard anymore they change it so much that it isn't compatible at all anymore or replace it completely.

[–] Rhabuko@feddit.de 0 points 1 year ago* (last edited 1 year ago) (1 children)

Yes. Threads wants to use the ActivityPub Protokoll. We can interact with Kbin and Mastodon users thanks to this Protocol. The fear is that they use their huge user base to change the protocol to their liking (basically take control over the ActivityPub) and everyone who wants to stay federated with them and their users has to adapt those changes until the day they will simply cut everyone off.

[–] HopperMCS@twisti.ca 1 points 1 year ago

When they do go that route, I propose the community fork the standard and continue work that way. We already do this with code.