 idk who needs to hear this but instance admins should not be blocking threads — that’s a terrible default. there are many opportunities to take a stand against big tech, but adding friction to people’s ability to freely communicate with others is not the place. let your users decide if they wanna block threads. if they feel strongly about it, chances are they can figure out how to block a domain themselves. 7 comments
 @samhenrigold Yeah, I think maybe some smaller instances where there’s broad agreement that it should be done could get away with it, but if you’re a big instance with a broad range of people, I don’t think it’s a great move. @matt I think a great distinction is if people are signing up for an experience that happens to be powered by Mastodon vs signing up for Mastodon and using an instance as a vehicle for that. If you're an experience (eg yowza.social) then yeah, anything goes. But like you said, if people are signing up for an account as a means to interact with the broader world (90% of instances) then at that point, an instance admin becomes a service provider and people expect a less opinionated experience  @samhenrigold I somewhat agree, and we won't defederate threads by default on our instance.  @samhenrigold my instance admin blocked them because they didn’t know if they would be able to handle the traffic or if it would drive their server costs up. i *get it* but like… that shouldn’t be an issue, from a technical level. |
Gregory's Server
@samhenrigold this and I believe blocking threads on the server level will just result in people feeling frustrated and moving over to threads.