Oddbean new post about | logout
▲ ▼
hodlbod | 1 days ago (raw) | root | parent | reply | flag +1 
 Eh, nips are for documenting common practices. If clients want to let users virtue signal, it's good to agree on how to do it
▲ ▼
1440000bytes | 1 days ago (raw) | root | parent | reply | flag +1 
 I don't have any issues with pronouns. I care about things that really affect nostr.
▲ ▼
hodlbod | 1 days ago (raw) | root | parent | reply | flag 
 I have issues with pronouns 😂. But do you mean that defining fields in kind 0 affects nostr negatively?
▲ ▼
mleku | 1 days ago (raw) | root | parent | reply | flag 
 IMO the standard has been fixed in place for over a year and mechanisms for extension without breaking many existing implementations is more the issue

most apps will have no problem adapting or ignoring these extra fields, probably, because they are not making any assumptions about the key names in the object in the content field
▲ ▼
mleku | 1 days ago (raw) | root | parent | reply | flag 
 my main issue is just that you don't put things in the nips without having two working implementations. period.
▲ ▼
melvincarvalho | 1 days ago (raw) | root | parent | reply | flag +8 
 It misses the point.  Users should control their profiles, not a centralized committee.  Nostr is a protocol, not a cult.  Let users choose.  Have some defaults, and then users can select a number of extra fields.  For example mastodon has 4, which people like alot.  We can then start to add new things to nostr such as #pubky decentralized dns and true censorship-resistant.  We are far too centralized right now.
▲ ▼
Vitor Pamplona | 1 days ago (raw) | root | parent | reply | flag +1 
 Users can still add whatever they want to their profiles. I don't know why you are saying that a centralized committee is blocking it. Right now we already have 30 or so different fields on Kind 0 events. Just five of them are defined on the NIP. 

There are hundreds of kinds that were never defined as NIPs. This centralization idea you make of Nostr is so strange. I don't know if you are just saying things in bad faith or if you truly don't know how Nostr works.

The NIP is just an interoperability point so clients can understand each other and bounce ideas off each other. It is not a W3C spec.