346
submitted 1 year ago* (last edited 1 year ago) by deadsuperhero@lemmy.ml to c/fediverse@lemmy.ml

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

Any instance that federates with this garbage should be mass defederated

[-] aaaaaaadjsf@hexbear.net 9 points 1 year ago

Yeah I agree. Can't be federating with Instagram: comments section™, owned by Facebook®.

[-] pjhenry1216@kbin.social 3 points 1 year ago

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

[-] joeldebruijn@lemmy.ml 1 points 1 year ago

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

[-] pjhenry1216@kbin.social 2 points 1 year 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.

this post was submitted on 31 Aug 2023
346 points (92.2% liked)

Fediverse

17776 readers
15 users here now

A community dedicated to fediverse news and discussion.

Fediverse is a portmanteau of "federation" and "universe".

Getting started on Fediverse;

founded 5 years ago
MODERATORS