What is Nostr?
cmd /
npub1gg5…ulq3
2024-03-01 06:02:48

cmd on Nostr: I may have found a use case for the abandoned "subject" field that nostr notes had ...

I may have found a use case for the abandoned "subject" field that nostr notes had with NIP-13.

It would be great if there was a standard "content id" with every note, so that you could reference notes by their content, rather than an absolute id.

The content id would be a sha256 hash of the content field and pubkey.

What this would enable is replaceable tags for notes. Imagine you could in-place update the tags on a note, similar to a replaceable event.

This would open up so many possibilities:

- Easily delete a note by adding a delete tag.

- Easily update a note by adding a ref tag to the new note.

- Update a note's metadata based on the comments. This may be good for special protocols (like zap giveaways).

This could also help relays with storage, as they could choose to discard notes with older metadata.

I would mainly want this for a simpler way to delete messages, as the current NIP-09 solution is a terrible burden on clients and not well respected by relays.

What other cool things could you, if you could change tags on a note while also preserving the reference id?
Author Public Key
npub1gg5uy8cpqx4u8wj9yvlpwm5ht757vudmrzn8y27lwunt5f2ytlusklulq3