
NotHereToPlayGames
MemberContent Type
Profiles
Forums
Events
Everything posted by NotHereToPlayGames
-
I'm going to revert back to the previous editions for now. Advanced users can alway opt to have their own local versions perform the data-write-preventions. I think we have a Law of Unintended Consequences going on and too many UNKNOWNS. I did suspect this, but wanted to see what others encountered also. To me, I see too much of the possibility of "memory leak" - since we can't write to the hard drive, the data resides in RAM instead. In-process of reverting changes. It is something that the advanced users can decide for themselves if they wish to have their own local copies prevent data-writes.
-
It's a matter of perspective. MOST users that I encounter see this as "value ADD" because they typed something and they don't have to type it AGAIN if they accidentally close the tab or their browser crashes and they lose the tab. edit - but I agree, I kinda find it disturbing and I myself would rather retype content that was accidentally lost.
-
v13.5 V3 does this connection also. But only on FIRST RUN. Since v13.5 V4 prevents various files from being written, it performs the connection with EVERY LAUNCH because it doesn't have the logged record that it already made the connection once. Still digging... Leads me to believe that v13.5 branch requires some additional telemetry removals that were not discovered until just now. I'd kinda recommend v13.0 branch until further notice (unless of course the possible telemetry doesn't concern you until resolved).
-
I actually use TWO loader.ini files - one for "during" installing extensions because "some" extensions require this .log file in order for the settings to apply with the NEXT launch. I use this for "during" installing extensions -- FileDelete=%Profile%\Default\Local Storage\leveldb\LOCK;LOG;LOG.old Then I use this AFTER my extensions are installed -- FileDelete=%Profile%\Default\Local Storage\leveldb\LOCK;LOG;LOG.old;*.log The only difference being the ;*.log at the very end.
-
I have a dark theme I've been playing around with. But it is specifically tailored to look like XP. A very dark XP, but still XP. I really do have an immense hatred for 99.99% of my programs having the default XP "buttons" but "new" Chrome/Chromium/360Chrome/Firefox-Australis not having that XP "look". But I'm sure the same goes for you, you run Vista and you wanted an aero theme, so that makes perfect sense to me. I wouldn't mind having a copy of the Vista aero theme if you are allowed to share it. EVENTUALLY my skin folder will have options for end-users to pick from.
-
v13.5-r4 should have added 23 empty folders and 21 zero-byte files. Windows will not allow a file and a folder to be the same exact name in the same exact folder so by having an empy folder with a certain name prevents 360Chrome from creating a file with the same name and vice versa for creating a folder when the same-named file is already present. Windows does allow copy-paste a folder and overwrite a file, but will throw an error if you try to copy-paste a file and overwrite a folder.
-
The files replacing folders is to prevent telemetry "writes". We have prevented them from being sent to any Chinese IP Address but now we go one step futher and prevent them from being written even "temporarily". There was a minor XP Theme skin change for bookmark "padding", but other than that there was no major changes. Will revert the "File System" tweak, many thanks! Please let me know if you encounter anything else.
-
What do other users have as far as file contents in this folder - <root folder> \ Chrome \ User Data \ Default \ Local Storage \ leveldb ? You may have something in your Operating System's "temp" folder also. For me, the .log file ID number will change periodically but that may be because I delete this file with every exit of 360Chrome. This .log file logs the REPLY text box here at MSFN.
-
Updated download links in first post. Reminder that there is no profile migration tool as of yet and reminder that this release has to copy FILES with a given name and overwrite FOLDERS with the SAME NAME (which Windows will prevent you from doing). If you wish to preserve your existing profile (bookmarks, extensions, settings), you will need to do this MANUALLY.
-
I agree! It actually kind of annoys me that every time I turn around, somebody wants to squeeze the turnip 'in the name of' "security" or "privacy". (a red herring) We've prevented the telemetry in 360Chrome. But that wasn't good enough, now we are preventing files from logging websites. (a very good advancement, I add) But not only is that not good enough, we have the double-edge sword of "no one gives a d@mn" and "what other files/folders can we safely block". Both can't be true at the same time. I think I have every file/folder blocked in v11, v12, and v13.5. I'll upload files after I get v13.0 caught up. There will be no "dark theme" improvements with this set of uploads - maybe later, maybe not. ps - the Web Data file is where 360Chrome remembers your preference to not send usage statistic "feedback", this feature is "broken" but I prefer the flag to be set to not "participate" in the "feedback program", this setting defaults to "yes, I'll participate in the feedback program" when you delete the Web Data file and allow 360Chrome to create a new one.
-
Updating first post to include two types of downloads - one download for new users starting with an empty profile, a second download for current users which need to keep their current profile. May end up no longer maintaining an XP x86 SP2 version of v11 since I don't think any of the x86 SP2 folks are using v11 anyway.
-
Regarding data collection -- I urge users of v13.5 to monitor their <root folder> \ Chrome \ User Data \ Default \ Local Storage \ leveldb folder and the files contained within it. The .log file in particular logs timestamps and was always able to be deleted on exit in v11 and v12 -- but if you delete on exit in v13.5 then some extensions will lose their settings and revert to default settings. edit - in v13.5, this log file keylogged my entire post as I was typing it! it's also keylogged in v11 but in v11 I can delete-on-exit without any of my extensions losing their settings. So in v11, every browsing session is started wtih an EMPTY .log file and therefore the .ldb files don't keep growing. But I can only delete the .log file on every exit AFTER my profile is created and I've set all of my extensions' settings.
-
Good deal! Yeah, popup blockers were vital twenty years ago but there is no real use for them nowadays when script-blocking is so much more effective - and protects agains so much more than just popups.
- 2,340 replies
-
1