this post was submitted on 16 Dec 2023
985 points (79.2% liked)
Fediverse
28380 readers
1231 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 !moderators@lemmy.world!
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
I'm just saying that even on federated instances the users can choose to block Threads, and that that gives the same result for them. There's no need to force the hand of the user; there are more than enough corpo-critical people on Fedi for it not to be taken over by Meta.
Edit: And I understand that allowing interaction with Meta is very risky business. Which is why I like the approach of instances like social.coop which restrict interaction from Threads but still give the user a choice.
Not quite the same result. Blocking the instance stops you seeing their posts, but not the comments coming from their users.
I didn't actually know that. Thanks for mentioning it
My pleasure. TMYK!
No, that's just Lemmy. On Masto it blocks all interactions from users (including prohibiting them from following you and therefore fetching your posts).
Fair. But I'm on lemmy for discussion. I don't want threads' bobbleheaded userbase fucking up every discussion thread on lemmy. So I will stay on instances that have de-federated that shithole and urge other instances to do the same.
But they won't. Seeing how little even the relatively federation-conscious Mastodonians interact with Lemmy, from Threads it will be close to zero (especially since the devs are very "careful" with federation and probably won't display article-formatted posts anytime soon).
I'm not comfortable with assuming the dregs of Facebook will leave Lemmy alone. I'll stick to instances that have defederated and I'll actively block instances that don't.
I'm not out here trying to stop you from being on federated instances or anyone else. But I will not personally support instances that allow that monster into the ecosystem.
You know that if you actively blocked the instances that are federated with Threads you wouldn't have seen this post, right (lemmy.world/instances)? I'm also only active on instances that block Threads, but blocking those who don't is an excessive measure.
Like I said, I don't care what others do. But for me the correct answer is to not interact with users from that platform.
When I start seeing threads users in .world lemmy comment sections I will block .world.
That's not how federation works. If you're on an instance that doesn't allow Threads, you won't see them at all, even when viewing posts coming from other instances.
I am given to understand that I will still see the comments from threads users on lemmy. Just not the posts from threads.
You're confusing defederation with Lemmy's instance blocking. Defederation means that none of a server's content is federated. Lemmy's new instance blocking feature, however, only blocks communities and not users.
I don't think I was confusing the defed from blocking, I was confused about what you meant. Thanks for the clarification.
We are on lemmy. So they are right in this context. I really couldn't give a crap about anything like Twitter because I hate everything about that type of medium.
The thing is, you don't really see anything from the Microblogging Fediverse around here at all, do you, so why would you from Threads? And Meta will only explicitly collect your data if you follow one of their accounts, which is impossible from Lemmy. So in a Lemmy context it is quite irrelevant.
Also,
I'm not ;)
It's a similar situation as with the unions. We can all manage to have a pay rise by ourselves. Or, we unionize and ask together for the pay rise.
Defederating the instance is like unionizing. We all go forward instead of individually to have weight. This weight is in form of killing asap the federating attempt, as threads.net users will have nothing to see in the Fediverse. If you let each user manage the situation, threads.net can do whatever they want. There is no individual responsibility in this case. We have to play collectively.
We need to play collectively because the Fediverse isn't one monolithic network, unlike Meta. It's a federated network. It's each instance and Meta. This is why unionizing is important. It's the Fediverse and Meta. This is the magic of activity pub. You can let others use the protocol but say no to the interaction with them.
The second aspect is that Meta is relying on “cognitive capitalism”. Meta will use free cognitive time from the Fediverse to capitalize. This has huge implication on mental health and all kind of minorities relying on the Fediverse for various reasons. We can say all together no to this, what isn't possible individually. I recommend the book "The Soul at Work From Alienation to Autonomy" by Franco "Bifo" Berardi. It's a good book to understand the issue with Meta and others.
Look, I hate Meta as much as the next person, but they really don't have that much leverage over the Fediverse as people are making it seem. It is completely optional to follow their accounts so they have little direct control over people's feeds, not to mention that their active userbase is quite small. I'd say a better approach is simply restricting interaction by making it opt-in in all ways, just like social.coop.