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
jb55 1y ago

now there is discussion to make @nevent a convention/design nip, but bleh, more complexity 🥲

Reply to this note

Please Login to reply.

Discussion

Avatar
elsat 1y ago

Is this a yes to design NIP workshop at nostr:npub1nstrcu63lzpjkz94djajuz2evrgu2psd66cwgc0gz0c0qazezx0q9urg5l

Thread collapsed
Avatar
daniele 1y ago

No please

Thread collapsed