Oddbean new post about | logout
▲ ▼
Nostr Dev Team | 3 months ago (raw) | root | parent | reply | flag +1 
 Isn't the whole point of a replaceable event that it should be replaced (by the most recent one)?

See NIP-01 (only the latest event MUST be stored, older versions MAY be discarded)
▲ ▼
KoalaSat | 3 months ago (raw) | root | parent | reply | flag 
 Correct, but this bug was removing ALL records on DB with exception of the most recent one 😅
▲ ▼
Nostr Dev Team | 3 months ago (raw) | root | parent | reply | flag 
 You mean, events with different a-tags / kind numbers?

That would be a (serious) bug
▲ ▼
KoalaSat | 3 months ago (raw) | root | parent | reply | flag 
 Only in the group of type >30000, I was constantly sending events with different "d" tags and freaking out because on every try, I only got 1 result for: ["REQ", "111", {"kinds":[38383]}]
▲ ▼
KoalaSat | 3 months ago (raw) | root | parent | reply | flag 
 *ALL records with type > 30000