Oddbean new post about | logout
▲ ▼
Rabble | 11 months ago (raw) | export | reply | flag +4 
 Why are Amethyst and Damus using event kind 30000 with a “d” tag of “mute” for their mute lists instead of event kind 10000 which nip-51 specifies as the event kind for mute? Coracle and nos.social are using kind 10000 as the spec says. 

https://github.com/nostr-protocol/nips/blob/master/51.md

@Vitor Pamplona & nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5sWhat’s the thinking here?
▲ ▼
teldon | 11 months ago (raw) | root | parent | reply | flag +1 
 Makes you wonder how many other such inconsistencies there are across the most popular clients.
▲ ▼
Vitor Pamplona | 11 months ago (raw) | root | parent | reply | flag +2 
 Basically, because 30000 took off before 10000. The idea of generic lists and muting being just another one was exciting. These days, we might rollback to saving both or just 10,000, I am not sure. 

With 30,000 your mute list shows up on Listr. 10,000 doesn't show there. So, ups and downs.
▲ ▼
jb55 | 11 months ago (raw) | root | parent | reply | flag +1 
 Yeah i remember at one point this was the recommended way. Why did this change? Whats wrong with 30000?
▲ ▼
Rabble | 11 months ago (raw) | root | parent | reply | flag 
 I think we should either update the spec or update the implementations. I kind of like it being it’s own event type as the spec is written but honestly I don’t have a strong opinion. Mostly I just want us all to agree and do one thing and document it. This is a case where interoperability is improved a lot by consistency.
▲ ▼
badonyx | 11 months ago (raw) | root | parent | reply | flag 
 > With 30,000 your mute list shows up on Listr. 10,000 doesn't show there. So, ups and downs.

Latest version of Listr shows kind 10000 just fine :)