Jerry 🦙💝🦙Dec 16, 2023

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?

Show threadCaptMorganDec 16, 2023
@jerry think of it as opsec, would you be leaking ANY data to threads for any users who don’t explicitly opt in? I think they’re going to be able to scrape the user data anyway if it gets leaked through other instances who choose to federate with them so anything other than complete isolation will allow them to gather and monetize data from all fedi users eventually.
Show threadCaptMorgan
@jerry I still believe for users who really want to interact with threads, just join threads. You dont gain anything by having a fedi account and then interact with users on threads, you are effectively giving threads all your user data so why not just join threads? Whats the point of Mastodon if not to explicitly opt out of being tracked and monetized by those guys?
Dec 16, 2023 at 6:36pmWeb
Show threadAndrew PorterDec 16, 2023
@CaptMorgan You know that your posts and boosts are not private, ja? It's all publicly available at the "https://freeradical.zone/@CaptMorgan" URL for anyone who wants to scrape that data.
Show threadCaptMorganDec 16, 2023
@adfporter good point, so threads can scrape any data they want regardless of uf they ate allowed to federate