Actually. If you think about it, its design is kind of a vulnerability.
Let’s say a Fed agency wants to target and take down a relay.
- Create a bunch of child P, crap and push it out to the relay from anonymous accounts, then get a search warrant or complain that the relay is allowing that stuff and arrest the individual running the server for allowing its distribution.
Rince repeat till the whole network is harmed, and people are afraid to run relay’s.
The network degrades, and people start experiencing slowdowns and frustrations.
- In my opinion, relays - especially public relays. Should have the option of a public filter list of known bad actors. If several relays ban an address, flagging it as high spam or child P, it should be given a note on the network.
Then relays can filter based on how many times that address was used nefariously.
So if someone keeps switching relays and getting banned, eventually there’s a threshold hit that lets all public relays simply ban as they can obviously see there’s a problem with that user.
New id, process starts over.
Yes, I understand the need for censorship resistance. But outright illegal activity with no mechanism to mitigate that content can be used as a weapon to harm the network.
No one wants to open this app and be met with a sea of kiddy P. There has to be a mechanism to control that at a higher level than individual blocking.
Maybe a way for individuals accounts to subscribe to a blocklist of bad actors, which is derived with a consensus mechanism amongst their followers.
So, if 80% of followers block this address don’t show its content. Allowing that threshold to be adjusted.
It’s kinda like that right now with the way you see followers stuff and then out one level creating a web of trust of sorts, but I don’t think it’s enough.
Especially the relay vulnerabilities.
Oddbean new post about login | logout