|
|
|
|
|
by Rygian
1513 days ago
|
|
> The browser is the one who stores and sends cookies. The website is the one who decides which cookies to send in the first place. The browser never invents a cookie out of thin air. > you can just reject all by default until the user explicitly request them to be stored Which cookies should the user "request to be stored" and which cookies can the user safely ignore? How does the user tell them apart? Why should the user have to bother? > If cookies had a cost and would degrade the user experience Cookies are already degrading my user experience; you may have noticed the cookie consent popups on many sites. Those popups exist because cookies were being abused (ie. non-consensually) for purposes that are not essential to the functioning of the website. Such uses are now banned in the EU. > And browser manufacturers gave them [marketing companies] a lot of tools Browser manufacturers did not build those tools for the sake of marketing companies. |
|
I can't fault websites for making use of functions the browser offers them.
> Which cookies should the user "request to be stored"
Have a simple toggle button for "Save state for this website" and discard everything when that button isn't pressed. Most website I visit I don't care about and have no need to keep any state. The few that I need to log into, I can just press that button. Knit that together with the "Save Passwords" function and it might be pretty much automatic most of the time.
> Those popups exist because cookies were being abused
Those popups exist because browsers failed to do their job. If the users wants warning for cookies, that's something the browsers can do just fine by itself, yet few do (e.g. Lynx).
> Browser manufacturers did not build those tools for the sake of marketing companies.
I'd disagree on that. Google makes their money with ads, so of course they'll optimize both Chrome and Search for maximum ad friendliness. Meanwhile Firefox is also run on Google ad money, so they can't step to far out of line either. There aren't many browsers that are build for the user first. The "you are the product" quote applies to browsers just as much as it does to Facebook.