-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add an option to always use relays #2957
Comments
I also need this feature. I've found that direct connections between different network operators sometimes have higher latency than using a relay. |
Changelog for 0.31.0 mentions " Seems to be this PR: #3056 |
We still haven't implemented this with privacy in mind, while you can have all data go through the relay server I can't guarantee that you'll never send an IP address to the peer. And even if that happens to be so, it might break in the future, given this is a debugging tool for now it is not unreasonable that it would behave like a real case where holepunching does not work, in which case initiating holepunching should be happening still. |
The context for #3056 was to push a lot of data through the relay path of the magic socket so that we could improve how it behaves and increase throughput/performance of it. And continuously test for regressions of that performance. |
Together with #2901 it should be possible to establish all connections via proxy and not reveal the IP address even if communicating to unknown relays.
Some users may want to use P2P features of the app (calls, webxdc realtime) but never reveal the IP address.
The text was updated successfully, but these errors were encountered: