Seems like low-hanging fruit to get this done while we’re kind of in a new user enrollment lull. nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr nostr:npub1atc6zwsr9nnyn0rq72g2qqznr3x4yhm20g50wsexjukygwrg9atqh0lssy
It's just about picking the names and writing the NIP. Maybe nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 can use his dictator powers to choose which fields should be used for names and what they should mean semantically. I would follow whatever the NIP guidance says.
This is the typical case of too many cooks in the kitchen. We just need to pick which fields are the right ones and update our UIs.
Discussion
While we are at it. Let’s appoint you as the lead nostr PM. We need some strategic guidance.
More than happy to help since that’s my actual job at the Fiat mines.
I think we need Jira on nostr. 😆
Man, you need Steve Jobs to manage the nostr devs. I’ve seen how they discuss implementation. 🤣🤣🤣 I would fail getting them to agree on anything.
