NotHereToPlayGames

Right you are! Apologies, I should have did a trial-run first. Still should be quite easy. I suspect that 360Chrome's "loader" can be configured to run Supermium. That "loader" has the ability to delete files when the browser that it launches is closed. I have not tried, but it "should" work. Would take several folder/config differences and is not just a "copy Supermium and overwrite 360Chrome" process. There are several other "loader" obtions as well. Or, even just a simple .bat file to launch Supermium (I myself prefer actual "loaders" over .bat files). But .bat files are "extremely easy" and anybody with a keyboard should be able to figure them out.

If you are serious about having Supermium delete them after it quits, this CAN EASILY BE DONE by adding Chrome++ to Supermium then adding one line to Chrome++'s .ini file to silently and invisibly run a .bat file every time you quit Supermium.

This really should scare the living sh&t out of you. Not to scare-tactic or anything, but the "normal" behavior is for there to only be ONE folder and ONE file. The folder is basically always there, the file is erased and recreated by the browser over and over and over. If I were you, I would rebuild my profile ONE STEP AT A TIME. First verify if I only have ONE folder and ONE file with a brand new profile !!! !!! !!! Then rebuild my profile ONE STEP AT A TIME, one variable changed at a time, and track down just what I did that made Supermium start acting NOT-NORMAL.

It should also be noted that this has already been discussed at GitHub and the Supermium developer has already stated that Supermium's --ungoogled-supermium PREVENTS ANY POSSIBILITY OF THE TRANSMISSION OF THE DATA. Which, for the record, is how Official Ungoogled deals with BrowserMetrics also. Full read - https://github.com/win32ss/supermium/issues/1110 Excerpt -

I do! I don't stare at the logs while they are being written but if it lands in the log, then I know more needs done to axe telemetry. I read the log line by line each and ever day. AGREED! It should not be written in the first place! Recording the data is one thing. SENDING it is another. SENDING it is easy to prevent. Perhaps the Supermium developer took the "easy route" - record the data, but don't send it. Only a GitHub Issue would get the developer's response.

I cannot test this in Supermium (I have in the past) at the moment but give this as a Testing Method for anyone interested in PROVING THAT A BROWSERMETRICS FILE IS **NOT** "SENT" ANYWHERE. For one, the minimum file size for this BrowserMetrics file is 4 MB. That's a LARGE file and cannot be "sent" without catching it in the act, it just can't happen, 4 MB is HUGE and not a "blip on the radar" that a blink of the eye would "miss". 1) Launch System Informer or something similar so that you can see how many chrome.exe processes are running. 2) Launch DNSQuerySniffer or something similar to catch DNS activity. 3) Open your file explorer to where your BrowserMetrics file is written. 4) Launch Supermium - do not visit any web sites... let it sit IDLE for TWO FULL MINUTES... 5) Watch how many chrome.exe processes are running via System Informer or similar 6) You will see a chrome.exe process close - continue to not visit any web sites... continue to let sit IDLE... 7) You will see a couple more chrome.exe processes close - continue to not visit any web sites... continue to let sit IDLE... 8) You will see another chrome.exe process close and you will see a BrowserMetrics file eventually written - if not, exit Supermium, let all processes close, relaunch, and LET IT SIT IDLE... 9) Keep doing this over and over and over, launch Supermium, LET IT SIT IDLE, wait for BrowserMetrics to be created, exit, relaunch, LET IT SIT IDLE, over and over and over 10) NO DNS ENTRIES SHOULD EVER BE CREATED DURING ALL OF THIS I still only use Supermium R5. I have never witnessed it sending out BrowserMetrics. I only have one file that gets created, it deletes itself, then it recreates itself. I have never seen it being sent anywhere. Anything more than that, then I revert to this - submit on GitHub.

Don't listen to unproven Conspiracy Theories. Totally disconnect yourself from the internet, disable your network card, you name it. *IF* this Conspiracy Theory were true, then a TOTALLY UNCONNECTED browser would pile these up left and right "because they were not successfuly sent".

Not true.

Same here, I only ever have one of them. If you clear your cache at exit, this file deletes itself at the next launch, but recreates if that session remains open for a certain amount of time.

More precisely, there are instructions in this post and the post right after it -- https://github.com/win32ss/supermium/issues/684#issuecomment-2451508665 My Ghidra is still decompiling chrome.dll. It would be faster if I didn't have to go through Ghidra and if folks already know the address for Supermium v132 and how to locate in Brave's chrome.dll. Still digging but I for one do not want the chrome_url_fetcher_* folders but don't really want to just keep deleting them all the time, I don't want them created in the first place!

Has any of the Supermium Users modified their chrome.dll to prevent chrome_url_fetcher_* folders from being added to AppData Local Temp?

It kind of does. Which would also explain why I *wasted* three days and countless hours trying to find any RGB difference and FOUND NONE! I only looked while in "normal" mode.

More precisely, there are instructions in this post and the post right after it -- https://github.com/win32ss/supermium/issues/684#issuecomment-2451508665 My Ghidra is still decompiling chrome.dll. It would be faster if I didn't have to go through Ghidra and if folks already know the address for Supermium v132 and how to locate in Brave's chrome.dll. Still digging but I for one do not want the chrome_url_fetcher_* folders but don't really want to just keep deleting them all the time, I don't want them created in the first place!

Let's bring this B U L L S H I T back on topic! Has any of the Supermium Users modified their chrome.dll to prevent chrome_url_fetcher_* folders from being added to AppData Local Temp?

Not me! Please stop "judging" my socio-economic class. I may not live in a "tourist attraction", but I could if I "wanted" to!

*ALL* dark-mode users. It's not they that keep PICKING BS FIGHTS over trivial S H I T !!! !!!

What is OLED? Is that my TV or my monitor, I really don't remember, NOR CARE. I don't recall without digging through credit card statements or whatnot how old my monitors are. For one, *I* don't care, only *YOU* do. Your obscession, not mine. I really DO NOT UNDERSTAND why *YOU* hang on my every word. Sure, I threw out "less than 10", who the H#LL CARES how old my "less than 10" are except for the PICK-A-FIGHT *BS* here at MSFN ???

I never said near 10. I also never said LED. Moving on... What I have in my living room and computer room really is NONE of your business. You just like to "pick fights" and for some ungodly reason, my monitors have a target on their back. Not sure where, 'cause I'm sitting right in front of them and can't see the target. And I have 20/20 vision. This is just *YOU* "picking fights", plain and simple. Moving on...

Fair enough, THAT I can agree to (we knew the INACTIVE tab bar changed). It's still a gigantic PITFA that the complaints about brightness have never actually been precisely pinpointed and I spent hours upon hours hunting through RGB .css declarations and could not find ANY color differences! NONE! NOBODY said to look at the context menu! So I do not believe for one second that the original "complaint" was a context menu! Not for one second. I tried and tried to "help" but the story kept changing as to "where" this "brightness" is located! One day was complaints about "piercing white". The next day it was complaints about "acid blue". Seriously, from this side of things, the story kept changing!

Cool. But this *CAN NOT* be the same *COMPLAINT* that the dark mode users have been *COMPLAINING* about here at MSFN because *NOBODY* has said *ANYTHING* about #native-ui-style OR context menus. Q. E. D. We're just keep throwing noodles at the wall until one of them finally sticks. ie, changing the story along the way until we finally have a "detail" that *matches* and then claiming that was the "detail" being cited all along (but we all know better).

Wrong again! "Proper" is relative. It's all relative. Heck, when I travel just my own country, I hear dialects that sound like they stopped school in the 3rd grade. I do not tell them how to talk and spell, WHY DO YOU INSIST SO MUCH ON IT ???

No it is not! I am an American. We are not British since the Red Coats were defeated.

I know you and your crew are doing this on purpose (too sequential to not be on purpose). You said 20 in one post, one of your followers then said 30, now you're at 40. I give it four days for somebody to call my less-than-10-year-old monitor 50 years old. H#LL NO!

Didn't look and the way I see it, I spend too much time hunting down things like this "for you" and they end in nothing but Circle Jerk Diatribes from both sides of the equation. So no, I have no plans to "engage". You are a Smart Fellow and know how to track down "odd behavior" (American English, and YES, I am "allowed" to use American English). Why ask me to do it "for you"? Moving on... "Toodles"... edit - I can report that his Brave build does break Brave's phone-home update-check at each and every launch, but his Brave build also breaks Widevine on Netflix. Have not dug any deeper as of yet. Widevine and portable flags are my *only* reasons for needing anything outside of Official Ungoogled. I'd actually much rather use Supermium for Widevine/Netflix but that may never get "hacked". To be honest, I kind of blame MSFN, lol. I used to *NEVER* "stream" via computer. Now I do nothing but stream via computer. No more "smart TV", no more Roku, it's all done via computer plus userscripts, plus userstyles, plus extensions, etc. I don't even "watch TV" anymore, I stream *everything* and LOVE IT! No "ads", just a muted screen and a still-life image, "Commercial Break. Be Back Soon."

I have used one of his releases, he already has an ungoogled portable - https://github.com/e3kskoy7wqk/Chromium-for-windows-7/releases/tag/ungoogled-chromium_133.0.6943.126 Sure, it's "only" v133 instead of "cutting edge". I started experimenting with his when he released an ungoogled v132 - https://github.com/e3kskoy7wqk/Chromium-for-windows-7/releases/tag/ungoogled-chromium_132.0.6834.159