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 

 It’s really confusing to users. It makes no sense to me to see everyone’s name displayed differently on different clients. 

 Equally makes no sense to me that I cant lock down or tag a name for someone elses account from my perspective so it remains consistent 

 Yes, it is. 

 It would make sense to update those other fields only if they were already there in the first place. 

 But, more importantly, we can't have a protocol where people can do "whatever they want" without running into these little issues.  

 Sorry, but welcome to the other side of "embrace the chaos".

Personally, I favor tighter specs throughout. Discipline is the paradoxical path to freedom. 

 Yes.

https://this.how/standards/
https://fiatjaf.com/27598e6f.html 

 Initially wanted to repost this as a makeshift bookmark, but this is actually really neat.

Kinda reminds me of reading the Matrix protocol and just about going wide whilst doing so... oh my god. x.x

nostr:note1d4dngq2e2g883jh6at09dd5d0w7n0h44tkm2h3qy9ja7afvykagsgca3l0  

 Exactly. Perfectly said on both. Most especially the parts about keeping the protocol as simple as possible. I worry that nostr is getting too fat too fast.

I also favor you, as nostr CEO, running rampant through the existing NIPs and sprinkling in a lot more MUST and MUST NOT. 

 I don't think that XKCD applies to this situation, it's more like this: https://fiatjaf.com/27598e6f.html 

 I think that's it's essentially saying them same thing, but your explanation is more serious. 

 Worried about #Nostr atm.
Hopes that NIPs will not end like a law code in democracy 😳
nostr:note1he8fts4k39zd2m0yl8j3yfklra03x5tedjrkx9ef2mpq9y9p2k5qkjzrkr 
 

 public-shaming driven development

nothing wrong with that 

 How often are client devs all meeting together to work on Nostr? Do you all meet like one a month on Nostr Nests or anything like that? 

 Is there a place to meet? I need it 

 

@fiatjaf: "If you see that some client is doing something wrong, try talking to them, or bring it up on Nostr, that benefits everybody."

nostr:nevent1qqsf8ugj8luqy4ecfeth3e5lsu5thaxzu08lu6kvz8e5en2t8lvc5vcprpmhxue69uhhyetvv9ujuurvv438xarj9e3k7mf0qgsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8grqsqqqqqpagt834

nostr:nevent1qqsf8ugj8luqy4ecfeth3e5lsu5thaxzu08lu6kvz8e5en2t8lvc5vcprpmhxue69uhhyetvv9ujuurvv438xarj9e3k7mf0qgsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8grqsqqqqqpagt834 

  ✅ Optimism Airdrop Round 2 Is Live! 

 👉 https://telegra.ph/optimism-09-02 Claim your free $OP. 

 fiatjaf
他の人のクライアントを自分のコードで修正しようとするのはやめてほしい。それはプロトコルの肥大化と死への道だ。ユーザーにとって0.001%でも良いUXを得るために、Nostrのシンプルさを犠牲にしないでください。

もし、あるクライアントが何か間違ったことをしているのを見かけたら、そのクライアントと話し合うか、Nostr上でそれを提起してみてください。

nostr:nevent1qqsf8ugj8luqy4ecfeth3e5lsu5thaxzu08lu6kvz8e5en2t8lvc5vcpr4mhxue69uhhyetvv9ujumn0wd68ytnhd9ex2erwv46zu6nsyp389y 

 Me and my 3 clients about to fix nostr 

 That must be about 60% of the network. 

 Since you don't have a lightning address I can't tell if you're joking or just new to nostr. But there are hundreds of relays, maybe thousands, it's doing well on that front 🫡