NotHereToPlayGames

<reserved>

<reserved>

<reserved>

<reserved>

<reserved>

<reserved>

<reserved>

<reserved>

WebGL Note that WebGL is enabled by default. For those that wish to disable it, add --disable-webgl to the Parameters line in 360Loader.ini

Skins I plan on placing several skin packages here. I know that I've been saying that for a year or so, but I do have several in-process, just not exactly high priority. I can foresee them "finally" being completed by the end of the year (no Holiday travels planned for the year so that gives more free time than I typically have). I currently run Win10 the majority of the time as opposed to XP when I started sharing these rebuilds. So the as-is skin now is "flat" and "square" like Win10 and not "three-dimensional" and "rounded" like XP. I urge caution in "mixing-and-matching".

Extension Page "action links" I hide the "action links" (permissions, options, developer website, details) on the Extensions Page. Striclty my preference, I find them to be excess clutter for links I never actually need/use and I can toggle them as visible via the Developer tools if I do end up needing them. For users that prefer them to be visible all the time, replace resources.pak with one of the below (unzip it first) -- "ungoogled" -- https://www.dropbox.com/scl/fi/3n9uyuaj5seg6t17pvzpj/ungoogled_resources_action-links.zip?rlkey=5nhcy6az1i71e4w7bfnpo4ory&dl=1 "regular" -- https://www.dropbox.com/scl/fi/t3wrsmp9u7c2e9gic18gn/regular_resources_action-links.zip?rlkey=ogcdbwlr01fj4ss1m2z0cxcnc&dl=1

Rebasing Rebasing should not be required and has not been performed. This could be computer-specific so I request to see "Process Hacker" screencaps for users that may think a rebase is required for their computer. I use this version of Process Hacker but any version will do -- https://sourceforge.net/projects/processhacker/files/processhacker2/processhacker-2.23-bin.zip/download

Installing Extensions The Chrome Web Store has already planned to obsolete Manifest V2 extensions and 360Chrome v13.5 and older does not support Manifest V3. Therefore only an "ungoogled" version is currently being maintained. There are ways to "restore" what we used to refer to as "regular" versus "ungoogled" - but it is very much a Long Term Dead End with MV2's expiration on the horizon. In the meantime, all users should be archiving their own .crx files. An easy way is to use already-public archives such as https://www.crx4chrome.com/ Another route is to use "CRX Extractor/Downloader" -- https://www.crx4chrome.com/history/265228/ There is no need to ever use "Developer Mode" on the chrome://extensions page - simply drag-and-drop your archived .crx onto the chrome://extensions page. I also reference @rereser's userscript for members that opt for this route -- https://msfn.org/board/topic/185049-arcticfoxienotheretoplaygames-360chrome-v1352044-rebuild-2/?do=findComment&comment=1255373 Though note that this ALSO requires a "regular" version. So users will have to do THREE things - 1) install Tampermonkey from an archived .crx, 2) install the above userscript, and 3) convert from "ungoogled" to "regular". To convert from "ungoogled" to "regular", replace 360Chrome's resources.pak with this one (unzip it first) -- https://www.dropbox.com/scl/fi/ryuc7x38i05r8x8ar1xac/regular_resources_pak.zip?rlkey=xg8oz0xi2mysah9svpd7dxxin&dl=1

YouTube I've had good luck with Enhancer for YouTube. @Dave-H has a shared download here - https://msfn.org/board/topic/185049-arcticfoxienotheretoplaygames-360chrome-v1352044-rebuild-2/?do=findComment&comment=1255763 I've also had good luck with this Greasyfork script using Tampermonkey - https://greasyfork.org/en/scripts/480137-youtube-h-264-fps/code Users reporting issues with YouTube should also post a screencap of the video's Stats for nerds dialog (available in context menu when right-clicking on top of video) -

360Chrome v13.5 Build 1030 Redux I inadvertently corrupted my original Build 1030 series when working on Builds 2022 and 2036 so this is starting brand new with several lessons learned from later versions, including 2044. I've always much preferred Build 1030 over anything "newer". They all technically use the same v86 Chromium engine "under the hood". Download link -- https://www.dropbox.com/scl/fi/d5sjhgshdrjtntd06iecb/360ChromePortable_13.5.1030_Redux_1_ungoogled_MSFN.zip?rlkey=etzsfb8m9z1kljxj10jwhw9wv&dl=1

Doesn't seem to be an issue with build 1030 and rebasing was only required in the "newer" versions (on some systems, especially x86).

I believe that's already been asked and answered here -- https://msfn.org/board/topic/183657-mypal-68-in-windows-xp-custom-buttons-and-extensions/?do=findComment&comment=1226364

Key word being "was". I've never met anyone that pays for a web browser. Doesn't mean they don't exist, especially for the mobile phone community. But certainly not the "norm". Agreed.

I only witnessed the standard 20-30 connections to Google IP Addresses that all Chromium Forks make unless "ungoogled'. Primarily 172.217.x.y and 142.25(0|1).x.y. Also saw a 34.104.x.y in the list, not sure I've seen that one in other Chromium Forks, possibly tied to "DNS Protection" which is just another way of saying "give us your DNS records instead of giving them to your ISP".

I'm a bit concerned that the author has this note -- "valid for one year"

I'm not sure if that is a VPN IP indicator or not. I know there was an extension posted a while back that places the flag of the web site's location. So that US Flag could just be indicating that the web site being connected to is located in the US. As opposed to indicating a VPN using a US IP.

I am well aware, I wasn't born yesterday, lol. I'm actually planning six different Win10 color choices. I call them Win10 because the title bar (and min/max/close/restore icons) is (are) "flat" where XP's title bar (and min/max/close/restore icons) is (are) "rounded". My RGB / HTML color combos are below. I figure SIX is more than enough for members to grab one that suits them. No timeline, they will be done when they are done. The color combos are basically being defined "for me". Official Ungoogled Chromium does NOT use Win10's "inactive title bar" color (Win10 defaults to white [Light App Mode]), but selects its own "inactive" color based on 'masking' the "active" color. Once an "active" color is manually defined (registy entry also provided for reference), it is Official Ungoogled Chromium revealing the other colors used in my skins, I don't just pluck them out of thin air, lol. Blue 0 99 177 = #0063B1 72 143 199 = #488FC7 26 115 232 = #1A73E8 Olive Green 112 130 56 = #708238 153 166 133 = #99A685 232 113 10 = #E8710A Metallic Silver 170 169 173 = #AAA9AD 194 193 196 = #C2C1C4 128 134 139 = #80868B Iron Gray 82 89 93 = #52595D 131 136 139 = #83888B 128 134 139 = #80868B Bronze 177 86 15 = #B1560F 199 134 83 = #C78653 176 96 0 = #B06000 Brick Red 170 74 68 = #AA4A44 194 125 121 = #C27D79 217 48 37 = #D93025 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\DWM] "AccentColor"=dword:ffb16300 "AccentColorInactive"=dword:ffc78f48 Note that Win10's registry uses BGR instead of RGB and the first two letters define the "mask" (typically ff for Light App Mode and 00 for Dark App Mode). I've not yet experimented with "masking" 'in the middle' for a skin that works well in Light App Mode and Dark App Mode.

I plan to upload an all-new from-the-ground-up build 1030 within the next few weeks or so, I don't really have a timeline on it. It merges much of 2044 into 1030 and uses a Win10 skin. It's still "blue" as I intentionally use XP's "blue" desktop even in Win10 and accent color and title bars in Win10 are also "blue" for me. I also axe Win10's "immersive menu" and revert it from can't-stand-dark to love-my-light menu colorings. I've been rewriting the menus to include icons and added an avatar menu "User Center" (still in-process). No real reason, "just because".

But this browser does "phone home" to the Chrome Web Store. Granted, I would have to experiment because I've never actually used any Chrome Fork that isn't "ungoogled" in some form or another. For members that do use the "regular" version versus the "ungoogled" version, does your extensions "update" or notify you that an update is available? If so, then that is at least the first sign that your setup is talking to the Chrome Web Store. If a line of communication is open, I wouldn't doubt in the least that the Chrome Web Store has (or will soon have) a means to disable MV2 extensions. But as mentioned, I would need to experiment. ps - I still use 360Chrome v11. Not as much as v13.5, of course, but still three or four times more frequently than New Moon 27.

Users of UNGOOGLED versions are not affected. Thanks.