Re: [dev] [surf] [PATCH] cookie policy

From: Nick <suckless-dev_AT_njw.me.uk>
Date: Thu, 30 Jan 2014 14:43:59 +0000

On Thu, Jan 30, 2014 at 02:58:53PM +0100, Christoph Lohmann wrote:
> Such a file should be easily managable using scripts. Match the given
> domain name, surf would use and modify the given modestring. If no host‐
> name was found, add it’s raw value. Users should modify or shorten this
> on her/his own using their sanity.
>
> Any comments?

Good, I like this proposal very much. I had been wanting to add a
'noscript' like feature for some time, but (apart from not having
the time) I couldn't think of a reasonable interface. This sounds
good enough.

Also I recently started using a similar extension on firefox for
cookie management, which is very handy indeed. At present I just
have a little script triggered regularly by cron to delete the
cookie file if I don't have any surf windows open, to ensure no
long-lived tracking cookies, but this proposal would be a much
neater way of handling things.

One thing is that each character of the modestring should be
optional in the mode file, so that surf can just leave them in their
current setting. I'm thinking here of the style.css toggle, which I
generally use according to ambient light conditions, rather than site.

Another consideration is exactly how we want to limit scripts.
There's lots to recommend being able to only enable scripts from
specific domains (rather than all scripts a specific page requests).
The difficulty would be finding out which 3rd party domains are
requesting scripts, so as to add or remove them from the mode file
if necessary. We could just print to stdout, but that would get
quite a lot of noise. Does anybody have any thoughts on this?

Anyway, good idea, thanks Christoph.

Nick
Received on Thu Jan 30 2014 - 15:43:59 CET