Event JSON
{
"id": "8dfc41615c4b2e17e9f1867858ec120d9b50292ffee2319820ad3fe215311cca",
"pubkey": "3f68c31732066fc0cb565d450f7adbf57a0bc0ae8ea187922758b7a5285de638",
"created_at": 1723582887,
"kind": 1,
"tags": [
[
"p",
"3f68c31732066fc0cb565d450f7adbf57a0bc0ae8ea187922758b7a5285de638"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
],
[
"e",
"2b1ce44d1980e023ab8e5e0beca2ba2bec31d29b0be890ba1f4e503ffc011661",
"wss://relay.damus.io",
"root"
],
[
"e",
"dd1da9e6f4ec19a39b070aaa37c9e90666459860ace10da647e1c94f95864c14",
"wss://junxingwang.org",
"reply"
],
[
"t",
"recurring"
]
],
"content": "Definitely. I guess what I'm wondering is what advantages a nostr-specific cal format gives us. e.g. starting from scratch has meant we don't get recurring events right away (something iCalendar already supports): https://github.com/nostr-protocol/nips/blob/master/52.md#recurring-calendar-events",
"sig": "c728dd2a9c1923715a478a941f604094dc0716f00276dca5d9c0a157731eb71eef9617f425f6cbff4aed426c17a315a1e563956b5598256243c3b709c0a7f572"
}
