ArcticFoxie/NotHereToPlayGames -- 360Chrome v13.5.2036 rebuild 1

[rereser]

.

Edited 6 hours ago by rereser

[NotHereToPlayGames]

10 minutes ago, rereser said:

found 2x

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".

[NotHereToPlayGames]

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

 

 

 

Edited April 10, 2023 by NotHereToPlayGames

[rereser]

.

Edited 6 hours ago by rereser

[NotHereToPlayGames]

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.

[rereser]

.

Edited 6 hours ago by rereser

[NotHereToPlayGames]

23 minutes ago, rereser said:

there must some reason for you to build 13.5.2036.

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.

[rereser]

.

Edited 6 hours ago by rereser

[NotHereToPlayGames]

3 hours ago, rereser said:

connections on first run 13.5.2036 beta directly after zip unpack.

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.

[NotHereToPlayGames]

10 hours ago, NotHereToPlayGames said:

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

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.)

[NotHereToPlayGames]

6 hours ago, rereser said:

connections on first run 13.5.2036 beta directly after zip unpack.
with DNSQuerySniffer :

hiya.browser.360.cn
and after a few seconds :
cloud.browser.360.cn
skin.chrome.360.cn

on second run only hiya.browser.360.cn

I can confirm skin.chrome.360.cn and will keep hunting for the others.

Please let me know if you encounter any others.

[NotHereToPlayGames]

14 hours ago, rereser said:

hiya.browser.360.cn
and after a few seconds :
cloud.browser.360.cn
skin.chrome.360.cn

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

Edited April 10, 2023 by NotHereToPlayGames

[rereser]

.

Edited 6 hours ago by rereser

[NotHereToPlayGames]

18 hours ago, msfntor said:

Left click on padlock: Security disabled+some Chinese signs...

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

Edited April 10, 2023 by NotHereToPlayGames

[NotHereToPlayGames]

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

Edited April 10, 2023 by NotHereToPlayGames