One of the most important NIPs has been merged. π
https://github.com/nostr-protocol/nips/pull/1256
Login to reply
Replies (43)
The Satoshi NIP
LFG!!!


One of the most important NIPs has been merged. π
https://github.com/nostr-protocol/nips/pull/1256
View quoted note →
@Gigi π
Right to vanish
One of the most important NIPs has been merged. π
https://github.com/nostr-protocol/nips/pull/1256
View quoted note →
If relays implement it...
This is important progress.
One of the most important NIPs has been merged. π
https://github.com/nostr-protocol/nips/pull/1256
View quoted note →
This is no different from "do not track" and relies on people respecting it, lol good luck
Why is it important?
And if the 3 letters in all the 17+ eyes π countries delete everything they've collected as well ...
People can just block all the relays that don't respect this. It's similar to how virtually every relay accepts event deletions.
This is important progress.
One of the most important NIPs has been merged. π
https://github.com/nostr-protocol/nips/pull/1256
View quoted note →
Relays generally do not want to piss off users. It's the same reason most people search sites delete (or at least hide) your data if you ask.
Have any relays (and clients) implemented it already?
and its already implemented and ready to use on: wss://jellyfish.land
π«‘πͺΌ
and its already implemented and ready to use on: wss://jellyfish.land
π«‘πͺΌ
One of the most important NIPs has been merged. π
https://github.com/nostr-protocol/nips/pull/1256
View quoted note →
we fully respect it. π«‘πͺΌ
and its already implemented and ready to use on: wss://jellyfish.land
π«‘πͺΌ
View quoted note →
I love this one. Thank you @Vitor Pamplona
One of the most important NIPs has been merged. π
https://github.com/nostr-protocol/nips/pull/1256
View quoted note →
Nice.
Can this be reversed? What is unrequest vanish?
Ok, Iβm biting. How do I make my account vanish? (iOS or Web)
for ios i think @nos supports it.
ahead of time supporting. π«‘πͺΌ
One of the most important NIPs has been merged. π
https://github.com/nostr-protocol/nips/pull/1256
View quoted note →
There is a WIP pull request in nostr-rs-relay to support it π

GitHub
WIP: feat: Support NIP-62 by TheAwiteb Β· Pull Request #228 Β· scsibug/nostr-rs-relay
Close #227. This PR supports NIP-62
There is a WIP pull request in nostr-rs-relay to support it π

View quoted note →
GitHub
WIP: feat: Support NIP-62 by TheAwiteb Β· Pull Request #228 Β· scsibug/nostr-rs-relay
Close #227. This PR supports NIP-62
Why most important?
Btw, it's a quite dangerous NIP, a bugged or malicious client can definitively nuke a your profile just using a remote signer. Scary.
I would at least add a delay to the final action (e.g. 24 hours) and a mechanism to undo the request.
Thanks

How did you solve for "Relays MUST ensure the deleted events cannot be re-broadcasted into the relay."?
Seems like a burden.
GDPR.
Rebroadcasting seems to be the elephant in the room... Clients of readers can push your notes to relays you don't want.
Appeasing EU tyrants is important? Do governments have to comply with GDPR or is it just for the serfs?
The internet is forever
You'll never truly fully delete anything!! Even a like!! π³
you can make a funny website with animals that supposedly generates funny bears in the feed based on your friends list, but in reality, it will nuke the profile π€£
jellyfish uses immortal as it's software.
we have 2 layer of protection for this issue which help us to stop double processing of an event, stop rewriting of deleted and vanished events.
1. a redis bloom filter which keep track of all events seen by relay. so if someone send an already processed event, we will reject immediately. so, a deleted event is a event that were processed in past!
2. we don't delete a record on mongo db, we update it and remove all fields of it except its id. so it's basically just a nonsense hash. when someone try to write it again, (if we lost redis data for any reason.) we don't write duplicate ids on database and write operation will fail.
you can take a look at code:

GitHub
GitHub - dezh-tech/immortal: An advanced Nostr relay implementation.
An advanced Nostr relay implementation. Contribute to dezh-tech/immortal development by creating an account on GitHub.
overall it's not too complicated.
what about posts that were already used to train ai?
We support it in @nos!
Nope. Notes still exist. I am assuming that some relays donβt support it π©
only some relays support it. on jellyfish we completely respect it. only a small fraction of relay would respect deletions and request to vanish.
be aware where you publish your data!
Thanks. I guess Iβm heading back to where I was just before Nostr: no social media.
I had hope. May the good devs win this one. More white hats, less VCs.
I know I wonβt resist checking back in a year or two to see how it all evolved.
what is your reason for living?
Should be called "Prefer to vanish/disregard" as nothing is truly gone once published online.
As with everything it is a multitude of small things that influence my decisions⦠but:
On the surface Iβd say I wasnβt able to find ways of using it that fit my needs/wants. I seek creative collaborations I guess. I enjoyed my time on stemstr but that βdiedβ. I donβt see media being taken seriously yet. The echo chambers I fell into have a tendency of rubbing me the wrong way.
On the deeper side Nostr made me understand that my fascination with Bitcoin has more to do with Game Theory than Cryptography. There are no incentives on Nostr to play fair. Not for the relays, not for the clients, not for the users.
Add to that the hypocrisy of major players in this space, shouting that V4V is the only way all while signing investment contracts for clients and media players.
Monetization has to be sorted out. Sats have to flow and being redistributed constantly to participants and infrastructure. 
