Thread

Planning to use service workers in the browser? Also, are you thinking one connection per relay? Most Nostr apps use multiple relays simultaneously. How will it handle deduplication on multiple overlapping data streams from different relays?

The idea is the bulk of the apps nostr logic (connections, event storage, subscriptions) are handled in a service worker so that the main rendering thread in the tabs don't lock up so much. also in theory this should be more efferent since the service worker can handle the signature verification and duplicate events from multiple relays

Makes total sense. What will you use for storage? IndexedDB?

IndexedDB is the reason I'm looking to make multiple threads. getting sick of it freezing the main thread. but its built-in to all browsers so it makes sense to use it as a default Then maybe have an option to detect and use the local nostr-relay-tray or a SQLite WASM database