From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] cookie_monster
Date: Wed, 29 Oct 2014 16:45:56 +0000 (UTC) [thread overview]
Message-ID: <loom.20141029T173807-659@post.gmane.org> (raw)
Ok,
So looking at ~/.mozilla/seamonkey/<dir>/
I see these cookies files:
cookies.sqlite cookies.sqlite-shm cookies.sqlite-wal
But the are sqlite files. So I need a gui tool to view them as to discern
logical understanding of what exactly they are and which do delete
or intelligently pre_filter. [1,2]
Any suggestions in portage or as a seamonkey "add-on" would
be keen. I run "no-scipts" but I think I need more to keep
the cookie_monster under control? suggesions? I also use
firefox, just not as much.
James
[1] http://sourceforge.net/projects/sqlitebrowser/
[2] https://www.bestvpn.com/blog/8177/super-cookies-flash-cookies/
next reply other threads:[~2014-10-29 16:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 16:45 James [this message]
2014-10-29 23:44 ` [gentoo-user] cookie_monster Walter Dnes
2014-10-30 10:50 ` Mick
2014-10-30 15:32 ` [gentoo-user] cookie_monster James
2014-10-30 22:37 ` »Q«
2014-10-31 21:10 ` Walter Dnes
2014-11-01 14:50 ` James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20141029T173807-659@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox