I think clients should display the "name" field and have a separate "username" field if they support that feature. It's not too late to change that.
Discussion
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 would you support that change?
The name and username fields have always been used interchangeably in the past. Both reference some sort of single-word user name tag. Display name was then introduced to be anything the user wanted.
I don't think there is a need to change the semantical difference between the two. I don't opposed it. I just think it's a lot easier to deprecate both in favor of display names.
Damus currently breaks if you leave display_name empty
Can't recover without reinstalling the app
I see your name as display_ name not supported. Is this your way to introduce changes or an interoperablity issue? I use damus with empty name field and never was an issue
Actually it might be whitespace in "username" (which is actually profile.name field) that breaks it
I just tried setting display_name to blank and put whitespace in my name field and nothing seems broken to me. What do you mean by breaks it?
Sorry for the vague bug report. Actually the issue was: when I logged in using my public key, it would pull some old relay list of mine that doesn't connect (1 relay requires auth and 1 doesn't exist anymore).
But also I noticed the app froze when you add a space to username, i.e. nav buttons and the form stop working:
