Jerry Bell :verified_paw: :donor: :verified_dragon: :rebelverified:​ (@[email protected])
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)

– @[email protected]

  • poVoq@slrpnk.net
    1·
    11 months ago

    You are arguing against something I never claimed.

    I said that if Facebook wants to copy and republish something (so that they can put advertisements next to it) they will do that through legal ways as posts are copyright protected. The only way they can do that is through openly federating instances that allow republishing in their ToS.

    It is totally irrelevant if scraping is legal or not (its a gray area), the questing is rather does defederation stop Facebook from using posts from the Fediverse, and it likely does (IANAL).

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

      We’re seemingly talking about different things. I don’t think they can put ads next to my content if they scraped it… Then again isn’t this how Google works? They even have caches of a lot of the content so you don’t need to hit the original one… So we know they store the pages.

      I see how if federated it’s more of a gray area since it’s federated: so maybe they can put ads? Idk seems like another gray area. I wonder how a ToS can be applied from a legal perspective if the content was federated instead of directly posted. Then again Google just looks at a robots.txt file to figure out what/how to scrape. Maybe that should apply here somehow? Idk.

      I’m guessing it’ll take many years for laws to catch up… And they’ll be written by whoever has more money at the time.