Jerry Bell :verified_paw: :donor: :verified_dragon: :rebelverified:​ (@jerry@infosec.exchange)
infosec.exchange
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?

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.

[…]

(Note: this was only intended for Infosec.exchange/.town, and fedia.social)

– @jerry@infosec.exchange

  • csm10495@sh.itjust.worksEnglish
    21·
    11 months ago

    It only takes looking at your data to figure out your trends, save the trend, and serve you ads.

    Think about it: public posts are public. It’s the same as you putting a note in the town square. Anyone can look at it and see the username of who wrote it.

    Defederation doesn’t stop that, it just inconveniences people who want to use/see both sides from one login.

    • poVoq@slrpnk.net
      32·
      11 months ago

      This is not how it works technically.

      For Meta to analyze your data they need to either scrape it (legally questionable and scraper bots are commonly blocked on server level) or work with a local copy. By federating with them you are allowing them to legally make a local copy of all the posts of the instance.

      Newspaper articled are often also public, yet google got sued (and lost) because they were scraping and analyzing them to put previews in their search results.

      Just because something is public doesn’t mean you can just take it. Copyright still aplies.

      Defederation does stop legal use, and Meta is already in enough legal trouble, especially in the EU, that they are unlikely to blatantly pirate user contributed content from sites that defederated from them.