Replying to Avatar rabble

If we want Nostr to truly protect privacy and resist censorship—like when X faced a government ban—we need to stop relying on relays with known IPs or domain names.

We need encrypted traffic between clients and servers by default. That means Tor (and networks like I2P and Nym) should just work right out of the box, ideally without leaving the mixnet where traffic could be exposed at the exit node.

💡 A lot of relay operators are already running Tor onion services, which is awesome—but we need to make them easier to discover and use. If a public relay becomes unavailable, we should be able to switch to the Onion service version seamlessly.

What do we need to do to make this happen? First, it’s about getting Nostr relay software to publish the Onion address when it’s set up. Then, it’s about getting clients to handle alternative transports like Tor or I2P natively, letting users choose between IP (TCP/IP), Tor, or other options.

We could also explore mapping DNS records to onion addresses or including the info in HTTP headers. But maybe the most straightforward approach is extending NIP-11 to include alternate transport details so that everything's baked into the protocol.

What do you all think? How can we push this forward? Let’s brainstorm and figure out the best way to support these privacy-preserving networks and keep Nostr resilient. I think we need Tor support in native clients where users can turn it on with a single click. Or maybe even have it attempt Tor as a fallback when the normal way of connecting fails.

This isn’t a big change current relay info ospec here: NIP-11 https://github.com/nostr-protocol/nips/blob/master/11.md

Good call, @Rabble.

I run a nostr:npub126ntw5mnermmj0znhjhgdk8lh2af72sm8qfzq48umdlnhaj9kuns3le9ll and their built in marketplace’s #Nostr #relay application with a private relay set up. I’ve whitelisted my npub for my app usage to allow writing to it.

But, I can’t seem to use it.

I use @Nos.social , @Primal , and @Nostur on iOS, and @NoStrudel on the Start9. Among the iOS clients I can’t get the ws:://***.onion address to work in my relay settings, nor do I know where my iOS apps will default write my posts to.

I also want my relay to permanently store my content. But I don’t know how it can be configured to do that.

Would love more clarification on how to set this up.

Reply to this note

Please Login to reply.

Discussion

As far as I know Amethyst has support for accessing onion services via orbot’s tor service but the rest of the nostr apps don’t yet.

some apps work with orbot running and the app tunneled tunneled through orbots VPN, like 0xChat for the start9 private relay.

I have the same problem and posted about it previously. I cannot access my relay on Start9 while using iOS Primal because it won’t accept the ws:// address. If you try iOS Damus you will be able to add the ws:// address then use your relay with Orbot running. I hope that changes are made in Primal because it’s still my preferred client right now. My work around is to use Damus and Orbot when I want to post then go back to Primal when just looking around.