Is there any plan to mask identifying information about users (IP, env variables) from relay operators, seems like that should be baked in to the protocol instead of requiring tor. No one should trust nostr until this key issue is resolved, as the digital divide might be too big for non-techies. I want to use a client that only connects to privacy respecting relays.

Reply to this note

Please Login to reply.

Discussion

then run your own

While I can do this, my point (hence referencing the digital divide) is for non-technical people who may not be aware of this risk, or how to mitigate it -- not myself.

just use an anonymizing websocket proxy

I've always preferred these solutions instead of tor. like anonymized dnscrypt:

https://github.com/DNSCrypt/dnscrypt-protocol/blob/master/ANONYMIZED-DNSCRYPT.txt

cool, will try this!

I'd bake that into alphaama if I knew how

you could enable a "proxy mode" that bounces all relay requests through anonymizing proxies. shouldn't be too difficult. we just need those proxies to exist.

that last sentence doesn't even make sense, any client should connect to your relays

If I'm recommending a nostr client to a human rights worker in the global south, often not techies, it needs to be minimal friction for them to use, and not be identified by using it. Having to string apps together is usually too much friction and introduces multiple issues.

I see this as more of a web problem and less of a nostr problem? even if relays say they are privacy preserving, how do clients validate that?

you just wait for Nostr Layer 2