- cross-posted to:
- thenexusofprivacy@lemmy.blahaj.zone
- cross-posted to:
- thenexusofprivacy@lemmy.blahaj.zone
cross-posted from: https://lemmy.blahaj.zone/post/7992691
There are some straightforward opportunities for short-term safety improvements, but this is only the start of what’s needed to change the dynamic more completely.
This is a draft, so feedback welcome!
deleted by creator
The Ministry of Truth, of course.
who is the judge of the server side code? what about the terrible green on white default lemmy color scheme? who is the judge of https? who is the judge of the physical infrastructure of the internet? who is the judge of wifi6?
omg it goes so deep judges everywhere judging me!!!
I have no idea what you’re trying to say.
You can immediately see who is an admin and who is not.
If you have an open instance and someone puts csam on it and reports you, you’re toast. Thats what blocklists are for and they arent new. Mastodon instances already have blocklists which every sane admin uses. They even come in different flavors.
The way this works is that certain instances „vote“ on blocks by applying blocks to certain instances and if one, multiple or all „trusted“ insrances block an address, it „federates“ through these updated lists.
good thing nobody suggested that… And if they did it would be completely unenforceable.
Yep. But, even though I didn’t suggest it, I didn’t explicitly say that it didn’t mean global blocklists. So I clarified it, and added a footnote with more detial.
Nonsense. Instance blocklists are used across the fediverse today. They’re certainly not a perfect solution but they have the advantage of actually existing. See Blocklists in the fediverse for a lot more discussion.
deleted by creator