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 :pixelfed: admins to easily add user domain blocks for all local users)

I'm eager to hear your feedback!

PR: github.com/pixelfed/pixelfed/p

34
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
🎓 Dr. Freemo :jpf: 🇳🇱

@dansup

Well I certainly will be refusing to use pixelfed then, this is uncalled for.

0
11mo
0
11mo
Sean

@dansup Weren’t you complaining about instagram appearing to block your app??? How is this any different?

0
11mo
Sean Bala

@dansup It seems like Opt-In might be a nice middle ground between full openness and full blocking. Was there something that prompted you to go down this route? Was it Threads opting for Opt-In?

0
11mo
MrCopilot

@dansup just from an administrative perspective, having the floodgates of reportage opening to deal with makes this decision seem obvious and sensible.

Philosophically, there is ample space for disagreement, but each admin and user has to grapple with each other's choices.

This is in contrast to the very services trying to federate.

Where the user must endure the fickle whims of the tech bro CEO, corporate board, advertisers & market.

All to say, glad you made a thoughtful choice Dan.

0
11mo
Debbie Goldsmith 🏳️‍⚧️🏳️‍🌈

@dansup Not happy. I will unblock it for my account as soon as that feature is available. Could you please point me at the PR so I can follow it?

0
11mo
PhilipKing

@dansup I don’t understand this. I see on Threads ordinary people doing ordinary things. Perhaps you’d like to explain what it is you are worried about?

0
11mo
Thu Htoo San :fedora:

@dansup Thank you! You've made the right decision for the community. Opt-in is the way it should be from the start.

0
11mo
Replies