Jump to content

ArcticFoxie/NotHereToPlayGames -- 360Chrome v13.5 build 2022


Recommended Posts

56 minutes ago, XPerceniol said:

I'm only at the moment blocking the following:

RE gstatic..
0.0.0.0 gw0.activeasanaingstatic-v3.net.zooplus.it
0.0.0.0 gw0.datatestingstaticnginx.net.zooplus.it
0.0.0.0 node.ns-northamerica.backend.vpn-activemarketingstatic.net.zooplus.it
0.0.0.0 csi.gstatic.com
0.0.0.0 gstaticx.com\

RE googleapis..
0.0.0.0 firebaselogging.googleapis.com
0.0.0.0 clientmetrics-pa.googleapis.com
0.0.0.0 crashlyticsreports-pa.googleapis.com
0.0.0.0 update.googleapis.com

I'm assuming those are HOSTS file entries?

Link to comment
Share on other sites


5 hours ago, rereser said:

would be nice to know if resources.pak and / or chrome.dll modifications are needed with every new file.
for updated link on date only and on build version update please.
it would make the "upgrades" for "regoogled" users more convenient.
your instructions are clear but may not be for all users.

Agreed.

Small "patch" .exe's (7z executables with self-contained portable HxD coupled with AutoIt) would be fairly easy but then all of the anti-virus folks would crawl out of the woodwork and cast aspersions.

Link to comment
Share on other sites

Plus, I also think that v13.5 is basically "end of the line" for 360Chrome on XP.

I hear rumors of another Chrome Fork in the works that would dethrone 360Chrome if the rumors are true.

Waiting to see.  https://msfn.org/board/topic/184127-xp-and-future-of-web-browsing/?do=findComment&comment=1230273

 

edit - truth be told, 360Chrome could come out with twenty "newer builds" for v13.5, but if a web site that does NOT work in build 2022 isn't PROVEN to work on the "newer build", then I will not upgrade from build 2022.

I'm not looking to be the dog chasing its tail with constant "updates".

Edited by NotHereToPlayGames
  • Like 1
Link to comment
Share on other sites

1 minute ago, verta said:

Tested working. I can translate to english now.

Good deal.  I'm "on the fence" as to whether to keep the translate feature intact or not.  I myself "never" (never say never?) visit sites that need translated.  And when I do, there are web-based translation sites as opposed to being "built in" to the browser.  On one hand, Official Ungoogled Chromium does not have it and my goal with 360Chrome was to immitate Official Ungoogled for the most part.  On the other hand, it's buried away in a context menu and makes no "connections" to Google until the user intentionally selects that context menu item.

Link to comment
Share on other sites

18 minutes ago, Dave-H said:

I just get an error message anyway if I try to use the translate function.
Is that normal?

The "ungoogled" version does intentionally prevent that network connection unless you perform the chrome.dll modification posted here -
https://msfn.org/board/topic/184135-arcticfoxienotheretoplaygames-360chrome-v135-build-2022/?do=findComment&comment=1230537

Link to comment
Share on other sites

Here are the patches needed so remove some Google-related context menu items that @NotHereToPlayGames prefers not to have in his un-Googled builds. The patches are to be applied to chrome.dll from 13.5.2022.0 rebuild 2, but they aren't specific to this rebuild, so if he doesn't include all of these in his future versions, you could still apply them on your own. They should even work with the Chinese original, but not with other base builds like 1030, not to mention the 13.0 line etc.

Fortunately everything that was needed could be derived from static analysis and the logic for these things was pretty simple, so I could get this done relatively quickly. However, this has barely been tested, so be prepared for browser crashes and things not working as they should. If in doubt, please refrain from using these patches for now. I certainly hope I got everything right the first time, but this type of work is very unforgiving of even the smallest of mistakes... It's really not my style to release something like this without real-life testing it for a while, but I wanted to get this out to @NotHereToPlayGames so now he can beta test something for me :lol:. But seriously, I don't really have time to test this myself as I'm not using this browser that much, and even then a customized older version.

FYI, some of these changes are for "IE mode" menus. I never use the IE engine with 360 myself, but since it wasn't that hard to fix, I figured why not do it. Oh, and feel free to mix and match, the patches don't depend on each other.

Make sure you make edits in "hex" mode, not plain text mode (not trying to patronize; I got into some weird errors when I forgot to switch to the hex tab one time). All of these edits should only match 1 time with Replace all. Red bytes are replaced with black ones, but always search/replace the entire sequence, not just the changing part.


Drop Share URL QR Code from Chrome mode page context menu:
89 F9 68 79 1A 00 00 68 4F 81 00 00
EB 0F 68 79 1A 00 00 68 4F 81 00 00

Drop Share URL QR Code from Chrome mode link context menu:
89 F1 68 79 1A 00 00 68 50 81 00 00
EB 0F 68 79 1A 00 00 68 50 81 00 00

Drop Share URL QR Code from IE mode page context menu (three parts, because need to match up surrounding menu items):
6A 00 68 D5 08 00 00 FF 75 08 FF 15 44 42 ED 16
EB 5E 68 D5 08 00 00 FF 75 08 FF 15 44 42 ED 16

68 E4 25 00 00 FF 75 08 FF 15 44 42 ED 16
68 D5 08 00 00 FF 75 08 FF 15 44 42 ED 16

68 E4 25 00 00 FF 75 08 FF 15 C4 42 ED 16
68 D5 08 00 00 FF 75 08 FF 15 C4 42 ED 16

Drop Share URL QR Code from IE mode link context menu:
8D 7D E8 68 79 1A 00 00 57 E8 F3 0F 14 FB
EB 3A 90 68 79 1A 00 00 57 E8 F3 0F 14 FB

Drop Share URL QR Code from IE mode image link context menu:
8D 45 D8 68 79 1A 00 00
EB 43 90 68 79 1A 00 00

Drop Share image location from Chrome mode image context menu:
89 F9 68 7A 1A 00 00 68 51 81 00 00
EB 0F 68 7A 1A 00 00 68 51 81 00 00

Drop Share image location from IE mode image context menu:
6A 00 6A 0F 53 FF 15 44 42 ED 16 83 F8 FF 74 3C
EB 4A 6A 0F 53 FF 15 44 42 ED 16 83 F8 FF 74 3C

Drop Translate to English from Chrome mode page context menu (this also avoids some of the translation-related housekeeping, could (very) slightly speed up page loads):
8D 86 F0 02 00 00 50 E8 CF BA 71 FE
E9 E6 00 00 00 90 50 E8 CF BA 71 FE

Edited by mixit
Link to comment
Share on other sites

On 11/26/2022 at 2:21 AM, mina7601 said:

I'm probably doing something wrong/missing something here, but there's no actually "TranslateEnabled" registry entry at all. I tried using ProcMon as per @mixit's post, but nothing specific comes up. I tested Ungoogled Chromium 86.0.4240.193 32-bit.

No, you're quite right, it wouldn't be there unless the policy is specifically applied, and Ungoogled has no reason to follow Google-branch policies. I thought maybe they have their own policies under a different key, but it's not too surprising if they don't.

Edited by mixit
  • Upvote 1
Link to comment
Share on other sites

3 hours ago, mixit said:

Drop Translate to English from Chrome mode page context menu (this also avoids some of the translation-related housekeeping, could (very) slightly speed up page loads):
8D 86 F0 02 00 00 50 E8 CF BA 71 FE
E9 E6 00 00 00 90 50 E8 CF BA 71 FE

found no page load speed increase when browsing with the translate portion changed.
at least there now is a way to reverse if NHTPG removes all in his ungoogled version.

if one tests the ie compat mode on some site , do not forget to change back to chrome mode.
the setting is remembered for each site separate.
reload page after change.

Edited by rereser
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.


×
×
  • Create New...