Cypherpunks write protocols to censor users based on KYC: https://github.com/cashubtc/nuts/pull/106
Note this feature is optional and the auth is blinded in the same way as e-cash itself. It is a ZK proof, the mint doesn't know the authenticated user.
Being optional is irrelevant as such mints would still be considered cashu mints. Mint knows each authenticated user with a `linkingkey`and account model: https://github.com/cashubtc/nuts/blob/9cb6272e9d1eb26fdfb117318bba825c068e888d/16.md https://image.nostr.build/0bc478c5e6563054fe6f46abc5bc88cf46417ce4af9faad6dfb7e72e6a57ea16.jpg
The more I look I to this the more disappointed I get. After a got a post censored and then deleted on nostr (i still dont know how and by whom)and now this , I think this operation is highly suspect, to the point that it may be malicious ? Bittorrent mainline DHT with millions of relays and #pubky may be a better bet.
What!
https://image.nostr.build/f204b03ae17f82bcd9ad7e52f10a72d2a1bf09b966a2741bb16700e6af26e351.jpg
Which app is this?
The client was amethyst. Shouldn't matter if its truly open source. If we can have Sybil attacks then the architecture is garbage.
Gotcha. Not an amethyst fan. So nothing surprises me with that client.
What is your preferred client?
Nobody censored you, dumb nigger
Go suck on an exhaust pipe , shlomo https://image.nostr.build/f204b03ae17f82bcd9ad7e52f10a72d2a1bf09b966a2741bb16700e6af26e351.jpg
Censor me bro 😂 Fucking retard thinks he's being censored 😂
My post was changed and not by me, shlomo. Do you speak English ?
That's not really possible, because your posts are signed by your key unless you leaked it.
Like I said, 2 of Peter Todd's posts were simarly censored. I saw that. I supposed he also leaked his keys ? The problem is, with only about 4 relays active you have a high chance of skullduggery. If we had , for example , a bit torrent network protocol (mainline DHT) with >10million nodes, tampering would be crowded out
As far as understand, nobody can censor you on nostr. That's the entire point of nostr.
Well, I got censored. Three times. So there's that. They're patently lying. Which makes it a honeytrap ? If the amethyst client did the censoring then there's a problem with the protocol. Something stinks here
Individual relays can decide to stop hosting your posts, but as long as some other relays keep them, then people can see them. This is why it's a good idea to connect to many relays simultaneously. It seems very unlikely that all relays would drop your posts. How do you know your post was censored? Were people interacting with the post for a while before it suddenly vanished, or what?
See the attached , the post had a "sensitive viewing" cover notification plastered over it. Two posts. Another post was deleted.I didn't do any of that. Don't know how to so that. So, who did it in a "censorship resistant network" I don't want to go into the network layer and start screwing around with config. Get a proper network layer, like Bitorrent mainline DHT. https://image.nostr.build/f204b03ae17f82bcd9ad7e52f10a72d2a1bf09b966a2741bb16700e6af26e351.jpg ?
Regarding the deleted post, it might just be a latency thing. I was trying to view your other posts, but there were none. Then about 10 minutes later they started showing up. I guess sometimes it takes time for information to propagate in distributed systems, especially over Tor. Also, how old was the deleted post? Many free relays delete posts after a certain amount of time, according to anecdotes, and it happened to me as well, but my post was definitely more than a month old.
Could be. I was not too worried about the deleted post for that reason. My posts that were censored were in a thread started by Peter Todd, I though he may have tampered with them , until I saw 2 of his posts also were censored in the same way. Unless he censored himself. Weird. Bottom line. We need a tamper proof network , otherwise what's the point ? Bitorrent with over 10m nodes probably gives you at least a few tens of thousands of nodes for your posts , out the gate.
Nostr seems to be pretty tamper proof. Popular clients do allow users to report abuse though. For example, you can report a post as spam. It's up to relays and clients to accept or reject the report, and decide what to do with that information though. Maybe that's what happened with some of your posts.
you do know how BIP/NIP/NUT processes work right? or for all the years you have been around you have not bothered to research it? proposals are open, implementation optional. go elsewhere troll
I don't know how things work. Please educate me and explain why this is possible in the first place.
https://bips.dev + https://bips.dev/2/ educate yourself