NotHereToPlayGames

Bingo! If you have ever completed a "captcha" on that computer, then it has been fingerprinted and "databased" and you are wasting your time and resources to try to "un-fingerprint". edit: "captcha" = Completely Automated Public Turing test to tell Computers and Humans Apart

Nor would I expect it to. Screen resolution is but ONE variable out of HUNDREDS. And it depends on which of those variables is being used to "fingerprint" you. If you send a User Agent that tells the world you run XP x86 SP2 when 99% of folks on XP x86 run SP3 and not SP2, then of course you are "unique". If you think about it, being "unique" is *NOT* the result you want if you are trying to "not be fingerprinted". Being UNIQUE is BAD - you have been fingerprinted and they know EXACTLY who you are, you are "unique".

You once mentioned that you do not run your browser window "maximized" because you feel it is a privacy vulnerability, so what window size do you run? Because it is that smaller window size that prompts the chevrons, in all versions of 360Chrome (I tested in several versions all the way back to v11 now that I know what you are talking about - a screencap at the very beginning would have been extremely helpful). Running a MAXIMIZED window is actually LESS of a privacy vulnerability - because then your fingerprint on screen size is a needle in a haystack, you blend in with everybody with the same monitor resolution. Running in a smaller window makes you stand out like a sore thumb because you become the only person on the planet running that window size.

Glad that's finally settled, lol That's not a new "feature" and has always been there, I never run that small of a window size.

Still NO CLUE of what you are talking about. There is no new feature. Can you share a screencap so the rest of us know what in Hades you are talking about?

It cannot be "removed". What you can do is NOT install "unpacked" extensions but REPACK them yourself and then install them. You have to perform the REPACK while in Developer Mode, do not install them until you REPACK them first. This dialog IS a result of how you are installing them, that's why it is "only you".

I do not have any of these issues and nor has anyone else indicated that they have, so I have to assume it is you and only you. You are installing your extensions incorrectly if you are getting this "nag window". This "chevron" is not some new "feature", IT SEEMS TO BE WITH YOUR EXTENSIONS AND YOURS ONLY. These are not "bugs" and I am compelled to ignore any "persistence" indicating otherwise - until proven otherwise.

No clue what you are talking about, what's a "chevron"? What extension icons? Is this ANOTHER extension issue that you think is a 360Chrome issue but isn't?

The Share "features" both accesses Chinese web sites that have been blocked - thus the page going blank is intentional. I don't recall who found the original hex codes to remove the context menu entries, unsure if him/they still follow this thread or not. I never use IE mode so I never tested the old hex patches, let alone carrying them over to a new build, I just pattern-matched and moved on. And I don't recall if I reversed those pattern matches when returning Translate "feature" (another feature I myself never use, I don't use translate extensions either, if the web site isn't English, I don't visit it or simply "guess" content based on "patterns").

Firefox has a similar "loopback" that firewalls with "parent-based" rules (ie, you can allow Firefox internet access when launched from the desktop but deny Firefox internet access if launched by a software installation opening a html page) will nag heavily about.

No surprise here.

Beta-3. https://www.dropbox.com/s/4r3aq2tsv8u6hin/360ChromePortable_13.5.2036_r1_regular_MSFN_beta-3.zip?dl=1

Thanks. I was missing the hiya and cloud connections because I forgot that my XP VM where I run these when still at beta stage had some hosts file entries.

The cloud connection is this line, "x" out the two t's in http -

The hiya connection is this line, hex out with 00s to resolve.

Why even turn on the avatar? It would not have been enabled out-of-the-box. I don't use uBlock so no clue on that one. Did you enable developer mode extensions? It would not have been enabled out-of-the-box. Already aware of Chinese on padlock, I've replied to whomever posted it first (I hope the same person didn't post that issue twice, lol).

Sometimes it's not the "web site address" that you need to hunt for. As one example, hunt for the word "resolver" and anything that looks like an IP Address immediately following.

Also note that it becomes a matter of perspective. The Russian Repack prefers to maintain the functionality of visiting the 360Chrome skin web site and change skins via that web site. I view that skin connection as "telemetry" whereas the Russian Repack Author views it at a matter of skin-changing functionality. The hiya and cloud could very well also be a "functionality" that we remove/disable and no longer need that "connection". At any rate, rest assured, I do not want these "connections" nor the "function" that they serve and I'll "Metallica" them ("seek and destroy").

Nope, I have not. Remember that my "source" is a Russian Repack. My telemetry removals are basically what the Russians missed. (There is no evidence that Chinese telemetry was "replaced" with Russian telemetry, though I keep an eye out for that as well.) In the past, Humming Owl and I just cast a wide net and replaced any-and-all "360.cn" with dots - I no longer recommend this approach and would prefer to isolate the "exact" root-cause instead of that "wide net".

I no longer use the "dot-replace" because local proxies still log the attempted connection. ie, your computer's DNS resolver was still asked to resolve an address. DNSQuerySniffer doesn't show it because only resolved address are displayed. So I will be replacing hiya.browser.360.cn hex equivalent with the equivalent number of bits replaced with 00 instead of 2E (2E = dot). The cloud.browser will very likely be something like ht tps://cloud and it is best replaced with hx xps://cloud. I prefer a method where the computer's DNS resolver didn't waste time to resolve a non-existing address (ie, an address replaced with dots still gets routed to your DNS resolver).

Beta-2. Regular. Tranalate enabled. WebGL enabled. Rebased. Disregard, link removed. I'm still getting a skin.chrome.360.cn connection after reboot so turns out not resolved yet. Re-uploaded, the skin telemetry (which is independent of actual skin) should now be resolved. Please let me know if you still see any 360.cn connections. https://www.dropbox.com/s/sk01gdpu1n3cftq/360ChromePortable_13.5.2036_r1_regular_MSFN_beta-2.zip?dl=1

I'll get this one in the next beta (beta-3, not in beta-2 about to be uploaded).

skin.chrome.360.cn was being connected to through a dns-query through IP Address 208.67.220.220