I continue to be squeezed by both sides of the threads situation. I am operating on the premise that people who think I’m a terrible person and this is a terrible instance for allowing any interaction with threads have left and/or blocked, those remaining seem to want to either have nothing to do with threads at all and are mainly concerned with their data, and those who want to seamlessly interact with threads. I have threads limited/silenced on Infosec.exchange, but that isn’t seamless, and it’s also not fully blocking. So, here’s my proposal:
I remove the limit from threads, and run a job to domain block threads for each account. Any account who chooses can undo the block (or ask me to do it) and then they can seamlessly interact with threads, and those who want nothing to do with them get their way.

Thoughts?

@jerry how many storage you will need if "syncing" with Threads? Will this be a big problem for many instances?
@disaster I don’t actually know - it’ll more be a function of how many people here follow how many people there, and the amount of interaction. The site is close to 7 years old and has ~1TB of media and ~200GB database. The current setup can handle about 10x that without and changes.