NotHereToPlayGames
MemberContent Type
Profiles
Forums
Events
Everything posted by NotHereToPlayGames
-
Correct, "normal" in-browser means will not delete the Google cookie. I for one cannot blindly trust a Google cookie on a Google web browser that has a "delete cookies" user-preference but ignores the user-preference and applies its own hidden rules toward that Google cookie. I use Google for search and for translate (but not the built-in context menu translate). Everything web-based Google works without allowing the telemetry from the Chrome Web Store setting a Google cookie. Having to install extensions through other methods is a small price to pay.
-
My Browser Builds (Part 4)
NotHereToPlayGames replied to roytam1's topic in Browsers working on Older NT-Family OSes
-
I stopped upgrading mine at v4.17.4808.
- 1,227 replies
-
3
-
- Server 2008
- software
-
(and 1 more)
Tagged with:
-
I would not use either on Vista. I would use (and do use) v94 forks for anything I run with Vista or higher. I have no need for anything higher than v94. And there is no such thing as "future proof" - we can only find what works for us "today" and we have to decide for ourselves if we want to be a dog chasing its tail with constant updates that gain us nothing or if we are content with running "old" and not having to deal with the hassle and nuisance of constantly upgrading.
-
My Browser Builds (Part 4)
NotHereToPlayGames replied to roytam1's topic in Browsers working on Older NT-Family OSes
That seems to be pretty common when you have .css/.js coming in from SEVERAL web sites and "one" of those SEVERAL gets blocked. -
You have to have one or the other, you can't have both. Enabling Chrome Web Store to funtion "as intended" also enables a cookie that you can not delete, a cookie that sends telemetry to Google, a cookie that you can not delete, a cookie that talks with each and every web site you ever visit, a cookie that you can not delete, a cookie that tracks your web usage across all browsing sessions, a cookie that you can not delete, a cookie that is even set in Incognito Mode, a cookie that you can not delete. This cookie is constantly sending "data" to Google. You don't have to sell your soul to Google to download extensions. There are better ways. I'm not so privacy-conscious that I wear a tin foil hat, but things like blocking this Google cookie doesn't require any tin foil. But I do cook all of my Christmas cookies on foil because then the cookie pan last a very long time.
-
re: Disable pop-ups - Yeah, I always prefer my Proxomitron determining what a pop-up is versus my browser. For example, 360Chrome won't let me visit my credit card's FICO page because 360Chrome thinks it's a "pop-up". re: Use custom font size - Can you show a picture of this ever working in any of the 360Chrome builds?