this post was submitted on 19 Dec 2023
846 points (82.9% liked)
Fediverse
27506 readers
977 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
My objection with federating with Threads has nothing to do with privacy or data access, it has to do with keeping the ActivityPub protocol alive. Embrace, extend, extinguish is a much more legitimate threat to the fediverse than data scraping ever will be. No, the danger is that Meta will begin to contribute to the protocol. At first, contribution by a corporate actor would seem like a fantastic boon to an open standard that we wish to see grow, that's the embrace phase. But it would not be long before Meta began adding features that are exclusive to a Threads user - they'll extend the protocol to better accomplish their ends. In this way, they seek to bring more and more users into their platform in order to take advantage of these exclusive features while maintaining compatibility with the larger Fediverse. The end goal is to have enough users that when they decide to break that compatibility, they will make off with the majority of the users from the open community; that's the extinguish part.
This is a well-established strategy that large tech companies have employed with open standards in the past (see XMPP). I strongly believe it is in the Fediverse's long term interests to remain defederated from Threads, and any other large corporate player. Better to have fewer users and grow organically than to federate with Meta; we may see a short term boost to the fediverse, but the long term risks outweigh any benefit.
That being said, the nice thing about the fediverse is that I can just leave this instance for another if I disagree with the admin's decisions.
I feel like Google is, or has, done this with AOSP
and with the usenet
I seen a lot of people post this and they always think that the counterpoint to that would be just don't allow them to build exclusive features into the standard. If they add a feature, fine but it has to be for everyone.
If they start adding exclusive features then the developers can block them at a API level. The open source GNU license still gives the original developers creative control over the project and they can shut down anything that is not contributing to open source standards. Is there a need for individual instances to take action unless you think that the developers won't block Meta, and they hate meta, so they will. But right now there's nothing for them to do because Meta haven't actually done anything yet.
You're making the assumption that Meta will give a single shit about the GNU license at all. Does the fediverse have the means to fight one of the largest companies on the planet in court?
They don't need to take them to court they can just block meta if they act badly there's no need to sue.
Left this in another response to previous poster, but since you summarized the points, I wanted to link the article as well: https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html
How does defederating mitigate EEE?