I just read this point in a comment and wanted to bring it to the spotlight.
Meta has practically unlimited resources. They will make access to the fediverse fast with their top tier servers.
As per my understanding this will make small instances less desirable to the common user. And the effects will be:
- Meta can and will unethically defedrate from instances which are a theat to them. Which the majority of the population won't care about, again making the small instances obsolete.
- When majority of the content is on the Meta servers they can and will provide fast access to it and unethically slow down access to the content from outside instances. This will be noticeable but cannot be proved, and in the end the common users just won't care. They will use Threads because its faster.
This is just what i could think of, there are many more ways to be evil. Meta has the best engineers in the world who will figure out more discrete and impactful ways to harm the small instances.
Privacy: I know they can scrape data from the fediverse right now. That's not a problem. The problem comes when they launch their own Android / iOS app and collect data about my search and what kind of Camel milk I like.
My thoughts: I think building our own userbase is better than federating with an evil corp. with unlimited resources and talent which they will use to destroy the federation just to get a few users.
I hope this post reaches the instance admins. The Cons outweigh the Pros in this case.
We couldn't get the people to use Signal. This is our chance to make a change.
They shouldn't just defederate from Meta, they should defederate from any other instances that federate with Meta. Like a firewall against late stage capitalism
But that is a double-edged sword. What if, for example, mastodon.social doesn't defederate with Meta, but you defederate mastodon.social? Now you've just cut yourself off from a huge portion of the fediverse. Admins should defederate from Meta if their community wants to do that, but defederating from other instances that didn't do that is going a bit too far, in my opinion.
A small price to pay for salvation from Meta.
I've already blocked mastodon.social.
Why?
Because the size of it, the sheer centralization around it, it creeps me out.
Why? If you have blocked meta shouldn't you already be exempt from seeing comments and posts by their users on other instances? Why is this punitive approach needed
Edit: (Alongside downvoting, an explanation might be better suited to change people's minds, I just eant to know the advantage of this approach since you are excluding yourself from many users and you would have already blocked meta in this scenario)
Yes, at least that's how it is explained in How the beehaw defederation affects us, Back then, beehaw.org defederated from lemmy.world.
Translated into the current context:
Conclusions:
Or what do you think, @amiuhle@feddit.de?
Hi there! Looks like you linked to a Lemmy community using an URL instead of its name, which doesn't work well for people on different instances. Try fixing it like this: !asklemmy@beehaw.org, !asklemmy@lemmy.world, !asklemmy@lemmy.ml
You'd see comments and posts from their users on other instances that don't block Meta.
It's unclear how many users you would actually exclude, I think a lot of users who are on the fediverse right now don't want to have anything to do with Meta.
As the fediverse grows, there will be different bubbles with not much interaction between those, mainly because some instances won't be moderated while others will try to create discrimination free environments.
Just so I understand, blocking an instance:
Does:
It doesn't:
Is that right? I was under the impression that defederating would block them completely, as that is how it worked over at mastodon, if it doesn't that seems like a serious oversight.