Re: Great SWT Program

On Dec 11, 9:28 pm, Arne Vajhøj <a...@xxxxxxxxxx> wrote:
There is this rather unknown browser from a small software
company in Redmond - where if you open two browser
instances independently then it does not share sessions.

What nonsense are you babbling now, arnehole? Every browser I've ever
used saves cookies in a browser-specific directory on disk. If a
matching cookie is there, it will dutifully feed it to the appropriate
server when requesting any URLs from that server. The directory is
sometimes configurable, but changing it every time I switch tabs would
be a nightmare. So would repeated logging out and logging in. So would
trying tricks with the URL, such as using http://ip-address/path/file
in one tab so the browser doesn't consider it the same host and
doesn't send the cookie.

Two independent browser instances of the same browser installation
will still share a cookie, since the installation has only one cookie
directory on disk at a time, and a cookie one instance saves there
will of course be visible to the other instance. There can't be two
different versions of the filesystem, one for each instance, after
all. Nor can cookies not be written to disk at all, not if you don't
want to lose them whenever you exit the browser. At best, the thing
you're suggesting could only work when a high privacy level was set
that blocks cookies being persisted. Such a setting results in
constantly having to login everywhere (not just at Google fucking
Groups, where I have to anyway due to their broken and brain-dead spam-
filtering strategy) and other problems though. I use adblock to cut
down on evil tracking cookies (by having the browser never even touch
the advertising sites that send most of 'em) and antispyware sweeps
every so often nail the ones that got by adblock, so they never last
more than a week or two. :P (The real solution to tracking cookies,
though, is probably to add an ignore-cookies-sent-with-inline-elements
option to browsers. So if the page actually explicitly requested
(whose URL is in the address bar) sets a cookie, it's set, but if some
460x60 .gif in an <img> tag comes with a cookie, the cookie is
dropped. Extra points if there's an option to also drop the
image, .js, or other file that came with it. That alone would nail a
lot of ads and non-user-beneficial bandwidth-wasting .js cruft right
there, even before applying additional filters such as adblock.
Alternatively, it could work this way: request a page from foo.com,
and cookies sent by foo.com for that page and elements in that page
are set, but cookies sent by any bar.com != foo.com with other page
elements may be crunched if desired, as may the elements themselves.
Sending cookies likewise -- only to foo.com when visiting a foo.com
address, even if there's a cookie for bar.com on the hard drive and an
image loaded from bar.com on the page.)
.