Why didn't you use "display_name" like Damus then? Or is Damus doing "displayName"?
Discussion
We save the same value on both displayName and display_name. We also save username and name the same "username" value.
But we display only one name, the first in this sequence: displayName, display_name, username, name.
This is so bad.
How so? client choice
Why not also "handle", "nickname", "display", "DisplayName", "nick_name", "user_name", "user", "Name"?
good ideas. make the profiles more robust. id also add alias, gamerTag, lolliTag, instagramHandle, MySpaceName, nintendoFriendCode
still up to clients how and what they render.
still up to relays on what they will store.
thanks for choosing a data structure that is open ended to accomodate this.
You must be trolling so I will start ignoring you.
Why would you like to add those things?
I was being facetious about them being in kind0. Its the result of anything goes without constraints at the relay or client level. We already have NIP32 for labeling to accomodate some of these and the core of kind0 should be streamlined for consistency
Yikes
We need relays to block metadata events with "username", "handle" and "displayName" fields by default on https://relaying.io/, sir.
