ManiMe on Nostr: Thanks. While this article is rough and lacking many specifics… what it does ...
Thanks. While this article is rough and lacking many specifics… what it does propose is that a single NIP could be designed for clients and relays to structure their own “content types”, without needing additional NIPs and “kinds” to be explicitly defined in the “centralized” repository. It’s not perfect, or even near a complete spec, but it does aim to “increase” the flexibility and freedom for developers. (ICYMI)
Published at
2024-05-28 18:22:47Event JSON
{
"id": "2b4e04d3cb6cf7002ac278c88e667c3ab726a22985b3baa76af614f792e1f41e",
"pubkey": "df67f9a7e41125745cbe7acfbdcd03691780c643df7bad70f5d2108f2d4fc200",
"created_at": 1716913367,
"kind": 1,
"tags": [
[
"e",
"34c12bb66dd1b158ded7455c8a0aa336fee0c3dce97a8c01e23b4ecd8615f0d9",
"",
"root"
],
[
"a",
"30023:df67f9a7e41125745cbe7acfbdcd03691780c643df7bad70f5d2108f2d4fc200:O4kUjmq64LACVhyzN2EhP",
"",
"root"
],
[
"p",
"06639a386c9c1014217622ccbcf40908c4f1a0c33e23f8d6d68f4abf655f8f71"
],
[
"p",
"df67f9a7e41125745cbe7acfbdcd03691780c643df7bad70f5d2108f2d4fc200"
],
[
"client",
"Nostur",
"31990:9be0be0fc079548233231614e4e1efc9f28b0db398011efeecf05fe570e5dd33:1685868693432"
]
],
"content": "Thanks. While this article is rough and lacking many specifics… what it does propose is that a single NIP could be designed for clients and relays to structure their own “content types”, without needing additional NIPs and “kinds” to be explicitly defined in the “centralized” repository. It’s not perfect, or even near a complete spec, but it does aim to “increase” the flexibility and freedom for developers. (ICYMI)",
"sig": "43cb1878ea3165a47a8fccf78ebfde177263f63138c927e0bc3a61b691de2a681d6ef8db829d900161ad948c99027170a2823b2b6be7d05a6ac06403dbed643a"
}
