Global Feed Post Login
Replying to Avatar jb55

we should have spec’d nostr:nevent… as @nevent… instead. Would have saved a lot of pain and confusion for users and implementors.

If you do @nevent… in damus it will convert it to nostr:nevent… at the protocol level, but maybe it should have just been @nevent because people try to do this now in other clients and it doesn’t work :[

for what its worth, if you manually type nostr: then the nostr object it should work in all clients, but I don’t think people know that.

Avatar
xtogro 1y ago

learned today, bit @ would be more intuitive

nostr:nevent1qqsqq0mr9gaw6cpn3qrk5fyfvkpczxr2qcz5aqkh8lrnkn47dg62vnqmrzcht

Reply to this note

Please Login to reply.

Discussion

No replies yet.