NotHereToPlayGames

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.

I was actually toying around with a "Halloween Edition" but time kinda got away from me and it's taking more time than expected. A witch flying to the left for "back", a zombie walking to the right for "forward", a black cat with a swooping tail for "restore", a tombstone for "home", a witch's pot for "bookmarks", a pumpkin for the "menu". Orange text on a dark gray background (which was planned to evolve into green text on a dark gray background for a "Matrix Edition"). It was more for fun as an interim before an official "dark theme" but like I say, time kinda got away from me.

Found this and this will be resolved in Beta_2.

For what it is worth, my version of v13.0 ( this thread ) also crashes here at MSFN. It started crashing here at MSFN roughly two months or so ago, I forgot when exactly but I dropped down to v12 as my default and haven't had any issues since. I am in-process of rebuilding a v13.5 but I have not used it extensively enough to see if it suffers the same crashes that v13.0 suffers. Other users have been testing it and have better stability with v13.5 then they had with v13.0. @Humming Owl - my WinXP is unmodified, my x64 is an unhacked official SP2 and my x86 is an unhacked official SP3 with none of the POS updates (and I always have to laugh that they called them POS). It is tweaked as far as not running any of the useless services and Internet Explorer is disabled with file name trickery, but all of my OS's are unhacked, no kernel patches, no certificate store hacks, et cetera. And my v13.0, your v13.0, Dixel's v13.0, the original Chinese (several builds), and the Russian Repack (several builds) all crash here at MSFN. I've abandoned trying to figure out "why" and just moved to v12 instead. Maybe v13.5 in the future, unsure as of yet.

I'm not really sure what that speed optimization setting is supposed to do.

It really all boils down to USER PREFERENCE. There is no such thing as a "best browser". Operating system plays a role. Available RAM plays a role. Can the same browser be used on six different computers running different operating systems and different RAM and clock spec's all play a role. Browser A will always perform best on web site U, V, and W. Browser B will always perform best on web site X, Y, and Z. Browser C will always have a GUI more intuitive and ergonomic than Browser D. Browser E will always handle RAM better than Browser F. Browser G will have a wider range of available extensions than Browser H. et cetera... It all boils down to USER PREFERENCE, what balance best fits the USER.