Oddbean new post about | logout
▲ ▼
hodlbod | 9 days ago (raw) | root | parent | reply | flag +3 
 I agree, but I also think that nostr has adopted mutable state, for better or worse. I'm more concerned now about the complexity that this introduces to nostr's most important event kind. It's one thing for blog posts to support edit, which forces complexity onto only long-form clients, it's another thing to force everyone to support it.
▲ ▼
jb55 | 9 days ago (raw) | root | parent | reply | flag +1 
 Definitely icky, but users have needs 🥲
▲ ▼
mleku | 9 days ago (raw) | root | parent | reply | flag 
 i think we just need to put textnote and article kinds into the "replaceable" basket with a tag `["replaces","eventid"]`

specifically, if a kind 1 or 30023

hold on, articles are already in the replaceable number range

so, already kind 0 is replaceable, so is kind 3 (follows), it's just a matter of a tag i think? maybe even just use `d` like the rest?
▲ ▼
hodlbod | 9 days ago (raw) | root | parent | reply | flag 
 I think this is a possibility. Just get rid of ranges entirely and make everything replaceable.
▲ ▼
mleku | 9 days ago (raw) | root | parent | reply | flag 
 yup, and it's not hard for relays to adapt so they usually just send teh new version, but if the new version has a "replaces" tag you can ask for that event by ID and it has etc back to the first
▲ ▼
mleku | 9 days ago (raw) | root | parent | reply | flag 
 also, i don't think `r` is used yet? or at least not `R` which could become the standard

btw, technically such a scheme makes it a blockchain 🤣 🧱
▲ ▼
mleku | 9 days ago (raw) | root | parent | reply | flag 
 it would make finding them a lot simpler too, i should point out, and you can put both tags in the interim

it would only take me a few hours to add this function so that it gives back only the newest of a chain of events with replaces... just kind and pubkey has to be the same