{ "id": "d518e8f58b49eaa62a4bcdc9ef6b15776c1bca288338788a2f074a79f5a2bc18", "pubkey": "fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1", "created_at": 1716362114, "kind": 1617, "tags": [ [ "a", "30617:a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d:nips", "wss://relay.damus.io" ], [ "r", "f25c7e672c23ca5463fa5c0fcb5e5f424d956862" ], [ "t", "cover-letter" ], [ "t", "root" ], [ "p", "a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d" ], [ "p", "397417f84734d01c2e9bebdfb68fadaa0099b92e6831ff3f4e1ed54ec893edef" ] ], "content": "From 8b4c82323c0c18faa30b856a8f57409ff0f0ab36 Mon Sep 17 00:00:00 2001\nSubject: [PATCH 0/1] Allow for a more expansive and updated event kind list\n\nIt is currently a real fight, to grab one of the coveted NIP files, in order to document a new event kind. As the NIPs are limited in scope and number, that means lots of events will remain undocumented and simply show up on relays and clients, with no central place for them to figure out what they are looking at and how to properly handle it. At the same time that simply making the README.md in the NIP repo a Wiki doesn't solve for the fact that this list will eventually be quite long and frequently-edited, so it deserves to have its own Wiki page. I suspect that we could actually remove some of the obscure NIPs and simply list their event kinds here, with a link to some description elsewhere (perhaps in the client repo where they are implemented).", "sig": "6232c61218ddf115b35caf1b95fdd3361e8f3ea829f97c12fd8e74f4b00f4200c46c48b9af61df38402973b9d64ffcef2173c4341dd57e19256caf9c4134a191" }