It should come as no surprise that the lemmy.ml [http://lemmy.ml] admin team
took about 2 minutes to decide to pre-emptively block threats / Meta. Their
transparent and opportunistic scheme to commodify the fediverse and it’s users
will not be allowed to proceed. We strongly encourage other instance
administrators to do the same, given the grave threat they pose to the
fediverse.
How does that work? Is threads using a protocol compatible to lemmy?
(And I fully agree with the preemptive blocking of any facebook stuff).
Edit: thanks for all the detailled answers.
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.
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.
I agree in theory, but in practice, when Google dropped RSS and XMPP support it took most of my friends with it, which is what started this mess in the first place. I’m actually not a fan of mastodon; feels too ambitious to start a new protocol without a killer app. RSS and XMPP are extensible protocols and I really just want modern support for those.
ActivityPub wasn’t built with the purpose of having a “killer app” in mind. That’s centralization logic. The point is for all apps to be able to talk to each other regardless of where on the network and maintaining the ability to do so seamelessly without the user having to think too much about it.
Mastodon should be able to talk to Lemmy. Lemmy should be able to talk to Pixelfed. Et cetera. I don’t believe XMPP had the same purpose, matter of fact I remember it just being a subpar IM protocol iirc, and I don’t see social media going by the wayside the way IM clients of the past did.
How does that work? Is threads using a protocol compatible to lemmy? (And I fully agree with the preemptive blocking of any facebook stuff).
Edit: thanks for all the detailled answers.
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.
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.
When they do go that route, I propose the community fork the standard and continue work that way. We already do this with code.
I agree in theory, but in practice, when Google dropped RSS and XMPP support it took most of my friends with it, which is what started this mess in the first place. I’m actually not a fan of mastodon; feels too ambitious to start a new protocol without a killer app. RSS and XMPP are extensible protocols and I really just want modern support for those.
ActivityPub wasn’t built with the purpose of having a “killer app” in mind. That’s centralization logic. The point is for all apps to be able to talk to each other regardless of where on the network and maintaining the ability to do so seamelessly without the user having to think too much about it.
Mastodon should be able to talk to Lemmy. Lemmy should be able to talk to Pixelfed. Et cetera. I don’t believe XMPP had the same purpose, matter of fact I remember it just being a subpar IM protocol iirc, and I don’t see social media going by the wayside the way IM clients of the past did.