-
Notifications
You must be signed in to change notification settings - Fork 12
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
improvement: reduce workload or proxy #58
Conversation
...to be comparable to browser-based proxies. Otherwise the proxy polls every 5 seconds, which is 12x as frequent as browser-based proxies do. See - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40373 - guardianproject/orbot#1105
2658391
to
92a8e53
Compare
Let me know, when a Snowflake version will be released, which contains your changes! Then we'll move this forward. |
Hey! Letting you know, as promised, that a new release has been published. It includes the change that is needed for this MR. |
Do you mean Snowflake version 2.10.1? We're short of releasing, one more upstream bug needs to be resolved. |
Yes, I meant 2.10.1. It includes the |
Ok, is this helpful for you? 3e2825a |
Yes, it's the right direction, but I'd say we need to default to a lower value, as in this MR. Would you like me to rebase it? |
The default comes from the upstream Snowflake library. Unless you give a good reason, why the default should be 2 seconds instead of 5, that is not going to change... |
Oh, you actually mean the higher value of 120 seconds, which is a lower frequency? Well, still. |
Yes.
|
Sorry, but I don't see any argument in the mentioned documents, why this should default to 120 seconds in @n8fr8, what would you consider a sensible value in Orbot? |
Yes, because mobile. The default for browsers is 60 seconds. This project is currently only used in Orbot and in its iOS alternative, right? |
The SnowflakeProxy "kindness" mode feature is only on Orbot Android. I don't have any special insight to what the value should be for this usage, but I think we want to lessen the burden on the user's device as we can. |
I raised this question on today's Tor anti-censorship meeting. We agreed that 120s should be alright. I'll post a link later if needed. Update: https://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-12-05-16.01.log.html |
Well. Everybody agreed on that Orbot should move to a 120 second interval. That doesn't mean IPtProxy should. Sorry, but the notion of changing the default of this in IPtProxy rubs me the wrong way. It'll be very different to what it was before. It will be very different to what the upstream Snowfake Proxy code uses. For anybody using this other than us, that will create confusion. And no. I don't have an idea of who else is using this feature, and if there are users at all. After all, it's FOSS. But I know of different people using IPtProxy in general. So there might be users out there, who are using the Snowflake Proxy feature and they would be very surprised if I change this behind their back. I will leave it at the default 5 seconds for now, in this lib. Orbot then can, and should, increase this value. I'll publish a release. |
That's also fine. Thanks! |
...to be comparable to browser-based proxies.
Otherwise the proxy polls every 5 seconds, which is 12x as frequent as browser-based proxies do.
See
Due to changes in the API, I think this is gonna be a breaking change.
Why WIP:
For reference, see de01c06
log.Fatalf
inside the main function instead of in the goroutine.int
, thinking that it's not gonna be available for the C version.