Understanding is fine, but it’s a UX issue that app devs need to account for. Think of web browsers, if I copy a hyperlink from a webpage in chrome and paste it into the address bar in Firefox, or into another webpage that someone using Safari clicks, it loads the content the user is trying to access. Whatever good reasons there may be for different nostr event ID formats, it kills the user experience when moving between apps, and moving between apps is touted as Nostr’s superpower.
what us the reason for different id formats?
Some of the formats allow for embedding info such as which relay to use to find that event or user profile. I understand it’s useful, but it’s only as useful as its interoperability across apps.
Do some apps not support nevent1? I know lots use note1, which results in failure to load in other apps that adhere more closely to the outbox model.
I’m on iOS. Primal doesn’t support them. I think Damus added support a while back but not sure. Nostur supports them. All of the iOS apps give note1 IDs when you copy them to share.
Oh, but they read them if they're embedded right? note1/npub1 are nice because they're actual ids, but have no routing information embedded. I think we can't use them long term if we want nostr to work (npubs are probably ok because we can check indexers).
Primal does not. At least on iOS.
You have a point. Thinking about ways to make this smoother for users.
Oddbean new post about login | logout