Querying stuff from relays is not trivial. I am currently using 8 separate layers of abstraction to build feeds:
1. A websocket wrapper
2. A message buffer to avoid locking up the ui, sending too many concurrent reqs, and handle pausing messages while negotiating auth
3. A target interface which allows for different relay implementations like multiplextr or a local relay
4. An executor that works with a target to actually do stuff
5. A subscription object which queries multiple relays, aggregates results, and tracks which relay an event was seen on
6. A cursor object to perform windowing for a given relay
7. A load function which throttles and merges concurrent filters with a timeout
8. Feed/context loaders that take a filter, listen with a subscription, load using cursors, and fetch context with loaders
If relays always returned results in order it would simplify and optimize some of this away. But it really is irreducably complex.
hodlbod
npub1jl…jynqn
2023-09-16 14:21:48 UTC
Author Public Key
npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqnPublished at
2023-09-16 14:21:48 UTCEvent JSON
{
"id": "2cf8af0ebe81133e8509d28f60e390229db0426b465c2dd119e5c92a906c3219",
"pubkey": "97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322",
"created_at": 1694874108,
"kind": 1,
"tags": [],
"content": "Querying stuff from relays is not trivial. I am currently using 8 separate layers of abstraction to build feeds:\n\n1. A websocket wrapper\n2. A message buffer to avoid locking up the ui, sending too many concurrent reqs, and handle pausing messages while negotiating auth\n3. A target interface which allows for different relay implementations like multiplextr or a local relay\n4. An executor that works with a target to actually do stuff\n5. A subscription object which queries multiple relays, aggregates results, and tracks which relay an event was seen on\n6. A cursor object to perform windowing for a given relay\n7. A load function which throttles and merges concurrent filters with a timeout\n8. Feed/context loaders that take a filter, listen with a subscription, load using cursors, and fetch context with loaders\n\nIf relays always returned results in order it would simplify and optimize some of this away. But it really is irreducably complex.",
"sig": "c4ed5d618905170509db7adc7b183c27e83d08164ba3649bba7dad62ee1bfe8825f5540106db59400f44bbca2827672401b667e532219dac6cb18573c3cd5d7d"
}