Another area of confusion for people is "nostr address".

This was difficult for testers to grasp because they didn't even know what "nostr" means.

This is understandable given the naming difference of clients and protocol.

One solution that I can think of is to rename it to "Unique ID".

It's a more clear term and eliminates the need of having to understand what nostr is right away. They can still discover the protocol over time without this up front confusion.

Here is an example of how I would describe Unique ID input field in client settings:

"Usernames are not unique in Snort. A unique ID is a human-readable address that is unique to you only. This helps friends identify the real you."

Notice I did not use the term nostr, but referred to Snort directly because this is the client that person is using.

To lessen the hand-holding, we can add some additional copy "Why are display names not unique?" with a link to learn more about this concept - and use that to introduce the protocol.

Another solution might be to tuck this field into an advanced settings dropdown. NIP5 DNS-based IDs are not a good solution for majority of people and only come in handy for higher social presence individuals. They can find this field because it'll be more important to them. As for the rest of us, the burden of proof can be through other types of verification as we've all been doing already such as posting on another platform.

Curious to hear your thoughts!