Replying to Avatar Dikaios1517

I have taken to manually typing the "nostr:" prefix for all Nostr URIs since it is far more consistently handled by various clients. Leave it off and you may or may not get the desired result, depending on the client.

That said, I think client devs should be better about recognizing and handling URIs that are missing the prefix. Can't really count on that, though.
Avatar
db42 6mo ago

Here’s a linked article nostr:naddr1qqd5jmn5wfhkgatrd9hxwt2vdahxwen0wfkj6cm80pengagpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgq3q5ypxpg429uyjmp0zczuza902chuvvr4pn35wfzv8rx6cej4z8clqxpqqqp65w9zu5tz

Reply to this note

Please Login to reply.

Discussion

Avatar
Dikaios1517 6mo ago

Did ypu add the "nostr:" prefix manually? If not, whatever client you used added it for you.

Avatar
db42 6mo ago

Yeah did type it in manually. But an app I’m working on didn’t seem to work correctly across those 3 clients when doing quote post with the “nostr:” in them. I’ll do some more testing.

Avatar
The Bullish ₿itcoiner 6mo ago

Hey, thanks for sharing my article. I’m still learning what the best practices are so let me know if you know of any good resources.

For example, I noticed in Primal when I copy the note ID, I get a string that begins with “nostr:nevent”; whereas in Damus, the string begins with “note1”. Which one is more preferable?

Avatar
db42 6mo ago

That’s a strange one. I believe in the nip specs it says to use “nostr:” so I think maybe Damus is incorrect in this case. But I’m sure they’re doing it that way for some reason.

Avatar
Dikaios1517 6mo ago

"nevent" is preferred, as it typically includes relay hints, while "note1" does not. Both should include the "nostr:" prefix, just like a standard URL should include the "https://"

Avatar
The Bullish ₿itcoiner 6mo ago

Ah thanks! I’ll try to incorporate that into the clients I make. 🤙