- Inconsistent user experience when tagging event and user IDs in various clients. Some clients support @note ID and @npub, some nostr:note and nostr:npub, some use nevent or naddr or nprofile. You may tag a note or user in one client, and half of the other clients don’t render it.

- In several clients, there’s no way to link to other events in a note without them being rendered inline in your event. This makes for some very long notes or long form articles if you link to multiple other notes. There should be a user setting to disable or enable that in your client, or a way to simply link to another note that doesn’t generate an inline preview in your event. Imagine if every hyperlink on a webpage rendered the full page it was linking to inline in the middle of a paragraph.

- A request to DM someone should cost an amount of sats defined by the user you’re requesting to DM.

- There’s no way to transfer your existing account to a new key pair.

Reply to this note

Please Login to reply.

Discussion

I'm starting to see a pattern here with tagging, both users and notes.

💯 It’s such a basic user activity to reference/tag another user or note. It really ought to just work, no matter which client you publish or read from.

The @ notation is the non-standard one I believe.