hodlbod on Nostr: Not by duration exactly, but by timeframe. But I think that's what you meant. The ...
Not by duration exactly, but by timeframe. But I think that's what you meant.
The alternative would be potentially to just list the dates the event falls on in YYYY-MM-DD format, but that's basically just a time hash, and introduces the question of timezones. Another alternative would be to have queries like since/until on tags, but that seems unlikely to get adopted at a meaningful rate.
Published at
2025-02-05 18:19:51Event JSON
{
"id": "ce501cb0aa75eabe85fadc3f996b217a41793481d0068ffdd577afcf96c04fa6",
"pubkey": "97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322",
"created_at": 1738779591,
"kind": 1,
"tags": [
[
"p",
"e8ed3798c6ffebffa08501ac39e271662bfd160f688f94c45d692d8767dd345a",
"wss://cyberspace.nostr1.com/",
"arkinox"
],
[
"p",
"2779f3d9f42c7dee17f0e6bcdcf89a8f9d592d19e3b1bbd27ef1cffd1a7f98d1",
"wss://nostr.wine/",
"tyiu"
],
[
"e",
"b6f343903b87d9856873a01e81ea5c948828d4d66326b9d57139a6e89bbd55a1",
"wss://algo.utxo.one/",
"root"
],
[
"e",
"f3f0de3de1b8f4c2bd6ac282c112d48d4a04a8937127f222afedef565fd6a47b",
"wss://nostr.wine/",
"reply",
"e8ed3798c6ffebffa08501ac39e271662bfd160f688f94c45d692d8767dd345a"
],
[
"client",
"Coracle",
"31990:97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322:1685968093690"
]
],
"content": "Not by duration exactly, but by timeframe. But I think that's what you meant.\n\nThe alternative would be potentially to just list the dates the event falls on in YYYY-MM-DD format, but that's basically just a time hash, and introduces the question of timezones. Another alternative would be to have queries like since/until on tags, but that seems unlikely to get adopted at a meaningful rate.",
"sig": "51388a962609fe32b4b6000fd17e681395ec25f75d70625a0c43378b2394f43807d846ee1298ba65b21a79eda67035c63e798e162c61a0d0e362fcc5eba57bca"
}
