NotHereToPlayGames

I agree. It does "collect" but it is not sent. That's the best I've found so far. "official" Pale Moon, NM27, and NM28 all do this also. If you run them as portables and compare file structure periodically, you will find a file with the name "telemetry" right in it! I've witnessed it at least a dozen times over the years. I've never actually witnessed its "collection" being sent anywhere, but it is being collected. I no longer care for those browsers and do not recall the specific "triggers" which cause the "telemetry" file to be created, but it is there. If I recall, it shows up in your User Data folder and not inside your portable file structure. It deletes itself and leaves an empty folder in your User Data folder. I have seen the MSFN entry. At first I thought the v13.0 crashes here at MSFN were somehow related to it but I could not prove it at the time.

It is my experience that the font/image issue referenced in your screencap is not due to tab freezing (introduced in Chrome 79). I have seen this a small number of times in 360Chrome v11 (based on Chrome 69). I have only witnessed this in Stylus's edit style sheet window. My debug fix (which seems to have fixed it) was to tweak Stylus's code so that the mouse cursor does not flash on and off. I wouldn't call this a permanent solution but just a debug test - what it makes me curious of is that if all of the websites that we witness this font/image issue with has a "flashing cursor" or not. ie, the flashing cursor in this text box when we type replies.

I delete both of these with every exit of 360Chrome in my personal-use copies. The problem with publicly providing a portable version is that it has to work "out of the box" for 'all' users. I delete these in the more matured releases (see loader .ini in v13.0 rebuild 4 as an example). But what happned was that half of the beta testers did not like not being able to "restore previous session" at launch, or that forum logins were not remembered from one launch to the next, et cetera. So the loader .ini was reverted to a "session-restore" version. This appeased the half of beta testers that wished to maintain cookies between sessions and the other half did not complain - so all was "good". The more advanced (that includes D.Draker as he does strike me as a more advanced type of user) will always have to edit the loader .ini to their more advanced needs. This is also ONE of the reasons I am proposing a "Builder" frontend - but it was immediately hit with "no, you need to minimize file size, not add to it!" You see the dilemma? You really can NOT, no matter how hard you try, you can NOT make 'everybody' "happy".

I've used uMatrix and uBlock both over the years (not at the same time, though I've heard of a few that have ran both at the same time). The GUI text for uBlock was always horrendous in my opinion, but I am using a frame of reference roughly 2 to 4 years ago, the GUI could be improved in recent builds for all I know. uMatrix has always seemed like a more OCD Approach -- I am OCD and it has served me well over the years, lol.

Agreed. But I go one step further, in my opinion. I do NOT let my uMatrix lists "update themselves". Nothing says "telemetry" more than allowing something to "update itself".

And the funniest part, it's the folks that label themselves as "unifying" that DIVIDE US THE MOST.

Don't eversell it, you've cited some gigantic negatives with DcBrowser over the past couple of months also. Here's one, I didn't want to go digging up all of them -- https://msfn.org/board/topic/182993-360-extreme-explorer-arcticfoxie-versions/?do=findComment&comment=1208299 I may end up doing a build with it "eventually", but as-is I have too much on my plate already.

Be sure to read their Privacy Policy. Some extensions claim "security" but it comes at a gigantic invasion on "privacy". So you have to balance "security breach 20% of the time" with "privacy breach 100% of the time".

My second first car when I was a teenager was a '74 Mercury Bobcat (second was an '84 Plymouth Horizon). Basically 99% identical to the Ford Pinto - only difference was an all-glass hatchback. Paid $100 for it, spent an afternoon putting a new rear main seal in it, drove it for six months or so, sold it for $600.

I would buy a Ford Pinto in a heartbeat if I ever found one! Maybe then people would stop tailgating me! Here's what most people don't remember - Ford WON the lawsuit that "claimed" their vehicles caught fire when rear-ended. The Pinto had the same EXACT flaw that every other car on the road had -- rear axle lined up even with the gas tank.

Took a few looks to see it, but yes, that does look inaccurate. That first screencap posting the same exact number for seven different processes is definitely inaccurate.

It 100% sure is, definitelly. I guess my main point is that your releases do not break the Google Cookie user-preference violation and ungoogled Chromium builds do. But I do also understand why that makes your builds better for the "as-is" crowd that is a tad bit less savvy on various Chrome workarounds like installing an extension without using the Chrome Web Store. Keep up the good work!

Humming Owl will not see this in the thread that you posted it in. This thread is my builds and DcBrowser is a Humming Owl build. Please report DcBrowser findings/requests in Humming Owl's thread - you know where it is.

I'd be open to adding a checkbox row for "with WebGL and SwiftShader" and "without WebGL and SwiftShader". But a reminder that a "top-level" 'developemental' approach to having tons of options because no one release is going to make 'everybody' "happy" does increase the file size of the end product. Some of us just won't be "happy" no matter what, but this is an attempt at "trying" to appease the masses.

ps - why do you report DcBrowser findings in this thread? DcBrowser is a Humming Owl release and I've seen too much telemetry not yet removed so I no longer even have access to it. Shouldn't those findings be posted in Humming Owl's thread?

Have you tried using about:blank as the empty tab instead of using a chrome://newtab/ (which is the URL for the default "new tab"). Other than that, the difference between 19,904 and 16,940 is tiny, relatively speaking. I have not loaded "Dark Empty New Tab" for my own compare-contrast.

FYI - I would not refer to your builds as Ungoogled because the Chrome Web Store feature needs broken to be truly in-step with standard Ungoogled Chromium.

I think the Preference file's accept_languages file also needs changed. There are portions that seem to go by language pak file name. But I seem to see just as many portions that go by accept_languages. Not sure how these are passed on to the visited website. It just seems that both are required for best language compatibility. "It all looks Greek to me."

Please don't make "demands". Please make "requests" instead. Clearly a "language barrier". Not worth "arguing". Have a great day!

If you want WebGL, that's on you. It is a security risk and unneeded. I have removed it for a reason and I will not be adding it back in. Again, if you want WebGL, that's on you.

My neighbor 1/4 mile down the road just called. She wanted to know why I was laughing so loud and that she heard me all the way over at her house.

I have already answered this question. You have to enable WebGL and copy switftshader folder and the .dll mentioned when I answered this question the first time. You put a "like" on it, so I know you saw it.

Seriously - uncalled for !!!

Have you ever looked up the informal definition of "high maintenance"? I wouldn't add an extension just to change an empty New Tab. You can create your own New Tab and be creative as you want with it (I personally don't use "bookmarks" and use my own New Tab with all of my favorite links). Place this file in the same folder that contains "chrome.dll" (and test by disabling "Dark Empty New Tab") -- https://www.dropbox.com/s/5yy90s71jcnu5qw/newtab.zip It's nothing more than an .html file inside a .zip and you can be as creative as you want with it, limited only by your own imagination. Uncalled for !!! What you define as a "problem" does not qualify for what others define as a "problem". Some of your "problems" really do require you to start learning how to do some of these modifications yourself instead of thinking us "developers" are here at your becking call.