this post was submitted on 07 Jul 2023
3567 points (98.6% liked)
Fediverse
27910 readers
1 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to [email protected]!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
Threads is using the protocol that the entire fediverse is using, called ActivityPub. The protocol allows for lemmy instances to communicate with each other and with other sites like kbin and mastodon. What lemmy.ml did is called defederation, so threads can't communicate with lemmy.ml. This is to prevent meta/Instagram/Facebook from killing ActivityPub in the same manner Microsoft, IBM, and Google has killed open source protocols in the past.
The most notable one imo is Google semi killing XMPP. They started Goolge Talk based on XMPP and after many people started relying on it, they replaced XMPP with their proprietary protocols.
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.
If one instance gets too big they could just ignore the standard and start adding random tweaks to it. And all the others would eventually have to adapt to that or risk becoming irrelevant by being incompatible with the big instance.
Federation allows for choice. Indeed, many AP implementations already add to the base AP stuff. Peertube already does this itself.
For this to really be a problem, the server software would need to be maintained by the same person running the instance, and they have to have the manpower already to either a) Build an implementation or b) Run a fork of existing software. Both take effort and quite frankly is juice that isn't worth the squeeze to risk cutting yourself off from the network like that.
the standard is made by the World Wide Web Consortium, which I trust to not let facebook take control of their standard. They also manage standards like HTML, CSS and SVG
No, they re-publish the work of WHATWG in standards form, the vendors literally made a pact not to deal with them. Then sometime in the last decade they standardized EME, even after the technology activists told them fucking not to. Defective By Design said this shit for years, decades, and W3C ignored everyone. I have more reason not to trust Berners-Lee at this point than put any stock in his leadership skills.
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.
Yes, sounds like there should be Meta's fake, desecrated version of "ActivityPub", and the actual Fediverse version of ActivityPub that does not budge to any of Meta's interests.
That's the same problem as with Chrome. If internet for most people goes through Google Chrome (which it currently does: Android, smart devices, Electron Apps, Android apps, Edge, Brave, etc.) then the controlling entity can redefine the meaning of that protocol. In the above example it would be Google redefining the meaning of the web, see DRM, manifest v3, and similar efforts. Small players wouldn't be able to play catch-up or disagree (it wouldn't matter) and risk bring irrelevant.
The admins of defederating instances fear the same could happen to ActivityPub and fediverse.