just go to an instance that doesn't federate with threads.net
You can also block the threads.net instance on the most recent lemmy version (0.19.0)
this post was submitted on 20 Dec 2023
29 points (100.0% liked)
Mastodon
196 readers
2 users here now
Decentralised and open source social network.
founded 5 years ago
MODERATORS
@abobla thank you for the update. Where can I block it? Can you help me with it?
I don't know how to do iton mastodon, but I know it's possible on lemmy 0.19 (lemmy.world, lemmy.ml, lemm.ee and others have this version).
I've never blocked an instance though.
edit: grammar
You can’t block Threads users or comments with the Lemmy instance block function, which basically makes the lemmy instance block function practically useless.
Interesting, maybe this can be suggested as a future update for lemmy
It was suggested long ago. This useless bs is what we got instead.
Question:
Is it possible that this happens because your instance has already defederated from threads?
My instance (mander.xyz) has defederated from them and I too can't block threads. (Fun fact: mander has only defederated from 2 instances, threads.net and burggit.moe)
I think you misunderstand: lemmy’s new instance blocking feature that users can use only blocks posts from an instance, not users or their comments from that instance, which is what most people wanted the feature to do: block the toxic jerks from any particular instance along with their posts, comments, etc the same way defederation would. By only blocking their posts but allowing their comments, etc. to come through, the new feature is mostly useless, as it still requires users to be blocked individually.
Since Threads is an instance that has, rather than thousands or tens of thousands of users like a typical lemmy instance, but tens of millions, this makes things even more daunting for users of instances which don’t defederate from Threads.
Sounds simple on paper, but my worry is that it would change the culture of Mastodon.
Here's a question, forgive my ignorance. Is there a way to determine ownership of an instance beyond the name of the user account that owns it?
What if meta used their massive amounts of data storage to flood the fediverse with meta-owned instances, making it difficult or impossible to determine what they control and what they do not?
This is a concern I have also posed.
Furthermore, greed becomes a factor when you consider someone could sell their instance to a corporation with no one being any the wiser.
This will be an ongoing struggle until capitalism is ended. Westerners think China has a firewall to keep The Truth out, but mostly it’s to keep foreign capitalists out.
There are better arguments for not federating with Meta’s Threads, some of which can be found in !fediverse@lemmy.ml. Firstly, Threads isn’t going to be able to restrict speech on other instances, at least not in any direct fashion. And secondly and more importantly, an argument for “freedom of speech” without qualifications is either naive or disingenuous: Paradox of tolerance
Right, that and knowing the long history of Embrace, Extend, Extinguish (EEE) ought to be sufficient.
@davel what do you mean about "an argument without qualification"? And what has this to do with what meta is banning?
Okay.