HardwareBanter - View Single Post

**Paul[_28_]** · January 7th 19, 02:13 PM posted to alt.comp.hardware.pc-homebuilt

wrote:
On Sunday, January 6, 2019 at 1:22:23 AM UTC+1, Char Jackson wrote:
On Sat, 5 Jan 2019 17:58:13 -0500, Bill wrote:

wrote:
Cookies and other "persistent data" from websites is a lagging your browser and system as follows:
I use "CCleaner" to delete mine almost every day. Cookies are
not going to go away any sooner than commercials are going to
disappear from radio and television. May as well get CCleaner,
and "fight the good fight".
If cookies were ever going to "go away", we'd need something very
similar to replace them. They provide a ton of functionality that people
wouldn't be happy to give up. Also, contrary to the claims made in the
first post in this thread, they don't cause lag, slowdowns,
fragmentation, or anything else of that sort.

You wrong about that.

This can be easily seen/monitored via resource monitor from task manager.

Also these cookies are stored in little files.

Each of these little files has to be seeked, causing huge ammounts of i/o wasted on these seeks.

One simple improvement would be if Firefox stores these cookies in a single file.

Though if cookies grow and shrink it might become a bit troublesome.

One idea could be to allocate some additional space per cookie.

Though I would rather see cookies go completely... at least the nags screens... boy are those annoying.

For those that use CCCleaners and delete cookies ? How do you cope with the nag screens ?

Bye,
Skybuck

Firefox cookies are stored in "cookies.sqlite", a single file.

Firefox databases are cross-coupled. You should not edit an
sqlite file, unless using a browser plugin designed for the job.
It is more likely to remove entries across all the sqlite files,
and do it properly.

Seamonkey (a browser derived from Firefox), has a built-in cookie
manager, which allows sqlite edits. There is no convenience function
to delete all cookies in one shot. Instead, you must do the
cookies *one by one* as a form of computer punishment.

Internet Explorer might save cookies as individual files.
Since I don't use IE for surfing, I really don't care how
those are stored. There should not be any.

MSEdge went from the individual file model of Internet Explorer,
back to using a database for them.

When a user disables cookies in the browser, the web site simply
switches to DOM storage, and the DOM storage settings
may be less obvious. On Seamonkey, there is no cleaner for
DOM storage, and I erase them manually. Some of Seamonkey
resources can be set to "delete on shutdown", but DOM storage
is not covered by that.

Browsers can be deceptive when they offer "erase history".
When you do that on Seamonkey, nothing happens. The menu
option is unhooked. If you set the browser to "delete on shutdown",
that covers a portion of the tracking information, but not all
of it. Your job as a browser user, is to figure out what
storage modes are persistent, and delete them in the Trash
Can.

If you delete *all* the sqlite files in Firefox, the Google
"filter" sqlite, the one built by a download happening every
day, that one will need to be downloaded again. Consequently,
you might end up repeating a 70-100MB download each day, if you
delete everything. They were very careful to design the resources
so just about everything you do has "side effects".

For Firefox, I can't find an SQlite Browser for Quantum
(latest) browser versions. Maybe there isn't one ?

Paul