Are you talking about splitting web socket implementation from relay implementation? Subscription handling is quite coupled to an IP now. But indeed an HTTP proxy could just strip the x-forwarded header.
Discussion
that can way to do (until new law arrive )- but 1st relay will always get client exitIP
I'm just always trying to think about how we can construct Nostr to be slightly-more private over HTTP.
Natively, I mean, rather than using VPN or Tor, as most people aren't using them and won't use them.
The idea of gift wraps is nice for DMs. But not suitable for public speak.
micropayments and short lived micro accounts and all relays are pay to write, which is also pay to proxy
the hard problem i bumped into is discovering the network and relays not needing to know what lives at the address the relaying message asks it to be sent to
this is why Tor and IPFS are both limited to around 8k nodes whereas bitcoin has over 20k
Didn‘t I see some nostr people talk about ham radios? They could meshnet and you would only see the exit on IP. But the meshnet routing would be unsolved.
Maybe we should buy an IP mixing satellite relay in space (or the international seas)
Can I rent servers for cash or Bitcoin somewhere? Short-timed?
few places can
depends on how short timed... month is the minimum for cryptoho.st but they have bitcoinpayserver and you can pay with lightning and they don't require KYC
they are based out of suaceva, Romania, i presume that's an industrial suburb area near Cluj Napoca or Sibiu or something (based on what GEOIP shows me on the map)
Final thought: yeah, onion routing
The header doesn't matter, unless the proxy is masquerading, which you can't trust, it's the TCP header that unavoidably reveals the source
The only way out is via onion routing