SilberWitch on Nostr: Any event type. It's content-agnostic, as we've already come up with working examples ...
Any event type. It's content-agnostic, as we've already come up with working examples for MP3s and stuff. Can also have different types of data in one. Like text interspersed with videos or graphics. Or indexes within indexes, to create a hierarchy, like in a ToC.
>>
Kind 30040 MUST have events listed in e tags in the order that they should appear, in the client. The events may be any already-existing events (including nested kind 30040s).
<<
Like so:
Published at
2024-11-22 18:41:09Event JSON
{
"id": "92363ef0aa5aa048524ab167adf4cec5aa0dfde65ffc78c66d9056d6c359e7f4",
"pubkey": "fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1",
"created_at": 1732300869,
"kind": 1,
"tags": [
[
"e",
"1d69aed16457f2f3e54ace738d179abdb309987fd438a79f564c5339e36f3fbd",
"wss://theforest.nostr1.com/",
"root"
],
[
"e",
"fa64c5c6fc3687a954c8bc56d201636029962a97bac6a2343df6f9b1892a274c",
"",
"reply"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c",
"",
"mention"
]
],
"content": "Any event type. It's content-agnostic, as we've already come up with working examples for MP3s and stuff. Can also have different types of data in one. Like text interspersed with videos or graphics. Or indexes within indexes, to create a hierarchy, like in a ToC.\n\n\u003e\u003e\nKind 30040 MUST have events listed in e tags in the order that they should appear, in the client. The events may be any already-existing events (including nested kind 30040s).\n\u003c\u003c\n\nLike so: \nhttps://image.nostr.build/100063f24c09d7a22ff102446eb419fb61f91446423e88fe8a57e98a4d7b44ed.png",
"sig": "9c71448717d42b561fe87a3582c3b0cf10e3cc499ebeeee2d4a707860514f1ca2359033e1ef6e9c50fe6ea08ecff93f03abbf778f9ded489eb48c42f3bac3c30"
}
