NotHereToPlayGames

Both of these "features" (as I understand them) sends your trackable data to a third-party, the third-party analyzes that data and then reports back if it is 'safe' or not (by their definition, not yours), then the browser proceeds based upon that reply. But WHO is this third-party, WHERE is this third-party ??? I simply do NOT "trust" either one because I don't have ANY information on HOW / WHERE / WHO "behind the scenes". When you rely on an extension such as Adblock Plus, uBlock Origin, uMatrix, Ghostery, Privacy Badger, et cetera, you have a community of users and a plethora of online reviews and critiques to base your "trust" on. In my view at least, relying on something built-in to the browser is like actually thinking that some petty "Do Not Track" 'feature' is really doing anything or that "blocking third-party cookies" actually blocks third-party cookies. I highly prefer my blacklists and my whitelists to be "local" and not sent who-knows-where and analyzed by who-knows-who. I use uMatrix and one-and-only-one list - https://gitlab.com/curben/urlhaus-filter/raw/master/urlhaus-filter.txt Then I use NoScript and only whitelist PARTIAL javascript on a small handfull of websites. If you go to 360Chrome -> Chrome -> User Data -> skin (at least that's the folder structure for the "portable repack") you should find one file with an .srx extension. If you can provide the file name for that .srx file, I might be able to see if that skin is the culprit. Or you could do so some digging on your end, the .srx will unzip with 7-Zip, PeaZip, IZArc, et cetera. There will be an .xml file (maybe two, depending on skin) and a bunch of .png files. The .xml file can be opened in Notepad++ -- look to see if the .xml references OTHER .xml files (if it does, it/they likely reside within 360Chrome -> Chrome -> Application -> 13.0.2206.0 -> skin -> skin.srx which itself will need unzipped. Which also contains http_nosafe_bar.xml and browser_strings.xml, either of which still contains a lot of Chinesse. Hope that helps.

@dencorso Are you using the "anti-tracking privacy protection" 'feature'? Or the "protect you and your device from dangerous sites" 'feature'? (I don't trust either one of them, to be honest.) Have you looked at "http_nosafe_bar.xml" that is contained inside "skin.srx" which exists in 360Chrome -> Application -> 13.0.2206.0 -> skin folder? Very close to what you have above so could be altered by alternate skins by the looks of it. What skin are you using?

You could try Roytam's "loader" and maybe it fits your needs better -- http://o.rthost.win/palemoon/palemoon-portable-loader.7z I've never actually used it so feel free to report back your opinion of it.

From what I can gather, the "libGLESv2.dll" file is needed for older graphics cards for 3D rendering. Not sure "how old", per se, as none of my computers seem to be old enough to "require" this file for 3D rendering. I don't really do a lot of 3D graphics via web browser. I used this as a test - https://www.wirple.com/bmark/ Mypal 27.9.4 scored 461. palemoon-27.9.7.win32-git-20210220-3b1d2cdd8-xpmod scored 384. palemoon-28.10.3a1.win32-git-20210220-729367b92-uxp-2b6effbf2-xpmod scored 618. bnavigator.win32-20210220-355db4de-uxp-2b6effbf2-xpmod scored 608. basilisk52-g4.8.win32-git-20210220-d9301c4-uxp-2b6effbf2-xpmod scored 645. And, drum roll, please -- 360Chrome v13 build 2206 scored 2941. 360Chrome v12 build 1592 scored 2565. 360Chrome v11 build 2251 scored 2457.

I benchmarked x86 versus x64 once-upon-a-time and x86 has better performance than x64, not the other way around. I do admit that this was a couple years ago, but the results were so CONVINCING and UNDENIABLE that I've never bothered with an x64 browser ever since.

Not sure, to be honest. File name suggests mobile phone.

Update. Content added for Russian to English Chrome Web Store.

I'll use my XP *FOREVER*. Even if THIRTY YEARS from now I "might" not be able to use a web browser or email client, I will STILL be using XP even if only on a secondary computer for Chess, Scrabble, Monopoly, Solitaire, Mahjong, Soduko, Kakuro, Crossword Puzzles, and other miscellaneous pass-the-time games that retired old folgies do between naps and yelling at the neighbor kids to get off their lawn. Although, having said that, I will also have to admit that ONE of my SIX "secondary" computers DID get upgraded to Win10 LTSB about five months or so ago because I got tired of several web sites "forcing" me to have FOUR web browsers! One web browser ONLY for ONE web site. Another web browser ONLY for a SECOND web site. A third web browser for rare miscellaneous. Then my at-the-time default for everything else. But now, ONLY because of 360Chrome, I have THANKFULLY been able to "upgrade" that secondary computer back to WinXP! Because while I like to tinker with several web browsers, I have no interest in being forced to have different web browsers for different web sites.

To each their own, but since you bring it up and seem to be requesting feedback -- my feedback is this, I DON'T GIVE A RATS ARSE ABOUT "UPDATES". The very FIRST thing I do whenever I install ANY operating systems is to DISABLE UPDATES !!! !!! !!! However, I do SLIPSTREAM updates before every installation - so I do "update". And one of the things I *LOVE* about Win XP is that I don't have to WASTE THE TIME slipstreaming MORE updates. I stopped slipstreaming and patching SO-CALLED "risks" in June 2017 on this computer (WinXP x64) and in January 2018 on my SIX computers running WinXP x86. I do NOT run antivirus - haven't for a good 15 years or so. If you know "how" to use a computer and know when to click and when not to click and if you do NOT let your software "phone home" and if you only allow WHITELISTED javascript, then "you'll do just fine". And make sure your hardware firewall (I also no longer waste my time with software firewalls) is set up properly. "You'll do just fine". WITHOUT concerning yourself with HYPOTHETICAL "so-called" 'security risks' propegated by an industry perpetuated as "needed" only when you allow 12 year olds to install "games" or when grandma installs some "coupon app". But anywhoo...

The "wrapper" program previously mentioned is called JauntePE and can be found here -- https://sourceforge.net/projects/jauntepe/files/ I'm not sure those 2 folders are worth the "learning curve" to learn JauntePE but I guess that's up to you. I personally clear my cache of EVREYTHING upon exiting EVERY browser session so at least on my end those 2 folders are EMPTY so they don't bother me sitting in ~\Application Data\. The "portable loader" does have a "[RunAfter]" section but I confess that I've never used it.

Not that I'm aware of. Those folders are temp and will be EMPTIED every time you close the browser. SEVERAL portable browsers can even share that same folder without affecting each other. I use a "wrapper" program at home that will perform what you seek, but I don't recall what it is called offhand. And with those folders being EMPTIED by default, I just let them sit there and ignore them.

Update. Added freebie software to first post and added step to remove Incognito Mode "background".

I used to use SpeedyFox under the FALSE assumption that it was making things "faster" - IT WAS NOT! Nothing but a "placebo effect", akin to "snake oil". I challenge you to prove me wrong, with quantitative before-and-after "measurements" -- 'good luck' to those accepting the challenge :)

Here's a quick guide on how to use the "official Pale Moon portable" version as a "loader" for Roytam releases. I use the older portable versions but the process is the same if you use a newer portable version (I don't like the icon color behavior in Win10 on the newer portable version but that's just a matter of personal preference). I use both the 27.9.4 version and the 28.2.2 version. I cannot find a link for the 27.9.4 but here is where you can find the 28.2.2 -- http://archive.palemoon.org/palemoon/28.x/28.2.2/Palemoon-Portable-28.2.2.win32.exe But there is no real reason to avoid the "new" if you prefer that route -- https://www.palemoon.org/download.php?mirror=us&bits=32&type=portable (ie, from here - https://www.palemoon.org/download.shtml#Portable_versions ) When you execute it, nothing is "installed" (ie, no registry changes, for example), it's simply just extracted (you could extract via 7-Zip or any preferred archiver, if you prefer). It will ask "where" to extract the files to - I generally create a new folder named "BasePortable" on the desktop just for convenience. This folder will contain six sub-folders (Backups, Bin, Downloads, Lib, ReadMe, and User). It will also contain two files, "Palemoon-Portable.exe" and "Palemoon-Portable.ini". We'll just keep default .ini settings for the sake of this tutorial. Open the "Bin" sub-folder. There will be a sub-folder inside it called "Palemoon" - we will keep it by that name even if we are using this for Basilisk, ArcticFox, New Moon, Mypal, et cetera. Open that "Palemoon" folder and DELETE all of the files in it (if your File Manager reports a read-only file, confirm in order to delete all of the files). The "Palemoon" folder should now be EMPTY. Now browse back to the folder where you extracted "BasePortable" (I used the desktop). Make as many copies of this folder as you want in order to make several portable browsers. But keep the "BasePortable" (with the EMPTY "Palemoon" folder) for future use if you like testing lots of Roytam builds without effecting your "everyday browser". As an example, let's say we want a Pale Moon 27 browser, a Pale Moon 28 browser, and a Basilisk 52 browser. We would copy the "BasePortable" THREE TIMES. Then rename the three copies to, for example, "PaleMoon27Portable", "PaleMoon28Portable", and "Basilisk52Portable". The folder name can be anything you want it to be. Next we download the Roytam versions we want to make as a portable browser. For this tutorial, I'm using the following three - http://o.rthost.win/palemoon/palemoon-27.9.1a1.win32-git-20180707-54887c52d-xpmod.7z http://o.rthost.win/palemoon/palemoon-28.1.0a1.win32-git-20180922-3c04affe2-xpmod.7z http://o.rthost.win/basilisk/basilisk52-g4.4.win32-git-20190727-9b0ff0e8b-xpmod.7z Then all three of those .7z files are extracted into their own folders. If you use 7-Zip context menus in your File Manager, highlight all three, right-click, hover over 7-Zip, then select Extract to '*\' These will all have sub-folders of their own of either "palemoon" or "basilisk" for these examples. Open the 27.9 folder's "palemoon" sub-folder and copy all of the folders and files. Paste those copied folders and files into the "Bin" -> "Palemoon" folder of "PaleMoon27Portable". Open the 28.1 folder's "palemoon" sub-folder and copy all of the folders and files. Paste those copied folders and files into the "Bin" -> "Palemoon" folder of "PaleMoon28Portable". Open the 52-g4.4 folder's "basilisk" sub-folder and copy all of the folders and files. Paste those copied folders and files into the "Bin" -> "Palemoon" folder of "Basilisk52Portable". For the case of the Basilisk52Portable, you will also need to rename "basilisk.exe" to "palemoon.exe". Once you become more comfortable with the .ini file and the folder structures, you don't need to keep the generic default "palemoon" naming scheme. But it's easier to just keep "defaults" if new at the portable loader. You now have three browsers completely independent of each other. You can execute all three at the same time. You execute the "portable" browser by executing (or shortcutting to) "Palemoon-Portable.exe" in the root folder of each browser. This method will start new profiles for each browser. The profiles are independent of each other. The profile locations for these three examples are as follows - PaleMoon27Portable -> User -> palemoon -> profiles -> default PaleMoon28Portable -> User -> palemoon -> profiles -> default Basilisk52Portable -> User -> palemoon -> profiles -> default Hope this is helpful to those that reached out requesting more details for the "portable loader".

I have done that also. It's why "HxD Hex Editor" is suggested in the first post but the "How-To Guide" hasn't gotten that far yet

You can download all of the Basilisk builds from here -- http://o.rthost.win/basilisk/

Confirming my original hunch - the first "4.4" (ie, basilisk52-g4.4.win32-git-20190727-9b0ff0e8b-xpmod) slightly outperforms subsequent "4.4" releases.

Attached are files that fix SEVERAL translation issues with v13 build 2206. The translation issues are still present in 2212 and I've abandoned 2212 due to Chinese reversions (ie, a step BACKWARDS as far as an English-user version). Fixes nuances such as "clearint" in the Speedup utility (ie, it's supposed to be "clearing" and now is with these files). Fixes several "colsed" dialogs that are supposed to be "closed" and now are with these files. Kind of lost track of all of the fixes I've had to make over the months. But uploading for those that may want to make use of them. Please backup/archive your original files "just in case" (ie, I know I made a few "skin" changes also that I can show you how to reverse if you prefer). 360Chrome should be closed when you replace these files. en-US.pak --> ...\360ChromePortable\Chrome\Application\13.0.2206.0\Locales en_skin.srx --> ...\360ChromePortable\Chrome\Application\13.0.2206.0\skin options.zip --> ...\360ChromePortable\Chrome\Application\13.0.2206.0 resources.pak --> ...\360ChromePortable\Chrome\Application\13.0.2206.0 skin.srx --> ...\360ChromePortable\Chrome\Application\13.0.2206.0\skin https://www.dropbox.com/s/7b4zanniozx372m/English Updates.zip?dl=0

In this installment, I change the default Chrome Web Store language from Russian to English. Go to 360Chrome -> Chrome -> Application -> 13.0.2206.0 folder (ie, version.0.build.0) Copy "chrome.dll" file to a temporary working folder. Open "chrome.dll" in HxD Hex Editor. Do a Ctrl-F (Find) for "goo.gl/j4MLV" (without the quotes) then close the Find dialog. You can edit via left hexadecimal or via right decoded text - but be mindful to not change "file size" (a dialog will pop up to confirm as a safeguard to prevent this). Also be mindful that a "00" (zero zero) in the left 'looks like' a "dot/period" in the right but it is not (a "dot/period" would be "2E"). Option 1 -- replace Russian URL with English URL. The default https://goo.gl/j4MLV redirects to https://chrome.google.com/webstore/category/extensions?hl=ru Here is a nice site to test "shortened links" (as a general rule of thumb I distrust them and dislike their usage) - http://checkshorturl.com/ We cannot change "address offsets" so we have to rely on a "short link". Option 1 is to redirect to https://chrome.google.com/webstore/category/extensions?hl=en-US To do this, REPLACE "https://goo.gl/j4MLV" with "https://bit.ly/2WKImUI" (again, you can test/verify at http://checkshorturl.com/ ) Save the file (HxD automatically saves the unchanged backup as "chrome.dll.bak". Cut-and-Paste the new "chrome.dll" into 360Chrome -> Chrome -> Application -> 13.0.2206.0 folder (360Chrome should be CLOSED when you do this). Option 2 -- replace Chrome Web Store link with direct access to Extensions Manager (I prefer this option).

But the "about:permissions" options of "Receive Push Notifications" and "Hide the Mouse Pointer" both continue to fail to function, as reported a half a dozen times or so over the last couple of years. But I digress...

While benchmarks don't paint the "entire" picture - if I used Basilisk 52, I would be using basilisk52-g4.4.win32-git-20190727-9b0ff0e8b-xpmod. For the most part, my observations in testing Bailisk 52 is that the first in a "4.x" series performs better than the last in a "4.x" series - but I did not look for ouliers between the first and last.

Looking like the "g4.4" series is coming out on top. Still in-process of comparing-contrasting.

I'll do some compare-contrasts over the next day or two and report back. Most of my current benchmark spreadsheets focus primarily on NM27 (and how it has been going downhill based on benchmark comparisons). Update: Looking like the "g4.7" series is where I would stay and I wouldn't bother 'upgrading' to the "g4.8" series -- "mileage may vary"

I did not tell you to use the official Pale Moon build. I suggested downloading the portable and THEN COPYING THE BUILD THAT YOU DO USE INTO THE BIN FOLDER. We only want to use the "portable loader", NOT the "official Pale Moon build". ps - not for the faint of heart, but I wouldn't run antivirus software if you PAID ME TO. Never been hit with a virus (and would put money on it that I never will be). Click-Savvy. Know what you are clicking, use a good HOSTS file, use NoScript and only allow white-listed .js, use a good uMatrix list, et cetera. But again, I wouldn't run antivirus software if you PAID ME TO. But "to each their own", I know that "most" people don't like BLOCKING ALL javascript by default. But it's either nag-screens about .js or nag-screens from the antivirus software, "pick your poison". But anywhoo...

In this step, I disable the Incognito Mode "background". To me, it's a bit pointless to even have the "background" - if I'm geeky enough to use Incognito Mode, then I already know what it does and what it does not 'do'. I've included the Google Translate "translations" (but #4 is definitley "lost in the translation") and also included the official Chromium v49 "background" for reference. 1) You are currently using an incognito window 2) Incognito windows can: 3) Leave no traces on the Internet, and leave no records on the Internet in stealth mode 4) Open more trumpet, create an incognito window and then open the website trumpet, no serial number 5) The incognito window will not record any traces of the Internet, but will keep the files you downloaded and the favorites you added. 6) The incognito window will disable all extensions by default to protect privacy. If you need to enable extensions, you can set it on the extension management page. I also added a freebie software (Chrome PAK Customizer) to the list in the first post of this thread. Go to 360Chrome -> Chrome -> Application -> 13.0.2206.0 folder (ie, version.0.build.0) Copy "resources.pak" to a temporary working folder. The easiest way to use Chrome PAK Customizer is to have TWO file manager windows open. One window being the "chrome-pak" folder (extracted from the downloaded "chrome-pak.7z") which will have "pack.bat" and "unpack.bat". The other window being the temporary working folder you copied "resources.pak" into. Left-Click-and-Hold on top of "resources.pak" in the temporary folder and Drag-and-Drop on top of "unpack.bat" in the chrome-pak folder. Wait for the command prompt window to close itself and you will see a new "resources_unpacked" folder in your temporary folder. Open the "resources_unpacked" folder then open the "pak_index.ini" file contained inside. Delete the line that reads "13581=13581" and make sure there is no empty-line gap between "13575=13575" and "13585=13585". Save and Close "pak_index.ini". Left-Click-and-Hold on top of "pak_index.ini" in the temporary folder and Drag-and-Drop on top of "pack.bat" in the chrome-pak folder. Wait for the command prompt window to close itself and you will see a new "pak_index_packed.pak" file in the "resources_unpacked" folder. Rename "pak_index_packed.pak" to "resources.pak". Copy-and-paste the new "resources.pak" into 360Chrome -> Chrome -> Application -> 13.0.2206.0 folder (360Chrome should be CLOSED when you do this).