Embed Notice

I did the requisite responsible reading about Threads federating, and I decided to domain block them after thinking about it.

1) Anybody who wants to view my public posts can still view them.

2) This is mostly an infosec account, and there's AFAIK zero infosec community presence on Threads.

3) I'm not really interested in helping Threads grow an infosec community presence.

4) I don't think there's any Mastodon admin ready for the network effects of several million users suddenly joining the network. There is shockingly little discussion about problems like coordinated inauthentic activity, which are going to come at that scale. I'm REALLY not interested in seeing or interacting in any way with chinese state disinformation campaigns lol

5) Mastodon servers and clients are held together by duct tape and prayers by people in their spare time. Threads is held together by people paid full time salaries at a large multinational corporation. Threads can make a better fediverse app and a better fediverse server than anything that currently exists. I think any future where people start downloading the Threads app as their default client to interact with the fediverse, and where people start using threads.net as their default server, is one that is very dangerous for the existence of the fediverse as a set of interoperable clients and servers built on open standards. I'm doing my part to make this as unappealing and as high friction as possible 🫡

6) fuck libs of tiktok, and fuck threads which is currently platforming them. The impact of accounts like Libs of TikTok on rolling back LGBTQ rights in the real world is a very good example of why network effects, discoverability, and social media amplification are dangerous.

Thanks to @jerry for letting people on this instance make this choice themselves. Having this kind of choice is a welcome change from other social networks.

#threads #fediverse #fedimeta