Open jonathanKingston opened 7 years ago
After viewing archive.org links loads I have 7976 bytes of cookie data... we need some smarter way of filtering this.
Should I change the expiry of all cookies to be a period of minutes perhaps? /cc @bunnybooboo
JS API for cookies is one of the issues here:
document.watch("cookie", function (id, oldval, newval) {
return newVal + ';path=/save/....';
})
Mine was terrifyingly long just now. Did not really understand what I was looking at initially. Time sensitive expiry makes sense but would that effect the sandboxing?
The jail cookies and archive.org cookies are currently not shared nor do I think the extension should try and make that possible (too many web apis to screw up pushing data etc).
I think the issues are purely around JS cookies from websites, the path we get for them are '/' by default which makes the cookie list very noisy. My suggestion is to try changing the path of these for now by injecting in a script to catch the websites using JS to create cookies.
Delete them....