NotHereToPlayGames

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

I can confirm skin.chrome.360.cn and will keep hunting for the others. Please let me know if you encounter any others.

On second thought, I've officially designated build 2036 as my default. (I accidentally corrupted my in-process 1030 rebuild 9 with a couple 2036 updates and don't want to track it down at the moment.)

Do you have Windows registry entries left over from other versions? I'm unable to replicate these connections and they seem to be remnants from other skins.

Curiosity. See if it offers any improvements. Which it doesn't seem to from what I can gather. That's how a lot of these upstream projects tend to go, they will add "stuff" around the edges but do nothing to the core rendering engine. I'll complete a "regular" non-ungoogled and release a second beta.

Really depends on your definition of "beta". If you follow the options.html file inside the options.zip file, you can see that most (if not all) of the changes since build 1030 all pertain to mobile phone "minimalist_skin" settings that are not used in desktop mode. I don't think any MSFN Member is using 360Chrome on a mobile phone but this could be a big userbase in China and thus a higher focus for upstream development.

I still perfer the 1030 branch and kind of don't see any benefit to using anything "newer" than 1030.

I was afraid that might happen. The one direction has only one find, but the reverse has two. So address offsets must also be considered when "reversing".

I'd also be curious if you reversed all of the following (the one Translate to English Chrome context menu and all six of the IE Mode context menus) - Function:Drop Translate to English from Chrome mode page context menu (1 occurrence) replace:C0 FB 8D 86 F0 02 00 00 50 E8 with:C0 FB E9 E6 00 00 00 90 50 E8 Function:Drop Share URL QR Code from IE mode page context menu 1-of-3 (1 occurrence) replace:6A 00 68 D5 08 00 00 FF 75 08 FF 15 D4 D2 ED 16 with:EB 5E 68 D5 08 00 00 FF 75 08 FF 15 D4 D2 ED 16 Function:Drop Share URL QR Code from IE mode page context menu 2-of-3 (1 occurrence) replace:68 E4 25 00 00 FF 75 08 FF 15 D4 D2 ED 16 with:68 D5 08 00 00 FF 75 08 FF 15 D4 D2 ED 16 Function:Drop Share URL QR Code from IE mode page context menu 3-of-3 (1 occurrence) replace:68 E4 25 00 00 FF 75 08 FF 15 54 D2 ED 16 with:68 D5 08 00 00 FF 75 08 FF 15 54 D2 ED 16 Function:Drop Share URL QR Code from IE mode link context menu (1 occurrence) replace:8D 7D E8 68 79 1A 00 00 57 E8 73 F8 13 FB with:EB 3A 90 68 79 1A 00 00 57 E8 73 F8 13 FB Function:Drop Share URL QR Code from IE mode image link context menu (1 occurrence) replace:8D 45 D8 68 79 1A 00 00 with:EB 43 90 68 79 1A 00 00 Function:Drop Share image location from IE mode image context menu (1 occurrence) replace:6A 00 6A 0F 53 FF 15 D4 D2 ED 16 80 7D E3 00 79 with:EB 4A 6A 0F 53 FF 15 D4 D2 ED 16 80 7D E3 00 79

Can you share the URLs for some example sites?

Hmm. I have noticed that the context menu does not show up on about:blank or chrome://newtab/ but it does show up when on an actual web site. This could be an upstream difference that landed in build 2036?

Hmm. But you did do the one-and-only-one Hex Value reversion?

Reversing does bring back "Translate to English" here. You may need to launch and exit a couple times after making that reversion. Also, make sure nothing in your setup is blocking access to translate.googleapis.com.