347
Threads' New Terms and Conditions Affects the Fediverse (wedistribute.org)
submitted 2 years ago* by [M] to c/fediverse@lemmy.ml
161 comments fedilink hide all child comments
 

This shouldn't come as a huge surprise. Meta is moving forward with their plans for Theads and the Fediverse, and their adjusted terms reflect a new impending reality for Fediverse users.

you are viewing a single comment's thread
view the rest of the comments
[–] 25 points 2 years ago (3 children)

Any instance that federates with this garbage should be mass defederated

  • permalink
  • fedilink
  • source
  • hideshow 6 child comments
    •
  • [–] 3 points 2 years ago (1 child)

    Defederating won't stop this. Defederating means you don't pull their data, not the other way around.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    That would require blocking their servers/domains/IP adresses at the firewall level I guess? Preferably taken from a curated list like NextDNS does?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago

    Partially. It'd help a little bit. But if you federate with another instance that doesn't block it, that data will still get out.

    Essentially the protocol would have to be updated to carry a blacklist that all instances would adhere to, but basically via an honor system.

    The only method that could truly protect your data would be whitelisting, but that would severely hamper and fracture the fediverse.

  • permalink
  • fedilink
  • source
  • parent