NotHereToPlayGames

You can get around that by installing your extension in a different way. Download your extension .zip or .crx source file -- in your case, here is your source file - https://github.com/gorhill/uBlock/releases?page=4 --> https://github.com/gorhill/uBlock/releases/download/1.26.2/uBlock0_1.26.2.chromium.zip Extract the .zip or .crx to a folder location of your choice. Personally my very next step is to delete any-and-all non "en" locales but this is personal preference to make the extension a tad more "lightweight" (and I'm never going to use non "en" anyway). I often make other modifications and seldom use extensions "as-is", but that's a whole different story. Now open the Extension Manager in 360Chrome. Do not install from the extracted folder. Instead, select the Developer mode checkbox in the upper right corner of the Extensions Manager. Click the Pack extension button. Click the Browse button for the Extension root directory field. (Leave the Private key empty.) Click the Pack Extension button. That will create TWO files (a .crx and a .pem). Unselect the Developer mode checkbox. DRAG AND DROP the .crx onto the 360Chrome Extension Manager page. You shouldn't have that nag window if you install your extensions this way.

Cool. Added update notes to first post. Slightly different steps but basically the same process. For users of Roytam releases, the same process is used to update his builds when using the PORTABLE LOADER (you just delete the old BIN folder contents and replace with the NEW files). PORTABLE browsers really are easy to maintain once you get the hang of 'em.

The easiest way is to extract the updated version then use your file manager to navigate to the Chrome\Application folder. In that folder will be two folders (version.x.build.0 [ie 13.5.1030.0] and components) and two .exe files (360chrome and wow_helper). Copy those two folders (and all of their contents and sub-folders) and two .exe files. Now navigate to the folder where your previous files are and navigate to its Chrome\Application folder. Delete the two folders and two .exe files that are already there. Paste the two folders (and all contents and sub-folders) and two .exe files that you copied from the latest update that were extracted in a separate folder. You have to do all of that with 360Chrome closed.

Puts them on par with the way SRWare Iron and Chromium do things by reverting to base functionality and removing Google telemetry. We remove Chinese and Russian telemetry, why would we keep Google telemetry? One of the four embedded Google API's (it's called Cloud Print) has been around since early 2010 in Chrome OS and embedded into Chrome browsers and enabled by default since Chrome v10 in early 2011. Cloud Print (and Adobe Flash) were officially axed in December 2020 - why would we keep them in any "modern" browser rebuild? Those that "want" Flash (or Widevine, as another example, or WebGL and SwiftShader as other examples) generally know how to add them in themselves and also know the risks associated therein. I leave those to user discretion but offer basic functionality out-of-the-box in hopes of greater stability without excess bloatware. I opt to remove a Feedback API and an Identity Scope API for reasons that their name alone should make your skin crawl. I don't recall the fourth one offhand but do know that I remove four API's - I think it was an ancient PDF Viewer where 360Chrome views .pdf's without it so why keep it?

I tested in alpha_10 and it gives the same exact results as rebuild_2.

I've said it a hundred times, what's one more -- WHITELIST JAVASCRIPT !!! Period, end of story! An excerpt -- Disable JavaScript Disabling JavaScript is an effective way of obscuring your browser from being fingerprinted. The reason is that without JavaScript enabled, websites can’t detect what plugins and fonts you have installed. Since this information is a major part of your fingerprint, it’s a good idea to prevent websites from seeing it. That said, many sites require JavaScript to operate effectively, so you might be throwing the baby out with the bathwater. But what if you could get the best of both worlds? One solution is to use a tool like NoScript. NoScript will block JavaScript on all sites by default, but allows you to enable it for the sites you really want to use. The downside is that this has to be done manually, so it does require a little bit of work to be used effectively.

Agreed!

I remove four embedded Google API's in both the "regular" and the "ungoogled". The "ungoogled" goes one step further and breaks Google's cookie policy violation. I do not know if this is the difference in your "font count" or not. If you still have alpha_10 (it still contains all embedded Google API's), does it have the same "font count" as rebuild_1 or rebuild_2 (both have the embedded Google API's removed) ?

Unless I'm missing something, I would think that N/A is actually the PREFERRED result. I don't really see the point of "fingerprint" detection, but it seems to me that the idea behind it is that a web site can "identify" you based on a COMBINATION of results. So even without an accurate FONT detection, you can still be "identified" by the COMBINATION of OTHER "items". Dog chasing its tail, or something like that.

Download links for v13.5 rebuild_2 added to first post. Only change from rebuild_1 is one file inside resources.pak so that Extensions Manager .css matches my v11 and v12 (I need to verify v13.0).

Can it be isolated to any specific to/from email account? Reason I say that is I have a different email client that crashes when-and-only-when Yahoo email accounts are being replied to. The Yahoo header becomes GIGANTIC after two or three replies.

We'll allow it. Since you saved the best for last with that C64 Legos keyboard.

Regarding fonts - I get the same in other browsers. N/A in hidester but a list in deviceinfo. But deviceinfo's list is far from accurate -- only lists 60 of my 76 fonts via 360Chrome v13.5 (did not check in v13.0, v12, or v11), only lists 23 of my 76 fonts in Basilisk 55, Basilisk 52, and New Moon 28. Hidester doesn't work correctly in New Moon 27 or 28.

All v11, v12, v13.0, and v13.5 download links updated in first post.

No qr popup here could be due to I keep host file entries as a precautionary measure even after removing as much telemetry as I can find. Partly because I prefer the host file entries in place due to testing several versions and several builds and not knowing what those versions and builds will try to "telemetize" (I made up that word, no royalties needed, use at will).

Already tried that also. Mini-Browser cannot be an option for me because XP x64 is my primary computer. All seven of my secondary computers run XP x86 as their primary OS but several are dual or triple boot (Win7 x86, Win10 x86 LTSB, Win10 x64 LTSB). One of those secondary computers is running XP x86 SP2 - what a piece of crap SP2 is, in my not-so-humble-and-opinionated opinion. Too many projects going on to dedicate any time to it. My usaged requires the same exact web browser and the same exact profile to function on all eight computers regardless of which operating system I am running at the time.

Cool, thanks. I'll be making v13.5 my daily default once I get to "rebuild_1" (should be later today). Just some minor GUI tidy-up remaining. Saving an official dark theme for later.

Already a step ahead of you. (Because 360Chrome requires wow_helper.) Nope, that doesn't get Mini-Browser to execute on XP x64. That is, if that is the help.exe that comes with the official unmodified download.

I didn't get any error warning, just a crash. It was always when logged in and entering text in the reply box. And it was always very lengthy replies - all lost when the browser crashed. When I was trying to track it down, I would OPEN the reply box but not even type in it. Leave the reply box OPEN and browse in a different window. Sometimes 30 seconds later, sometimes 15 minutes, but MSFN would ALWAYS crash if the reply box was open. I haven't returned to v13 as my default browser on account of random crashes and it happened on versions that I had used for MONTHS unchanged/unmodified without ANY crashes, then all of a sudden the same exact version, brand new profile, would crash left and right. I gave up on v13 and much prefer v12. Even the v13.5 that I've been experimenting with has random lockups only during startup (with or without a profile already in place). No crashes during browsing, just lockups at startup (maybe only 1 in 500 starts, but a lockup is a lockup and I run v12 because it's never had any of the issues that keep popping up with v13). And ONLY on XP.

Cannot replicate. I don't get the qr-code popup. Do you get it on a clean profile? I think I'll just leave the default "Share page", reupload, and call it our official "rebuild_1". Save dark theme for as-time-permits.

I cannot replicate. This could be due to OS-specific font or DPI settings on your computer.

This one might have to stay in the context menu, still digging - it is disabled, it's just still "visible" in the context menu and I've changed it to (disabled feature). This is one of those "added BLOAT" items that didn't exist in ANY of the previous v11, v12, or v13.0 builds.

Download link for v13.5.1030 Beta_2 added to first post. Alpha links removed to free up storage space in Dropbox. Should be 100% functional at this stage - only remaining changes are to remove one minor GUI context menu entry and to create a dark theme.

I see this in the context menu and have placed a "(feature disabled)" placeholder in the menu until I can find where to remove the menu line completely. Kind of a temporary fix for now.

My apologies. I had to clear out my Dropbox to make room for hosting rebuilds and this thread was dead so away they went to free up some storage space.