NotHereToPlayGames

I've not tried them but have used them in the past, they may work for you. One is called "Actual Window Manager" and the other is called "UltraMon". Neither one is free though but both have trials where you could at least test to see if they fit your needs.

I was originally going to delay all new builds until I had a "dark theme" ready. But to be honest, "dark theme" has never really held my interest as far as staying focused on it for the length of time truly required to critique my own work and deem it "ready". I'll upload new versions that prevent "data collection" in the next day or two.

This is my browser and I've opted to publicly share it. There are HUNDREDS, if not THOUSANDS of web browsers out there. Keep hunting, you MIGHT find one that fits "all" of your needs.

I'll add a note (when I do the next update, not worth the time to add it now) in Post #1 regarding "Preferences" and "Web Data" file when updating. But since there is only ONE complaint regarding them, I see no need to change from how they are packaged. I can't please "everybody" and I kinda don't really see the point in trying to. I'll aim to please the "majority" and that should be sufficient.

It's because my releases are "portable". If they don't work for you, no skin off my back if you don't use them. I can only do so much. I can provide without the "Preferences" and "Web Data" files but then somebody else would complain. If they don't work for you, no skin off my back if you don't use them.

I can't manage your files for you. As far as keeping bookmarks and extensions -- extract new updates to a TEMPORARY location, copy all files EXCEPT "Preference" and "Web Data" to your existing browser location that contains the profile you wish to keep. It should be that easy. Then delete the temporary files that you extracted. I can't manage your files for you.

Does not concern me. We are not forced to use MSFN. If we don't like MSFN, we have options elsewhere. I like MSFN and see nothing nefarious going on. I have no desire to live in a shack in the hills with no running water and no electrcity because of excessive paranoias. We all draw our own line in the sand and it isn't for any of us to tell other people where to draw their line. My two cents... Mileage may vary... To each their own... No animals were harmed in the writing of this post...

No side effects thus far. Will run this way for a couple days but looks like everything is good-to-go.

@msfntor - No, the updates will always be named according to their build and revision. Roytam does it this way for NM27 NM28 Basilisk BNav Kmeleon etc, official 360EE does it this way, official 360SE does it this way, official DcBrowser does it this way, official Pale Moon does it this way, SeaMonkey does it this way, Firefox does it this way, et cetera. All of these can be updated without losing your profile. Simply download the new update to a different location, extract the files, and only copy changed files over to your existing location. Users do not abandon browsers based on update and profile preservation - they learn how to update and preserve their profile, they learn how to migrate their profile. Otherwise Roytam's builds would have died in 2017. @D.Draker - I'm not sure if we should prevent ALL files that the browser creates. I'll experiment with the list and if there are no ill side effects, I certainly have no issue with preventing all of them. I will have to make sure that the folks (not me!) that prefer to close their browser with several tabs open and even with web sites still logged in, that "those types" can still launch and "continue where they left off" (again, not me!, I clear EVERYTHING with EVERY exit).

Thanks! None of those exist in v11 so these may be v13.0 and v13.5 only, I'll include them in all loader .ini's as a better-safe-then-sorry route.

Several of those do not exist and are never created in my setup. So I need to know which ones are created as FOLDERS and which ones are created as FILES in order for me to be able to prevent them. Thanks in advance. edit -- and does that WidevineCdm file/folder exist in the same directory as the above or does it exist in the plugin directory?

That's why! Way too slow of a download speed for that web site. That site is GIGANTIC as far as how many megabytes it is sending you. Very bad coding! They don't even offer you the ability to select a lower video resolution.

What's your download speed? https://www.speakeasy.net/speedtest/ I only get roughly 34 Mbps but that's kind of intentionally slowed down. I get closer to 240 Mbps on LAN but I feel that wireless is much more "secure" so I never connect via LAN.

Kill the d@mn freakishly huge downloaded .mp4's for the top-of-page "shootout" banner and then the video plays without any buffering whatsoever. Watch your download megabytes when you visit that page, that page is GIGANTIC. Terrible coding! No reason in H#LL to need such freakishly gigantic .mp4 videos for the "shootout" banner at the top of the page.

It plays in my v11. It had to buffer a couple of times but that could be just terrible upload speeds on the hosting server or terrible coding such as maybe sending too high of a resolution.

Your un-edited post did not have the "does not support WebGL" note. Maybe I should wait half an hour before doing any replies, lol.

This is related to the same exact reason that your two maps will not load in DcBrowser on meteoblue.com. https://pixlr.com/x/ requires WebGL and SwiftShader.

I've never used 8/8.1 so I have no pony in this race, no dog in the fight. I've always felt it was for "touchscreen" only (which I know it is not "limited" to touchscreens) so I've never had any use for it whatsoever. I like a keyboard and a mouse and use keyboard shortcuts and mouse gestures in not only my web browser but in all of my programs. But I'll throw this in just for fun -- https://www.computerworld.com/article/3575332/the-worst-version-of-windows-ever-released.html and https://techlog360.com/worst-operating-systems/ Oh, and one of the absolute first things I do with Win 10 computers is to get rid of the d@mn start menu "tiles" that 8/8.1 instroduced. Hate hate hate hate hate 'em! Times 1,234,567 hates! Add 8 more hates!

Open the "newtab.zip" file and edit the "new_tab.html" that is inside. You only need to include .js and .css files if your edited "new_tab.html" requires them.

Updated -- In the User Data \ Default folder - 1) create these empty folders a) Network Action Predictor b) Network Persistent State c) Reporting and NEL d) Top Sites e) TransportSecurity f) Visited Links 2) create these files with no extension a) blob_storage b) BudgetDatabase c) DailyBackup d) DailyRollingBackup e) Download Service f) Feature Engagement Tracker g) Platform Notifications h) Service Worker i) Site Characteristics Database j) Sync Data k) Thumbnails l) VideoDecodeStats I plan to have an updated v11 uploaded within the next day or two. Then update v12, v13.0, and v13.5.1030 after feedback on the above to make sure they don't break anything (they don't break anything on my setup). I am also able to place an extensionless "databases" file but only AFTER all of my extensions are installed so it seems safest to allow this folder.

Summary -- In the User Data \ Default folder - 1) create these empty folders a) Network Action Predictor b) Top Sites c) Visited Links 2) create these files with no extension a) blob_storage b) DailyBackup c) Download Service d) Service Worker Please let me know if you see more files/folders that we can prevent.

We can do the reverse for "Top Sites" -- create an empty folder so that the operating system cannot create a file named "Top Sites". Additional files to look into -- "Network Action Predictor" and "Visited Links". Still digging... We should be able to drastically reduce the files/folders that are created. @D.Draker -- Thanks for the nudge

That is very likely because you are on Vista and not XP. I wasn't getting "constant" crashes in v13.0 in XP but enough to not want to run the risk of losing anything. I've never had any crashes in v13.5. But it also uses too much RAM for me to be able to use it on my low-end secondary computers.

This seems to work with no side effects. I'll update the next set of releases with a file by the name of "Service Worker", this prevents the operating system from creating a folder by the name of "Service Worker". Will do some further testing, but we should also be able to do this for the "blob_storage" folder and the "DailyBackup" folder.

An ancient trick -- we have a folder called "service worker", delete the folder and place a "service worker" file without an extension in the same directory by the same name so the operating system cannot create the folder. This works in XP.