buttercat1791 on Nostr: More precisely, I'd say that kind 30041 is akin to kind 30023, as they both define ...
More precisely, I'd say that kind 30041 is akin to kind 30023, as they both define markdown content. Kind 30040 is better characterized as an index of kind 30041 events.
I agree with the general goal of maintaining commonality between event kinds insofar as it is possible and insofar as it makes sense.
What I've observed when designing new event kinds (in myself as much as in others) is that the content field seems to demand tribute. Perhaps the data I'm trying to represent *could* fit entirely into key-value pairs in the tags, but then it feels weird to leave the content field empty. If we can give developers, especially those new to Nostr, a correct understanding of the content field, we could create a better "pit of success" for enterprising developers to fall into.
Published at
2024-07-08 01:11:08Event JSON
{
"id": "ea4bc197afd6800fa0a25cad771a561246e8b911a7a71d90eaac411105cc6279",
"pubkey": "70122128273bdc07af9be7725fa5c4bc0fc146866bec38d44360dc4bc6cc18b9",
"created_at": 1720393868,
"kind": 1,
"tags": [
[
"e",
"265f615b4bdf3eef9c4a550430dc08d30510ba049870e6646bab3df0fbfb36c1",
"wss://theforest.nostr1.com/",
"root"
],
[
"e",
"ed70046552e17c23a872fa5a03835cc154dcabdb9493a9635087a9c3ea6275d6",
"wss://relay.damus.io/",
"reply"
],
[
"p",
"fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52",
"",
"mention"
]
],
"content": "More precisely, I'd say that kind 30041 is akin to kind 30023, as they both define markdown content. Kind 30040 is better characterized as an index of kind 30041 events.\n\nI agree with the general goal of maintaining commonality between event kinds insofar as it is possible and insofar as it makes sense.\n\nWhat I've observed when designing new event kinds (in myself as much as in others) is that the content field seems to demand tribute. Perhaps the data I'm trying to represent *could* fit entirely into key-value pairs in the tags, but then it feels weird to leave the content field empty. If we can give developers, especially those new to Nostr, a correct understanding of the content field, we could create a better \"pit of success\" for enterprising developers to fall into.",
"sig": "b6c2ac73629253b44d935c02cde42bafc8a5be82286f42ae95dae3ece1eb8dd2ea30582d4ccceafb903019bb48d2b88a0be8f7c7aae6aaf4499b01188a2008d0"
}