After some careful consideration, I have decided to block threads.net on pixelfed.social and .art by default
However, users will have the ability to unblock the domain
Soon we will be selectively enforcing authorized fetch for accounts with domain blocks so as to provide the best of both worlds.
(I'm also shipping a command for 
admins to easily add user domain blocks for all local users)
I'm eager to hear your feedback!
🇳🇱
Well I certainly will be refusing to use pixelfed then, this is uncalled for.
@clacke I see plenty of reasons in there to block threads, not a single thing to justify software blocking by default.
As i understand it from the post, it's actually a nice feature - the optional blocks.
It doesn't mean that a software will have some blocks by default, but admin will have an ability to block some instance "optionally". For example, you blocking poa.st cause your users tired to see these siegheiling fuckers in their mentions, but since the block is "optional", any user can unblock it for them personally.
It's like a "personal block" of the domain but only the other way around, a "personal unblock"
The feature which allows an admin block to be overruled is not what I have issue. The fact that the software itself dictates pre-blocked servers is something I am not ok with.
As i read it, @clacke said he will block threads by default on pixelfed.social and pixelfed.art, the instances where he is the admin, and he created a tool to do it. Pixelfed-the-software won't have any blocks by default.
Oh yes, I misread that. My apologies, no issue with the software then afterall. Thanks for pointing that out.
@freemo It is literally called for.
mashable.com/article/threads-h…
@dansup