3 ms·
Don't blame the regulation, blame everyone who is trying to get you to click the consent button. Cookies are a simple yes/no question, with the default answer
by nicbou 7y ago
Don't blame the regulation, blame everyone who is trying to get you to click the consent button.
Cookies are a simple yes/no question, with the default answer being no. If everyone did what's in the users' best interests, it would be a non-issue.
- djohnston 7y agoyou need session tokens to do useful things on WWW. why is the default no? i want my default to be yes.
- chacha2 7y agoGDPR only needs a cookie warning if it's used for tracking.
- notechback 7y agoTechnical cookies don't need consent.
- zpeti 7y agoSo how do you store user information then? Like logins? Sessions? Also rely on cookies. Browser fingerprinting? Great - then you've switched one problem for another. This entire EU regulation is a non solution to a not really existing problem. Yes, third party advertisers use cookies to track you. But they can build technologies to use something else. In the meantime you are a) breaking the internet b) wasting hours of each EU citizens time every year.
- deleted 7y ago[deleted]
- Cthulhu_ 7y agoThose are functional cookies, which can be placed without asking for consent. A site that just removes tracking and advertising does not need a cookie consent warning. They do not ask "can I place cookies"; they ask "Can my third-party trackers and advertisers place markers on your system so that your activity can be tracked across this and other websites". Don't stare yourself blind on the poorly chosen wording. It's not the "cookie law" either, it's the General Data Protection Regulation. It's not about cookies, it's about regaining control over your personal data, your online behaviour, etc.
- stan_rogers 7y agoThose are all allowed without explicit consent - it's right in the regulation. What isn't allowed without consent is all of the tracking and data-sharing nonsense that isn't actually required for the website to function.
- zpeti 7y agoTheoretically. Practically almost all websites need third party cookies to use any decent analytics platform (most often GA). So the end result is still that 100% of websites need cookie consent.
- clarry 7y agoYou don't need an analytics platform for a login. You also don't need to fingerprint my browser.
- XCSme 7y agoThere are also self-hosted alternatives so no third-party, or even cookie-less tracking. Something like: https://usertrack.net/ https://usertrack.net/
- myu701 7y agoMatomo is my user tracking of choice, it honors DNT by default and is self-hostable or can be run as a hosted service. Matomo was formerly known as Piwik
- XCSme 7y agoMatomo is great and it's nice that it's open source. One advantage of userTrack, which is also self-hosted, is that you get heatmaps and session recordings at no extra cost, which on Matomo cost from 200eur/year.
- vertex-four 7y agoJust because you can't be arsed doing the research and want to give your users a poor user experience instead doesn't mean alternatives don't exist.
- BeniBoy 7y agoGet familiar with the regulation before posting. Explicitely allowed: * Cookies for login/session * Cookies for shopping carts * Cookies for interface personnalisation (language, etc.) * Cookies for load balancing * Cookies to retain user choice regarding cookies And quite a few other.
- phiresky 7y agoYou're really misunderstanding the GDPR. Cookies are not mentioned anywhere in the law and it's actually really simple to understand: 1. You can do whatever you need to do to provide the service you're providing. (login cookies, sessions, store their email address, whatever). 2. If you want to process, store, and sell any other user data, you need to ask them first. So for example if you want to send 100 advertising companies personal data about your users, you need to ask for consent and allow them to decline without restricting their access to you service. What technology you use to track users is irrelevant, it can be fingerprinting or cookies or anything else. The only reason why you think the law is bad is because companies are frantically trying to work around it, trying to interpret it in unintended ways to not impact their data tracking ways, and trying to make users hate the law instead of them.
- BeniBoy 7y agoWell, this is a little more complicated, because the cookie issue stems not from the GDPR but from ePrivacy. This directive explicitely targets reading/writing into the user terminal without autorisation, hence the application to cookies. Edit: removed a post, that was not explicative enough. But the articulation is: ePrivacy says you need to consent to write non-essential trackers. GDPR defines how you can obtain the consent. So both laws take part in this ruling.