Put the nostrdb on a relay app, then. You don't even need a UI for that :)
Login to reply
Replies (2)
it would be slow if it was in a relay app. you pay the cost of sending it over a socket, parsing, etc.
with nostrdb its a single btree lookup into memory with a cache aligned struct pointer
Split it in two and make the relay available and the cache as a separate lib. It would be similar to what I and the web stacks are doing these days.