There's a common false dichotomy about #Threads: cut them off, or leave it to user choice.

I can't speak to other software, but Mastodon offers a third option: limiting Threads. This can be done for all users of a server.

- You can follow Threads accounts after clicking through a warning.

- You have to manually approve followers _from_ Threads.

Note, however, that boosted posts will continue to appear in your home timeline:

https://github.com/mastodon/mastodon/issues/26301#issuecomment-1868240966

So... I get banning the Threads server. I might do it myself, actually.

I get leaving an instance that doesn't ban Threads to join another instance that does ban it. Cool, migration is a feature of the fediverse.

But... don't ban servers that don't ban Threads. Like... that's some weird Civ III peer pressure bullshit.

I probably will ban Threads from my account. But I'm not leaving infosec.exchange. @jerry does entirely too well at server administration and this entire instance is comprised of too many people to be of one mind.

Like... we can all agree, no nazi's and racist shit, right? But politics and socio-economic models... fuuuck.... there's no way.

And I really want to talk with y'all. And I really really really don't want to spin up my own instance right now.

So. Ban Threads. Don't ban Threads. Instance wide or individually. But don't balkinize each other because of each other's stance for/against/indifferent Threads.

#Threads #ActivityPub #Fediverse