Replying to Avatar Bowfinger

I tried using tor, but its too slow and a considerable amount of posts cannot be retrieved, probably because the relays dont support it.

Do you have a workaround?

Thanks
Avatar
Mike Dilger ☑️ 2y ago

I don't have a workaround.

I think nostr:npub1sn0wdenkukak0d9dfczzeacvhkrgz92ak56egt7vdgzn8pv2wfqqhrjdv9 has experienced similar issues with his client (iris/daisy/?). A relay doesn't need explicit support for tor, but it mustn't block tor exit nodes. I suppose some relays are run at ISPs which block tor exit nodes by policy. It would be good to determine which relays are like that.

Tor will be slower because the service of onion routing isn't free, and network traffic is the slowest part of modern computing.

Reply to this note

Please Login to reply.

Discussion

72
nobody 2y ago

I will attempt to make sure my relay is accessible via tor this week. That is in line with our operating values.

Are you on my relay Mike?

Avatar
Enki 2y ago

+1 id like to see nostr over I2P as well.

Avatar
Mike Dilger ☑️ 2y ago

I think relays on i2p is a damn good idea

Avatar
Raymon 2y ago

How can you determine if your relay talks to an exit node?

72
nobody 2y ago

Some firewalls block known nodes automatically, and even better I will try to get a proper onion address set up as well. It’s more about testing that it works.

Avatar
Rainer 2y ago

Tor is terrible with websockets, especially with many of them like what a Nostr clients does usually (many relays). Generally, you will never get the full experience with tor and you will always loose events. Btw. I am using a special raspberry AP (with tor on eth) when I want to tor with my phone.