If for whatever reason you never wish to interact with #Threads, you can personally block it for your account. This hides all posts and profiles from Threads, prevents anyone from Threads from following you, and stops your posts from being delivered to or fetched by Threads. Simply click the "Block domain threads.net" option on any Threads profile or post you see in Mastodon.

@Gargron Yeah, I do not plan to block #Threads, as I am extending the same policy toward them that I do other instances (in essence, I am treating them like any other instance).

With Threads & #Flipboard joining the #Fediverse en masse soon, I am excited for what 2024 has in store!

Also, it should make it easier to convince businesses & politicians who use #WordPress to install the #ActivityPub plugin so they can interact with the Fediverse without needing to join another site.

@darnell @Gargron What will you be doing about extreme explicit hate content on the platform, like LibsOfTiktok, Gays Against Groomers, etc.?

@darnell @Gargron On that note, I'm really unhappy that the meeting certain folks had with Facebook over the summer wasn't used to give them an ultimatum: ban these types of hate accounts or all parties present pledge not to federate.

@dalias @Gargron I doubt everyone in the group would agree with that ultimatum which is probably why it was never issued.

If people want an instance that blocks Threads, they can always join one.

Most of the larger instances will not block Threads, & simply leave up to individual users to choose to interact with Meta’s platform.

@darnell @Gargron That sounds... disturbing. That there are major instance admins & devs who would not agree with something so basic.

@dalias @Gargron Yes, but most major instance admins are letting their users decide if they want to block Threads or not.

There are many people in the Fediverse who have friends, colleagues & family who use Threads. If their instance blocks Threads, they will merely move towards an instance that does not.

Yep. And conversely, many people in the fediverse want nothing to do with Threads -- polls consistently show 40% or more of the respondents want their instance to block Threads.

So with most of the biggest instances not blocking threads ... it'll be interesting!

And I agree @dalias it was a missed opportunity but @darnell's right: @Gargron
and most large instance admins don't seem to see it as an issue that Threads hosts hate groups

@jdp23 so let that 40% of Threads haters block.

But don't force that on the rest of the instance users.

@dalias @darnell @Gargron

@volkris @jdp23 @dalias @darnell @Gargron That's my thinking, too. It seems to me that letting individual users decide is the more sensible choice. The users who want their instances to block Threads can do so individually if the admin doesn't. OTOH, if the admin does block Threads, then users who do want to connect to people on Threads will have no choice but to give it up or move to another instance.

@volkris @Gargron @darnell @dalias @jdp23 Or if you're willing, you can host your own instance. I've actually considered doing it but never got round to it. 😅

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.