Oddbean new post about | logout
▲ ▼
Vitor Pamplona | 21 hours ago (raw) | root | parent | reply | flag 
 The issue is that if clients are doing something with a field, it should be listed and upgraded on the NIP. 

There are over 30 fields or so that I have seen on Kind 0s that are not listed there. And it is fine. I am not sure what the extra array does that the current field list wouldn't do.
▲ ▼
Alex Gleason 🐍 | 20 hours ago (raw) | root | parent | reply | flag +1 
 It creates a clear distinction between user-defined fields and protocol fields. User-defined fields are only for display (and only for display in a confined region of the profile), while protocol fields can actually influence the behavior of the account, like set your Lightning address or avatar.

User-defined fields are an amorphous blob the user can do whatever they want with but should not be relied upon in any way, kind of like pronouns.
▲ ▼
Vitor Pamplona | 20 hours ago (raw) | root | parent | reply | flag +2 
 Right, so if pronouns are just listed as a field when the user visits a profile, it works. But if they are added after each person's name in the feed, then it becomes something else.