For now I would leave the current event kind number specs as it is. It's more flexible that using NIPs for every possible content-type. But I can imagine there will be NIPs around specific content-types which will extend NIP-01 in the future.
Now all the content-type related stuff can be handled by all Nostr clients and map them to the related event kinds. This could be a very interesting mapping to work out (a visual presentation of kind numbers with content-types).
sebastix / Sebastix
npub1qe3…zefe
2024-05-28 10:27:28
in reply to naddr1qq…txrh
Author Public Key
npub1qe3e5wrvnsgpggtkytxteaqfprz0rgxr8c3l34kk3a9t7e2l3acslezefePublished at
2024-05-28 10:27:28Event JSON
{
"id": "34c12bb66dd1b158ded7455c8a0aa336fee0c3dce97a8c01e23b4ecd8615f0d9",
"pubkey": "06639a386c9c1014217622ccbcf40908c4f1a0c33e23f8d6d68f4abf655f8f71",
"created_at": 1716884848,
"kind": 1,
"tags": [
[
"a",
"30023:df67f9a7e41125745cbe7acfbdcd03691780c643df7bad70f5d2108f2d4fc200:O4kUjmq64LACVhyzN2EhP",
"",
"root"
],
[
"p",
"df67f9a7e41125745cbe7acfbdcd03691780c643df7bad70f5d2108f2d4fc200"
]
],
"content": "For now I would leave the current event kind number specs as it is. It's more flexible that using NIPs for every possible content-type. But I can imagine there will be NIPs around specific content-types which will extend NIP-01 in the future.\nNow all the content-type related stuff can be handled by all Nostr clients and map them to the related event kinds. This could be a very interesting mapping to work out (a visual presentation of kind numbers with content-types). ",
"sig": "645ee6b9991f73dc0d4e9bb6421e70152aaa6b8709f5372dac4c338c6e4ce6d8d89079dc1ef31d3fbd7195c2b11ea9e89247f00c7c61bb6b755d1257305b6ee9"
}