Mark on Nostr: I like the kind ID. Since it is just json instead of e.g. uint16 its a bit counter ...
I like the kind ID. Since it is just json instead of e.g. uint16 its a bit counter intuitive.
But you need to look up a ID instead of just inventing your own tag (or worst of all: namespaced tags) for your protocol. This has a huge impact on how new kinds are discovered.
Published at
2024-06-18 14:05:40Event JSON
{
"id": "b42de2567b78339ac16b085024298b33b5db2c180b23ce7ba80b3f9ae55ab6dd",
"pubkey": "bd4577608cd572c7d0625e48ac020aefccff9c05396b00c2515221b49ba16fbc",
"created_at": 1718719540,
"kind": 1,
"tags": [
[
"e",
"b12bdc8094233b9859d74099bf998fac5bb12ee33822af838dce593c9f5b1e20",
"",
"root"
],
[
"p",
"d0debf9fb12def81f43d7c69429bb784812ac1e4d2d53a202db6aac7ea4b466c"
]
],
"content": "I like the kind ID. Since it is just json instead of e.g. uint16 its a bit counter intuitive.\nBut you need to look up a ID instead of just inventing your own tag (or worst of all: namespaced tags) for your protocol. This has a huge impact on how new kinds are discovered.",
"sig": "ffcae38d75ffe514e106395327be47707d9ada20a28e4820f48868752e4770430fe6aa27e3cd13440dc5f955cd045a3d5961e8d5715bb1aeb795e8748c364298"
}
