Conversation

Notices

1. Embed this notice
   Tim Chambers (tchambers@indieweb.social)'s status on Sunday, 17-Dec-2023 03:28:18 JST Tim Chambers

   in reply to

   • Merry Jerry 🎄🎅🕎⛄️❄️

   @jerry Removing the block but assisting users to block individually that want to is an interesting choice. Appreciate your thoughtfulness here as an admin, and your commitment to an open social web as well.

   • Embed this notice
     Merry Jerry 🎄🎅🕎⛄️❄️ (jerry@infosec.exchange)'s status on Sunday, 17-Dec-2023 03:28:19 JST Merry Jerry 🎄🎅🕎⛄️❄️

     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?