Yay! Stories circles are coming to nostr

Ah shit, this deletes everything. Disregard .

this would be great

I fully support the right to vanish / NIP 62 #grownostr

I support this as well, despite no guarantees on compliance obviously, a mechanism like this should exist.

Imagine robbing folks of all the things you taught them in your notes, and all that wasted time, effort, and value on your end, GONE. Delete, Nuke, Right to vanish, w/e you wanna call it, its essentially rugging the community of the value you've provided. Would sats earned on notes be returned, or would those get rugged from the community too? 🤣

@OceanSlim any chance grain will include support for nip-62?

I'm sure eventually. Maybe next after 42. I saw this earlier this morning and also thought it was important.

Ideally it would be merged before I implement it.

Also:

If its a legal requirement, then government and other criminals have to comply? Look, I'm all for honouring people's wishes, but it would take me all of an hour to spin up a searchable store-forever client. Any threat actor who can't do this isn't actually a threat actor.

legally binding to what?

The relay, as a service provider.

That actually sounds like a privacy nightmare because it's easier to get a relay to delete your note, than to get every npub to do so. That's already an issue with SimpleX. Full distribution is not always better than decentralization.

This NIP doesn't actually change the existing delete functionality, it just pushes the work of deleting each note in a batch process onto the relay and adds an air of legal formality that can't be easily enforced. Solution without a problem, that just adds complexity for relay operators, IMO, but whatever.

She probably skimmed through it on fast forward and came to a conclusion as she does about everything. meh. elites

I listened to it. Doesn't explain how this architecture would allow asynchronous access to information on the relays, since it is merely relayed, instead of stored. Everything in real time, with no online record? Interesting for DMs, but not for normal notes.

Clients can simply implement a "nuke my npub" button, like I think Damus does. This just turns the button into an event and saves clients a function. 🤷‍♀️ Maybe it's more efficient, but hardly. If relays aren't honoring deletes, that's a different issue.

In expressing our thoughts and conducting ourselves in this ever-evolving world, it is of paramount importance to consider the potential consequences of our actions, both in the immediate future and in the long term. The words you have spoken serve as a poignant reminder of the significance of prudence and vigilance in all that we do. Just as the fashion choices of the seventies may have had unforeseen implications for the women of Iran, so too can our own actions and decisions have far-reaching effects that we may not be able to fully anticipate at the present moment. It is therefore incumbent upon us all to exercise caution and to consider the potential ramifications of our choices, so that we may avoid any regrets that may arise in the years to come. In this spirit, let us strive to act with deliberation and thoughtfulness in all that we do, and to always keep in mind the potential consequences of our actions. For, as the saying goes, an ounce of prevention is worth a pound of cure.

Maybe government will comply, but when governments have a "proxy" government like US have Israel gor example to spy on US citizens this whole thing is great idea but I'm certain there will always be hording relays which will not comply to NIP-62

Yea that I get. But 'legallly binding' implies some sort of law or that a contract was signed. That is what I am asking

Depends upon the jurisdiction you're in and/or the server is in. Germany has the DSGVO, which applies fines for failure to delete. I wouldn't implement this, if I were a relay operator. I'd do "best effort" to show good faith, but not make promises because it opens you up to a lawsuit, if your program has a bug.

Ah ok. Makes sense now. Thanks🙏

You seem to not know, that there are already relays that collect all data on the BCH blockchain. Nostr is a public network.

Storing Delete Events for each note when the user wants o delete the whole account is a burden to any relay. My delete events alone are already 5 MBs or so. On the enforcement side, as a person manages HIPAA-compliant data in Nostr relays, I strongly disagree. Enforcement is just one fuck up away.

Okay, yes, this could hit the OtherStuff, since they often have to be audited or certified. That's a good argument.

Didn't realize the data size.

Seems like an inefficiency, to have to keep everyone's delete events forever. Even this change wouldn't completely solve for that, as some people are rotating fast through keys or auto-deleting on a script, but not "burning" the npub. Maybe we should make more use of NIP-40. If someone is delete-happy, couldn't they just have a client setting that causes their notes to expire after about 3 months. Then you don't have to retain an event, after deleting.

GitHub

nips/40.md at master · nostr-protocol/nips

Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.