Stuart Bowman on Nostr: So a few months ago I looked into doing this — the problem is that Chrome's ...

So a few months ago I looked into doing this — the problem is that Chrome's manifest version 3 makes it difficult. Previously, in manifest version 2, extensions had essentially a hidden tab that could be used to run stuff until the user closed the browser. But with the V3 changes, Chrome seems to want to force everyone to use web workers that spawn and shut down on-demand, and this makes it hard to write a nostr client inside an extension because the client should ideally maintain persistent connections to relays. If you look in the google groups about this there are a lot of people complaining that the V3 changes are breaking their websocket implementations. Something to consider. Not saying it's hopeless.