3 ms·

Why only block third party cookies? Block all cookies by default. If the user needs a cookie she can enable them. For example, on a per-site basis. Default

Why only block third party cookies? Block all cookies by default. If the user needs a cookie she can enable them. For example, on a per-site basis. Default setting is cookies on for all sites.

thayne 6y ago
Because that would be a terrible experience for consumers. Do you really want to have to explicitly allow cookies for every site you log in to? Or whenever you want to use a shopping-cart? Do you want every site you ever go to to have a huge popup instructing you on how to enable cookies for the site? Not to mention how difficult this will make life for developers who use cookies for legitimate purposes.
- harry8 6y ago
  > Do you really want to have to explicitly allow cookies for every site you log in to? Yes! Absolutely. Click login/cart, popup "do you want to enable login/cart for $this_site?" yes/no But only when you explicitly make the request to use a cart or press the login button. Silently block everything else. There's about 5 sites I would ever use with cookies. And I use chrome for them. I use firefox with all that crap disabled for everything else. Give it a try!
  - thayne 6y ago
    > Click login/cart, popup "do you want to enable login/cart for $this_site?" yes/no I don't see how you could implement that without sites abusing any click event to try and get you to enable cookies. > There's about 5 sites I would ever use with cookies Good for you. Most people need more than that.
    - harry8 6y ago
      What as many as 10? 15? Or even 50! Now count your cookies. Orders of magnitude different. Thanks Google! Nobody agreed to that. Literally nobody.
      - pwdisswordfish2 6y ago
        When you cut to the chase like this it often triggers a canned defensive response such as, 1. "You agreed to it by using the software/website" 2. the design decision was made in the interests of improving "user experience" (meanwhile the users are a cultivated "product", not customers), or 3. the software/website has been "chosen" by large numbers of users which shows they all approve of the design (meanwhile, those users have no other meaningful choice)
  - eythian 6y ago
    I used to use konqueror years and years ago set to ask me about cookies from all sites. It got so tedious. These days I'm much happier with firefox/privacy badger selectively blocking stuff behind the scenes for me. Though I do wish it weren't necessary.
- deleted 6y ago
  [deleted]
- efreak 6y ago
  I do this a regular basis. Not quite daily--Firefox had extensions that manage it for me--but every time I use a text-mode browser (lynx, links, etc) it prompts me when a website wants to store a cookie. The answer is almost always no. > Not to mention how difficult this will make life for developers who use cookies for legitimate purposes. I'm not worried about this. Developers using them for legitimate purposes I agree with can keep using them. If I don't want your cookie, I don't care how hard it makes it for you. I don't want you storing a consent cookie when I say no (ask when you need to get data, not when the page loads). I don't want you storing a cookie saying when I last visited your page anymore than I want Walmart to know when I walk past their doors (reading a single page on your site does not make me a user. Including me in a general count of unregistered views is fine--assigning me a unique ID is not). If I log into a website or use a shopping cart, I am explicitly asking the website to store information for me. This is like walking up to the register (to ask a question, to pay, etc. They need to recognize me as a unique individual). Loading the homepage, loading a product listing? Absolutely not; this is like looking at a vending machine on my way by; you don't need to know anything other than (possibly) the fact that someone walked by (measure foot traffic) and did/did not buy anything (subtract number of purchases from number of visitors).

Why only block third party cookies? Block all cookies by default. If the user needs a cookie she can enable them. For example, on a per-site basis. Default setting is cookies on for all sites.

thayne 6y ago

Because that would be a terrible experience for consumers. Do you really want to have to explicitly allow cookies for every site you log in to? Or whenever you want to use a shopping-cart? Do you want every site you ever go to to have a huge popup instructing you on how to enable cookies for the site? Not to mention how difficult this will make life for developers who use cookies for legitimate purposes.

harry8 6y ago
> Do you really want to have to explicitly allow cookies for every site you log in to? Yes! Absolutely. Click login/cart, popup "do you want to enable login/cart for $this_site?" yes/no But only when you explicitly make the request to use a cart or press the login button. Silently block everything else. There's about 5 sites I would ever use with cookies. And I use chrome for them. I use firefox with all that crap disabled for everything else. Give it a try!
- thayne 6y ago
  > Click login/cart, popup "do you want to enable login/cart for $this_site?" yes/no I don't see how you could implement that without sites abusing any click event to try and get you to enable cookies. > There's about 5 sites I would ever use with cookies Good for you. Most people need more than that.
  - harry8 6y ago
    What as many as 10? 15? Or even 50! Now count your cookies. Orders of magnitude different. Thanks Google! Nobody agreed to that. Literally nobody.
    - pwdisswordfish2 6y ago
      When you cut to the chase like this it often triggers a canned defensive response such as, 1. "You agreed to it by using the software/website" 2. the design decision was made in the interests of improving "user experience" (meanwhile the users are a cultivated "product", not customers), or 3. the software/website has been "chosen" by large numbers of users which shows they all approve of the design (meanwhile, those users have no other meaningful choice)
- eythian 6y ago
  I used to use konqueror years and years ago set to ask me about cookies from all sites. It got so tedious. These days I'm much happier with firefox/privacy badger selectively blocking stuff behind the scenes for me. Though I do wish it weren't necessary.
deleted 6y ago
[deleted]
efreak 6y ago
I do this a regular basis. Not quite daily--Firefox had extensions that manage it for me--but every time I use a text-mode browser (lynx, links, etc) it prompts me when a website wants to store a cookie. The answer is almost always no. > Not to mention how difficult this will make life for developers who use cookies for legitimate purposes. I'm not worried about this. Developers using them for legitimate purposes I agree with can keep using them. If I don't want your cookie, I don't care how hard it makes it for you. I don't want you storing a consent cookie when I say no (ask when you need to get data, not when the page loads). I don't want you storing a cookie saying when I last visited your page anymore than I want Walmart to know when I walk past their doors (reading a single page on your site does not make me a user. Including me in a general count of unregistered views is fine--assigning me a unique ID is not). If I log into a website or use a shopping cart, I am explicitly asking the website to store information for me. This is like walking up to the register (to ask a question, to pay, etc. They need to recognize me as a unique individual). Loading the homepage, loading a product listing? Absolutely not; this is like looking at a vending machine on my way by; you don't need to know anything other than (possibly) the fact that someone walked by (measure foot traffic) and did/did not buy anything (subtract number of purchases from number of visitors).