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.
jb55 / Will
npub1xt…vkk5s
2024-08-13 19:29:59
Author Public Key
npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5sPublished at
2024-08-13 19:29:59Event JSON
{
"id": "98bb9a824ec6ca05f966b4ab835b72c2c1f823439d829ddd4c583c5148de6eda",
"pubkey": "32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245",
"created_at": 1723577399,
"kind": 1,
"tags": [],
"content": "we should have spec’d nostr:nevent… as @nevent… instead. Would have saved a lot of pain and confusion for users and implementors.\n\nIf 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 :[ \n\nfor 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.",
"sig": "743251b8dd8a766704ecc0b877202dccc18978b3a85d29c8ca4ab6688784fe0eef6b7ca23a58c7bf58f4b6144020a45e0ef69671a8527244165b9c70dcd07ee0"
}