@hzrd149 Good morning, sir. Failure to register protocol handler is breaking the load of the Next version: Not the case with the Production version. I believe that it should fail with an error, but not break the entire app. I found this error trying to access the Next version of noStrudel on Firefox through Tor, which led me to having to configure `dom.securecontext.allowlist_onions: true` to fix it. So, it isn't a total show stopper, but still would be interesting to fix, because who knows what else makes it break besides trying to access on FF through Tor, and it doesn't happen with the Prod version (it fails gracefully).

New onion address for the "Next" version of Nostrudel (next.nostrudel.ninja) for access through the Tor network: http://pzfw4uteha62iwkzm3lycabk4pbtcr67cg5ymp5i3xwrpt3t24m6tzad.onion Remember to add at least one onion relay on both inbox and outbox relay configurations, such as ws://bitcoinr6de5lkvx4tpwdmzrdfdpla5sya2afwpcabjup2xpi5dulbad.onion Remember that "Next" is never production ready, but a work in progress, therefore it may contain bugs (for example I had to reload it once for it to load my timeline), it's normal. Looking for the Production version? see: View quoted note → Once again, shout out to @hzrd149 for this fantastic client!

As usual, @Mike Dilger ☑️ was right.

Nostr on Tor works! I just spun up a noStrudel hidden service: http://a2zmtsslt7g7v5shssufp4uuh7wvr7betxglxf4fbtcxpejrvr7qmwid.onion It may take some time to load for the first time, so be patient! Make sure to use only Tor relays on the app, like so: Media upload is, at the time of this post, failing because of some restrictive configuration on the side of nostr.build, so, as a workaround, you may want to upload your files manually to an alternative service that doesn't block Tor, such as https://envs.sh , which will return a link that you can copy and paste on your noStrudel post. Good luck on your Tor adventures!