4 ms·

I want the dialog to be part of the browser, not the website. Similar or same as the "corporation.com wants to know your location" pop-up box. in the browser's

by dbtc 4y ago

I want the dialog to be part of the browser, not the website. Similar or same as the "corporation.com wants to know your location" pop-up box. in the browser's settings: [] only allow login cookies (and maybe some other standard essential) [] ask every time [] gimme all the cookies... How would this work? Maybe a w3m-standard for various cookie types? An API for the common things that are done with cookies? The browsers need to provide a method to persist those essential data such that it can only be used for that intended purpose. Then all 'un-standard' cookies can be blocked per User's preference. Sites that really do need extra cookie features must convince the user.

pessimizer 4y ago
An old XUL addon for Firefox called Cookie Monster had this perfect. First, set a default of either accepting all cookies, accepting cookies but deleting them after you close all the tabs from that site, or accepting no cookies. Then, per site, you can change that site default to a different setting than your global default. Then, you can temporarily override the site default, but that override will revert after you close the browser session (or you can manually clear the override so it goes back to the site default.) These settings are separate for first-party and third-party cookies. It didn't handle localStorage because that wasn't a thing when it was written. IIRC you could also delete all cookies from the current site manually, or open up a window to view all of them (and delete them individually from that window.) All of these functions were a click and a drag away, and none deeper than a secondary menu. What I'm saying is if the bizarre restrictions that both Firefox and Chrome have put on browser extensions keep this from being packaged as an addon any more, build a browser that has it built in. edit: add to that a global toggle for popups when sites make cookie/localStorage requests that you've set to be denied, and that's a pretty complete featureset for me.
- rrix2 4y ago
  I have been slowly populating Cookie AutoDelete with rules: https://addons.mozilla.org/en-US/firefox/addon/cookie-autodelete/ https://addons.mozilla.org/en-US/firefox/addon/cookie-autode... Still not ready to enable the scheduled deletion but I clear it once a week to find new things I need to whitelist. It can handle all storage types and even has some limited support for tab containers. Setting up the rules is time consuming though.
  - cpeterso 4y ago
    If an extension supports user-defined rules, rules lists could be crowdsourced and/or delegated to dynamic lists downloaded from a server (like uBlock Origin). The “I don’t care about cookies” extension is a good example: https://addons.mozilla.org/en-US/firefox/addon/i-dont-care-about-cookies/ https://addons.mozilla.org/en-US/firefox/addon/i-dont-care-a... . The extension even has UI for users to report websites whose cookie popup are not known by the extension. The first step might be creating a shared JS library for generic remote list management (periodically checking for updates, downloading lists, managing local list versioning) that extension developers can use in their extensions.

by dbtc 4y ago

pessimizer 4y ago

An old XUL addon for Firefox called Cookie Monster had this perfect. First, set a default of either accepting all cookies, accepting cookies but deleting them after you close all the tabs from that site, or accepting no cookies. Then, per site, you can change that site default to a different setting than your global default. Then, you can temporarily override the site default, but that override will revert after you close the browser session (or you can manually clear the override so it goes back to the site default.) These settings are separate for first-party and third-party cookies. It didn't handle localStorage because that wasn't a thing when it was written. IIRC you could also delete all cookies from the current site manually, or open up a window to view all of them (and delete them individually from that window.) All of these functions were a click and a drag away, and none deeper than a secondary menu. What I'm saying is if the bizarre restrictions that both Firefox and Chrome have put on browser extensions keep this from being packaged as an addon any more, build a browser that has it built in. edit: add to that a global toggle for popups when sites make cookie/localStorage requests that you've set to be denied, and that's a pretty complete featureset for me.

rrix2 4y ago
I have been slowly populating Cookie AutoDelete with rules: https://addons.mozilla.org/en-US/firefox/addon/cookie-autodelete/ https://addons.mozilla.org/en-US/firefox/addon/cookie-autode... Still not ready to enable the scheduled deletion but I clear it once a week to find new things I need to whitelist. It can handle all storage types and even has some limited support for tab containers. Setting up the rules is time consuming though.
- cpeterso 4y ago
  If an extension supports user-defined rules, rules lists could be crowdsourced and/or delegated to dynamic lists downloaded from a server (like uBlock Origin). The “I don’t care about cookies” extension is a good example: https://addons.mozilla.org/en-US/firefox/addon/i-dont-care-about-cookies/ https://addons.mozilla.org/en-US/firefox/addon/i-dont-care-a... . The extension even has UI for users to report websites whose cookie popup are not known by the extension. The first step might be creating a shared JS library for generic remote list management (periodically checking for updates, downloading lists, managing local list versioning) that extension developers can use in their extensions.