Cookies are for bellies, not for browsers
-
2019 is coming to an end and weβre baking some delicious cookies for the holidays. Can you help us tell a few folk at Google, Facebook and elsewhere that cookies are for bellies, not for browsers?
Click here to see the full blog post
-
@gwen-dragon: Ahah I agree with you
-
While I applaud the initiative, I think big companies have stopped caring a long, long time ago. They've somehow managed to convince themselves that their use of tracking cookies is for the benefit of users - to serve them "personalised content" and "enhance the experience". And they really do believe their own BS.
I got the following banner on a site recently:
"This website uses cookies and EU law requires us to tell you that. If you don't like cookies: don't visit this website. If you don't like this banner: don't vote for politicians who make stupid laws like this."
... This from a site who serves cookies from about a dozen third-party domains. And the EU law is there to protect people from companies like this. Not going back there for sure.By the way you guys are serving cookies from Typeform as well - but I'll let it slide this time since I assume it's just your CMS
-
I have changed my user agent to: Cookie Monster
a few times -
@Chas4 Oh! How many sites could you access with no problems?
-
Indeed, in Vivaldi, I still found cookies under chrome://settings/siteData that can be used for websites autologin (and maybe tracking) though I've set the browser to delete cookies on exit.
I know that Vivaldi has a double layer "nature" because of its chromium origin , but I still have to deleted manually those underground cookies every couple of days.
It's rather annoying.
-
Dear Vivaldi,
below is a step by step guide for preventing tracking by cookies- Click on Vivaldi button > Tools > Settings
- Click on Privacy on the left side
- Check Block Third-Party Cookies
P.S. Making it the default would protect a lot more users!
Cheers,
Madis O -
@madiso Unfortunately, this would also hinder the functionality of some websites, such as those with cross-domain logins (Vivaldi's own website being one) or using external commenting platforms. I agree with the sentiment, but until Vivaldi is better established, it would seem to me the default settings should cater towards keeping the majority of websites functional out of the box.
-
@Crimsonshade It could also be determined by heuristics (e.g. domain visited before?) or by a blacklist, similar to Firefox.
-
@snertev said in Cookies are for bellies, not for browsers:
I still found cookies under chrome://settings/siteData
Yes site data refers to Cookies but also Service Workers, Local, Database, File system types of storage. Unfortunately there is very little control of these types of storage. And more and more sites use them to store data and also for tracking. I hope some day we will have a way to block sites saving any kind of data unless we explicitly allow it.
We already can whitelist domains in
chrome://settings/content/cookies/
and then block all cookies+storage from any other domains. But it's not part of the Vivaldi UI and not easily accessible to most. -
@Pathduck said in Cookies are for bellies, not for browsers:
I hope some day we will have a way to block sites saving any kind of data unless we explicitly allow it.
I would also like to see this, but I fear that at that moment they'll store all the data on their servers (and will have perfect system to identify this or that PC).
-
@potmeklecbohdan A lot of them as Cookie Monster UA string is not likely one that would not likely be in one of the lists (tho the web dev or who is looking at the logs might laugh). Cookies have been used on the web for over 30 years tho how they are used now is a bit different than they were then.
-
Here's an important relevant blog post I forgot to share previously:
https://blog.chromium.org/2019/10/developers-get-ready-for-new.htmlTL;DR: cookies will get more secure in the next (!) version of Chromium, releasing in February.
-
<3, wish I had seen this earlier
-