Administered by:
It's time to address the elephant in the room, or actually Threads
As many of you may know Threads went live in Europe and with that they started testing federation with the Fediverse
At this point there is a choice to make
1. Block Threads on instance level, that will take away the choice for each person
2. Do not block and let people block if they want to(1 search and 2 clicks)
After much consideration and talks I think we need to go with option 2 and let people decide for themselves
@stux@mstdn.socialYou can simply block the whole "Threads.net" domain by going to the following profile:
@stux Thanks for keeping up the good fight 
@stux user to instance blocks do not prevent the “blocked” instance from fetching posts from the user. Only an instance level block with AUTHORIZED_FETCH enabled can do that. What you are suggesting would only hide threads posts from the user doing the blocking
@stux I understand the decision, but that link just takes me to threads.net which is not somewhere I want to be. Please can you explain how I block the domain?
@stux Doesn't work in Tusky – just redirects to Threads. And https://mastodon.me.uk/@mosseri@threads.net is not, apparently, a valid URL.
Looks as if I have to do this on a real computer, not a phone.
@stux Done.
@stux There's a post circulating that says that blocking the instance on the server level does not actually function as a block, and instead functions more like a mute.
Users on threads (and the data-scraping tools) are still able to read posts, and reply to them?
I don't know enough about how the fedi functions to know if that's true or not. But if it is, just saying "block the domain yourself" doesn't really solve the issue.
What’s stopping anyone from scraping data right now, sans federation?
@plasma4045 Wasn't the question I asked. Go away.
@stux People've been leaving threads because it's a cesspit leaving mostly the worst people behind. It's also fundamentally unmoderated (leading to the exodus), something I'd see as being reason enough to cut off.
The company habitually lies to advertisers about audiences and to their users about how the data is used so that's also a problem. Maybe FB will get in anyway and steal everything for their blessed AI but you don't have to hold the door open and with GDPR (data security) you shouldn't
@stux I get a 404 when I click the link and can't see him at all if I search for him. I just assumed we were already blocking the whole domain
@Smootasaurus i just unblocked 
it could take a moment
I did a search on @/mosseri/@/threads.net (remove the slashes) in my instance's search, which brought it up in a way I could then block it.