nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn have you thought about caching stuff locally and exposing that cache as a relay interface, so you can just seamlessly plug it in all other parts of the https://coracle.social/ code that connects to relays? Is this a bad idea?
NDK does something like that; it doesn’t expose it via web sockets but when you query anything it’ll query the cache (if you added a cache adapter) first (or only/parallel/skip, defaults to
For the user its all the same (though you can query if the event came from a cache or the relay)
NDK is such a marvel.
