@trumpet please stop blocking threads so that I can follow and boost @POTUS
This policy of blocking entire instances simply because you don't like who runs them is silly and detrimental to the Fediverse not to mention our democracy.
@schizanon This has nothing to do with who runs Threads, I’ve posted a few times before on the technical and moderation concerns we have.
We’re looking into how we can protect users who don’t want to federate while allowing those who do. The solution will likely be to limit Threads, while enabling authorised fetch on the server so that user-level blocks will be more rigid. I hope to post more on this soon.
@schizanon
Its actually a big part of the fediverse. If you do disagree with policy its pretty easy to port your account to another server that does federate, like hostux.social @trumpet
@schizanon@trumpet we're starting to see why the decision to block threads is a difficult one once federation is actually widespread. Many accounts people find important to have access to get blocked when it is done at the instance level. It was definitely smart for #fedipact to move on this early since a decision that's already been made is harder to reverse.
The good news is that you can always migrate if the instance doesn't make the choices you want.
Personally I've no interest in seeing content from Threads - if I wanted to see content from Threads, I would join Threads. Same with Twitter, BlueSky and so on.
I think that is the main reason people should not boost or otherwise inject content from one social media provider into another.
In the case of Threads, specifically, it's really not about disliking the person who runs it. It's much more about disliking (and TBH fearing) the proven pattern of evils perpetrated by the company that runs it. Many of those evils are very detrimental to democracy generally - not only yours.
So I'm very happy for my instance to block Threads, and feel it would benefit the world if all of Meta were gone - but for now, I'll take keeping the fediverse Threads-free :-)
Even more specifically though, I have no interest at all in seeing anything by, from or about the President of your country. I suspect I have this in common with a pretty large contingent of people who get quite enough information about the goings-on in that pocket of the world from other sources (or from people in offering their own takes rather than regurgitated ones).
So I for one will be filtering out any content from Threads if I see it start arriving in any significant volume. If your content ends up consisting substantially of regurgitated content from Threads, I will block you too. As I have blocked many who seem only to regurgitate Twitter, BlueSky, etc.
But opinions differ! I am sure there will be many instances that block Threads, and many instances that do not. As with so many other things, the great freedom of the fediverse is that you can easily move to an instance that meets your needs.
@dragestil@schizanon
Speaking as someone moderating a server that is not blocking #Threads yet, this is a vast over-simplification of why servers are blocking Threads: that network is a cesspool of hate, misinfo, CSAM, scammers, and bots, and it's totally appropriate for mod teams to not want to deal with that.
If @trumpet decides a preemptive block is in order, that's their right.
That said, this is the entire point of decentralized moderation: different servers have different policies, so you have different options when it comes to where to go.
Moving your account is easy: making a new one on the other server and linking the two in the settings. If you need help, just ask!
I suggest you look through your follows / boosts, or search JoinMastodon.org, to see if there's an appropriate server you'd like to move to, then go there and search for the POTUS account to see if you can still follow it from there. Anyone who hasn't blocked yet isn't going to: we've all had time to decide.
If users have no say in who their instance blocks then there's no difference between a corporate platform and a fedi instance. "If you don't like it here just move somewhere else" is precisely the rhetorics there.
as a corollary, the only sensible choice is that everyone self hosts their own instance @schizanon@trumpet
@dragestil wanted to follow you on mastodon.social, but it seems they have blocked you or your instance.
The Fediverse is so ridiculously toxic. I've been kicked off like three different instances for things as silly as saying that Neil DeGrasse Tyson is my spirit animal, and blocking people who use the n-word.
I hate it here so much I try to think of ways to undermine it...
@dragestil I want to build an ActivityPub implementation that's so simple to set up that it will lead to an inundation of instances that admins can't possibly hope to moderate.
Something like an AWS SAM template that automatically provisions a serverless instance on a new domain.
Add comment