Yeah, that's why I created this NIP, to help people rename and group their contacts.

GitHub

Contact Cards by vitorpamplona · Pull Request #761 · nostr-protocol/nips

Uses unbound lists to create events that define the relationship between two pubkeys in a public or private manner. Read here

Unfortunately we never fully implemented it.

What if we took npubs and mapped them to something a human can read and recognize, then optionally display that somewhere? Doesn't have to be one to one

Nah

This is another thing a robust tagging system would be good for Clients could automatically tag an npub with every name they're seen with, and users could tag the npub's other known names and npubs, and you could have a tag on any npub showing why you followed them

Why not just add the name they have to their npub only when they have been added to the follow list. It would avoid keeping a long history list of name changed. When we follow someone, we remember the name at that moment. A icon-tag could be used to say the name have been changed (in the follow list) And if we go on the profile we would have the last used name/changes.

We are using it in Chachi and Zapchat

Yeah, Nostur does this

This would need to be done at the client level, which means you would see some clients implement it while others don't. As far as Nostr as a protocol is concerned, when a user updates their profile note (kind 0) relays are permitted (and expected) to delete any previous version.

Great idea 💡