4 ms·
Well, the cookie popups are only there because of regulation. You are right about all the rest.
by eru 4y ago
Well, the cookie popups are only there because of regulation.
You are right about all the rest.
- ajdude 4y ago> Well, the cookie popups are only there because of regulation. You don't /need/ them if you only have essential cookies: > At GitHub, we want to protect developer privacy, and we find cookie banners quite irritating, so we decided to look for a solution. After a brief search, we found one: just don’t use any non-essential cookies. Pretty simple, really. https://github.blog/2020-12-17-no-cookie-for-you/ https://github.blog/2020-12-17-no-cookie-for-you/
- hk__2 4y ago> Well, the cookie popups are only there because of regulation. "only"? No, they are here because you use non-essential cookies AND regulation says you must ask visitors about them.
- midasuni 4y agoPlease don’t spread the ad company’s lies. There is no need for pop ups under the gdpr. If you are handling personal information, giving cookies etc which aren’t required (E.g to sign in), then ask at the point of signing in/up. Otherwise you don’t need to set cookies, you might want to, to track and monetise your visitors, but that’s different.
- IX-103 4y agoHow are you supposed to provide a consistent appearance for A/B testing changes without being able to store which group a user is assigned to? How are you supposed to count unique users that visit your site? How are you supposed to figure out why most users bounce? These are legitimate questions a publisher may want to know to improve their site, but are not allowed under GDPR without a specific notice and opt-out. There are many cases where what publications consider "essential" for their business do not match what the EU has decided is "essential". Heck, when GDPR was first proposed most publishers assumed advertising would be allowed under "essential" business uses since they can't provide content if they don't get paid. Clarification on this only came a couple of months before GDPR enforcement started, causing a bit of a scramble for publishers and advertisers.
- hk__2 4y ago> How are you supposed to provide a consistent appearance for A/B testing changes without being able to store which group a user is assigned to? Those are legitimate cookies for which you don’t need to ask an authorization. > How are you supposed to count unique users that visit your site? https://plausible.io/blog/google-analytics-cookies#how-can-plausible-analytics-count-unique-visitors-without-cookies https://plausible.io/blog/google-analytics-cookies#how-can-p... > These are legitimate questions a publisher may want to know to improve their site, but are not allowed under GDPR without a specific notice and opt-out. Why would the publisher’s questions be legitimate and the user’s right not to be tracked no? You can still answer those questions but you need to ask for permission. A physical store owner has also a lot of questions but they’re not allowed to follow you everywhere in the store and in the street. > Heck, when GDPR was first proposed most publishers assumed advertising would be allowed under "essential" business uses since they can't provide content if they don't get paid. That’s a really weird reasoning. Should drug dealers be exempted from police controls because their activity is essential for their income and so for their life? Earning money is necessary, but there are multiple ways to do so.
- matheusmoreira 4y ago> How are you supposed to provide a consistent appearance for A/B testing changes without being able to store which group a user is assigned to? You're not supposed to A/B test at all. Users are not test subjects. > How are you supposed to count unique users that visit your site? How are you supposed to figure out why most users bounce? You're not supposed to. You simply aren't entitled to any of that information. > These are legitimate questions a publisher may want to know to improve their site It doesn't matter how "legitimate" it is or how much money it costs publishers. The attempt to learn these facts requires collecting identifying information and that is harmful to us. The least you can do is ask permission. > There are many cases where what publications consider "essential" for their business do not match what the EU has decided is "essential". That's by design. Nobody really cares what an industry that's being regulated thinks. Obviously adtech considers it "essential" to collect as much personal data as humanly possible. What matters is what society thinks and we think sites work just fine with all the tracking disabled. > publishers assumed advertising would be allowed under "essential" business uses Advertising is allowed. It's just the abusive adtech model of targeted advertising that requires consent. Nothing stops people from signing a deal with some brand and serving static images or something. As long as it's not surveillance capitalism it's fine.
- denton-scratch 4y agoExcuse me? What regulation requires cookie popups?
- jand 4y agohttps://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32009L0136 https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A... EU Directive 2009/136/EC
- denton-scratch 4y agoThat is not a "regulation", it is a directive, requiring member states of the EU to implement appropriate legislation. It applies to the legislatures of member states, which I believe doesn't yet include the USA. Perhaps the clause you are thinking of is this one: "(33) Customers should be informed of their rights with respect to the use of their personal information in subscriber directories and in particular of the purpose or purposes of such directories, as well as their right, free of charge, not to be included in a public subscriber directory, as provided for in Directive 2002/58/EC" That directive doesn't call for a mist of popups to flash before your eyes before you can read content. It could easily be satisfied by a menu option that allows you to set your preferences. The mist of popups is caused by a bunch of angry data traders who don't care how much they annoy their users. Incidentally, citing a directive from 2009 is a bit anachronistic: that directive is overridden by the GDPR.