Damus
calle profile picture
calle
@calle
Nobody else seems to care but I think nostr finally needs a Hash Chain event kind or tag that is enforced server-side:

- To add a new event to the chain, you MUST reference a previous event. If the referenced event does not exist, you get an error.
- Only one event can reference another event. If an event has already been referenced before, you get an error.

IMO (almost) solves the biggest issue with nostr which is the fact that you never know if the data you have is complete and it allows atomic updates of data. Suggestions for improvements of this idea welcome.
20
calle · 15w
nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75sprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszythwden5te0xy6rqtnxxaazu6t09uqs7amnwvaz7tmj9enrw73wd9hj7zq9s8u this could make nip60 actually work
Raison d'État · 15w
PLEASE NO! This is what SSB does, and it exacerbates network flakiness. That be why I'm here...
Nusa · 15w
This is a Git-shaped problem. You mught not need a new kind. You want a relay-distributed repository with deterministic branch management: content-addressed objects, explicit parentage, fast-forward rules, detectable forks, and a current tip that relays can announce.