search

Lusito / forget-me-not

Make the browser forget website data, except for the data you want to keep.
zlib License
226 stars 25 forks source link

Protecting/removing single cookies #17

Closed Lusito closed 6 years ago

Lusito commented 6 years ago

A request from Reddit:

I'd like to preserve individual cookies. Some sites use one cookie to track the user and another cookie to control presentation, like the number of search results per page. I would like to nuke/block the tracker cookie but keep the presentation cookie. A whitelist, maybe with with regexp, might be a good way to accomplish this.

The behaviour for this needs to be elaborated first: I guess if a single cookie can be whitelisted, then the domain itself should not be whitelisted by the user (so when the normal removal kicks in, whitelisted cookies are protected).

Example User wants one cookie at domain xy.com to remain, but others to be removed. User will not whitelist xy.com, but instead create a cookie protector for the pair of (cookiename@xy.com).

OhSoGood commented 6 years ago

Hi @Lusito Any news about this enhancement? That would really be so great.... Thank you!

Lusito commented 6 years ago

Hi @OhSoGood This is quite high on my priorities, but as mentioned in other topics, I've been busy moving to a new city and just got internet hooked up again, so it might still take some time.

Even worse, mozilla just disabled the extension because they couldn't reproduce the obfuscated code, and I had to submit a new version. I hope this works for them now..

OhSoGood commented 6 years ago

Good setup so! May I ask why you obfuscated part of the code if the extension is opensource? That could be seen as weird and even as suspect by some...

Lusito commented 6 years ago

I use webpack to compile multiple files together so there are only 5 in the result. Each file only uses those parts of the code it actually needs, to avoid long parsing times. Code compression reduces the overall download size and also reduces parsing time.

The code obfuscation is only a side effect of the code compression. Obfuscated code is really only visible to those extracting the extension zip file. Anyone who is willing to do that can just as easily click on the github link.

Joel889 commented 6 years ago

Unless I'm missing something, protecting individual cookies is currently somewhat cumbersome. One has to find the cookie name going through Firefox's options, go back to the addon and manually add it to the addon's dialog.

I think something similar to Cookie Keeper, that shows a list of current cookies, that can then be individually tagged would be great. But I guess that would require implementing https://github.com/Lusito/forget-me-not/issues/9 first.

Lusito commented 6 years ago

Yes, cookie name rules are currently more of an expert setting. There are other voices saying a simpler UI for newcomers might be a good idea, so I'll look into making things more comfortable once the kinks have been worked out and maybe other feature requests have popped up to help define what is going to be the next look & feel of FMN.