Closed cvl closed 3 years ago
This is how google handles fingerprinting on their side and has nothing to do with our application. Causes could be numerous, for instance be it a shared wifi in a dormitory or similar situations.
It has a lot to do with Mysterium application, because that's what users will experience.
Any ideas how this can be resolved? I can see few options so far:
Anyhow, if user will see such UI he'll get scared and tell others. Reputation will go quickly to 0.
What we could do is ask Google to honor HTTP headers. They haven't been doing that for years and many have tried asking and all have failed.
Communicate to providers, that they should fix such issues (could be some instructions etc how to do this).
- is the provider using an Arabic version of Google because he speaks Arabian an "issue"? It seems like you're suggesting profiling based on the provider race.
Test (e.g. by crawling google and the like) & ban such providers (could be same grace period with notification to provider)
- we're definitely not going to be banning people due to their spoken language.
Arabic is not a race. Let's not start with this.
I'm suggesting to provide quality service: if user connects to Germany, he should expect either English, or in German. It doesn't relate to race, gender, sexuality.
Thanks for the answers.
Describe the bug Connected to Germany node 0x3d2a73bb408d0a5ace3e8fd71ded43cf6e344cfc I'm seeing google in arabic and in reverse.
Scary.
IP location:
Environment (please complete the following information):