Yes. Are you, the relay operators, deleting stuff? Which ones? Where is the line? Do you delete CSAM? Are you saving logs of what each pubkey is querying and receiving from your relay? Are you building interest lists per pubkey? Etc etc.
Discussion
You think it matters if relay operators build interest lists per pubkey, as anyone can do with the data on the relays like the guy you're replying to said
But you told me we'll never need a NIP for addressing the first question: "are you deleting stuff"
I see how you think this way, but refactor it a bit?
The standardization is not needed, neither with interest lists, nor with deleting practices.
How do you expect a P2P network to handle this stuff without it being standardized?
Do you think everyone will just become tech nerds that study the details of how their apps work and naturally migrate away from apps that are damaging the network? Because, no
Choose relays like you choose keys to follow. Don't just randomly choose them and accept what other tell you. Each operator has a completely different view of another. They are just people in the end. You cant standardize people.
You say "don't just randomly choose"
People will naturally choose what the authorities market the hardest, even worse than random choice
And you're expecting them to do better than random choice without a system to help with it. You're wrong
People will naturally gravitate to a small number of apps based on what other people are using and if those apps aren't standardized to report on each other's behavior, they'll barely notice when those apps start sabotaging the network
If more nodes are suddenly becoming what would be tags 3 and 5, but there's no tagging system to automatically stop relying on those nodes, π€π§ ππ© π‘πππ¨π© π©π€ πππ‘π₯ π©ππ πͺπ¨ππ§ π’ππ£πππ π©πππ©, then people won't even notice someone's posts being filtered until it's been months since they heard from that person.
This is like how on the current version of nostr, there's no P2P data integrity verification, so people don't even notice someone's posts being filtered until it's been a long time since they heard from that person.
Network nodes aren't just people
If they delegate their choice to the authorities, they are going to be slaves forever.
Regardless of how much the protocol tries to protect them.
You don't need nostr to be a sheep. And nostr can't block you from being a sheep.
Being proactive makes a difference
If the first nostr app with P2P data integrity verification ALSO has this system for users to see reports of what censorship level each relay is at, we create natural momentum towards people thinking it's silly to never venture outside tag 3+5 relays
If the first app like that has no solution to this problem, there's natural gravity pulling people to split off into a bunch of echo chamber cults that attack members for venturing outside their chosen bubbles
Seems a little sensationalized, tbh. Relays can be scraped without content, so I donβt what difference does it make?
Some relays can literally sell information like when you are connected, from which IPs and thus locations, what searches do you make and which posts are you looking at in real time. Lots of companies buy that information.
What I wrote didnβt make sense but it seems like you got what I was trying to say.
Fair point regarding the scope of information they have, and yeah, I can see some concern down the line.
I have to think through it some more and keeping an open mind, but the way Iβm seeing it right now is if youβre using a public relay that you arenβt paying for then yeah, youβd run that risk. If itβs a paid relay and part of their ToS is not selling your information, then thatβs the safer route for the end user.
Though I think for notes to proliferate youβd inevitably have to connect to at least 1 or more public relays that public goods.
You're absolutely right. I had not considered all the data
My privacy policy is I dont do shit with your data, that's more trouble than it's worth π
But now I have another thing to add to grain! It's a great idea to have a standard PP/ToS in the repo that displays on the frontend footer and can be changed by the operator.