Event JSON
{
"id": "f1213be54d15d88eae18d4cd4edbc4be77f3a5905066c4d6a7ac300299f8f6be",
"pubkey": "dc4cd086cd7ce5b1832adf4fdd1211289880d2c7e295bcb0e684c01acee77c06",
"created_at": 1726334687,
"kind": 1,
"tags": [
[
"e",
"3fbba0ec563849e0904f2d11a908ae89fa6c68e4e41a07ec75b665b532831c8e",
"",
"root"
],
[
"e",
"103946f2a21ccdeb1f259cece152d529db712f81db316b0a399f7ca1ac7f8b98"
],
[
"e",
"ff3b7cfa30ad168b41231d3b5d2abea571d673bb0d8e0d8d5abe343b04e4a9d7",
"",
"reply"
],
[
"p",
"fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1"
],
[
"p",
"dc4cd086cd7ce5b1832adf4fdd1211289880d2c7e295bcb0e684c01acee77c06"
],
[
"p",
"70122128273bdc07af9be7725fa5c4bc0fc146866bec38d44360dc4bc6cc18b9"
],
[
"a",
"30617:fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1:Alexandria"
],
[
"a",
"30617:dc4cd086cd7ce5b1832adf4fdd1211289880d2c7e295bcb0e684c01acee77c06:Alexandria"
],
[
"a",
"30617:70122128273bdc07af9be7725fa5c4bc0fc146866bec38d44360dc4bc6cc18b9:Alexandria"
]
],
"content": "Yeah, just allowing for a multitude of ways for human navigation. The general case would be to remove the '{noun}:' and just find anything matching the sane string across the categories.\n\nKind of an aside, but I'm wondering if it would make sense backend-wise if we paired an optional db for caching on relays we want to associate with to improve performance. I'd imagine without the db search performance would degrade as events increase.",
"sig": "561a6045940e99e4cd703f5243b27966070b48261e57d2bfef25e703c416a0088ca9cf4325c2a2a519083899fb0df4f0705bb98abcc3e1d68de5d281ad91489a"
}