Earlier quoted context omitted.
The cookie banner is only there because the website in question uses non-functional cookies (e.g. targeted advertising)
It's gotten entirely out of hand. Most EU national government websites have cookie banners. Even the European Commission website has a cookie banner! This should have been implemented at the browser level. Let the browser generate a nice consistent UI to nag EU users when visiting websites about accepting cookies and let the rest of us opt out.
RFC 35140: HTTP Do-Not-Stab (2023)
101–110 of 219 posts
Re: RFC 35140: HTTP Do-Not-Stab (2023)
#102> because every company out there fucking hates you They don't actually hate you. Rather, they love your money and they have a depraved indifference for you.
Re: RFC 35140: HTTP Do-Not-Stab (2023)
#103Earlier quoted context omitted.
No, they love the money they can make about you. I don’t know anybody giving their money to these people. It is other shady companies buying the data about for, shady companies that have collected. All of this is offered to you free of charge.
Mind you, some companies will take your money and still track the shit out of you, show you ads, and sell your data to the highest bidder.
Do they provide a guaratee to only sell once, instead of selling to everyone?
Re: RFC 35140: HTTP Do-Not-Stab (2023)
#104It’s great satire, but it really does mirror a larger societal shift where the burden of safeguarding personal autonomy has shifted from institutions/regulators to individual users. Do-Not-Stab, Do-Not-Track, whatever it might be, any sort of “voluntary compliance” is a non-starter in the face of financial pressures IMO we need to start normalizing being militant about this stuff again, to aggressively and adversaria…
I wonder if there is some way to DoS the tracking services by basically accepting third party cookies but then immediately discarding them so every page load generates a new cookie and presumably state stored on the other end to match it. Or are these tracking cookies typically self-contained so that no state is stored server-side?
Re: RFC 35140: HTTP Do-Not-Stab (2023)
#105Re: RFC 35140: HTTP Do-Not-Stab (2023)
#106Earlier quoted context omitted.
I wonder if there is some way to DoS the tracking services by basically accepting third party cookies but then immediately discarding them so every page load generates a new cookie and presumably state stored on the other end to match it. Or are these tracking cookies typically self-contained so that no state is stored server-side?
Isn't that the reason cookies were invented in the first place? To keep servers stateless?
Re: RFC 35140: HTTP Do-Not-Stab (2023)
#107Earlier quoted context omitted.
The cookie banner is only there because the website in question uses non-functional cookies (e.g. targeted advertising)
The cookie banner is there to punish people who have cookies turned off or set to be deleted upon browser/tab close - and generally annoy everyone else. Think about how obsessive companies are about "UX" and how disruptive the banner is. Bitch-slapping people for fighting against tracking is more important to them than the user being able to access or use the site at all.
Re: RFC 35140: HTTP Do-Not-Stab (2023)
#108This is such transparent EU Bureaucracy shilling. No wonder Europe doesn't have any large SaaS companies with their stabbing unfriendly business climate.
I think you are factually wrong: Skype, Spotify, Revolut, Zendesk, Transferwise... There are quite many European unicorns too (less though than US and Chinese companies) which are operating as SaaS. Some of them got acquired or re-based to other countries though
Re: RFC 35140: HTTP Do-Not-Stab (2023)
#109Earlier quoted context omitted.
The cookie banner is only there because the website in question uses non-functional cookies (e.g. targeted advertising)
It's gotten entirely out of hand. Most EU national government websites have cookie banners. Even the European Commission website has a cookie banner! This should have been implemented at the browser level. Let the browser generate a nice consistent UI to nag EU users when visiting websites about accepting cookies and let the rest of us opt out.
I understand it’s was media and communication departments do, and that it’s natural that the people working within them would want to do so regardless of where they work. It’s their trade after all, unfortunately they bring the exact same “user engagement” mindset with them into the public sector. Well, at least in my anecdotal experience with a handful of these departments in 7-8 different cities around here. You can of course make good points on user metrics on a public website, but they should frankly work very different than they would on most web sites. On a public website it should be the goal to get to user to leave the site as quickly as possible, because the longer they hang around the more time they are spending finding what they need. That’s not what happens with these metrics in my experience, however, instead they are used to do what you might do on a news site.
That’s just one side of it, however, because the privacy concerns are their own issue. If you absolutely want metrics on a public website at least have the courtesy to build your own. It should be illegal for public web sites to use 3rd party tracking. I know why they use it, it’s for the same reason they spend a ridiculous amount of money on custom designs systems build on top of what is usually SharePoint or Umbraco. They refuse to hire the Django (insert any other extremely low maintenance system) expertise because it’s expensive on the “long term budget”, even though it would be much cheaper than 3rd party tools and consultants on the actual long term budget. Anyway, that is another point. But it really pisses me off when public websites need you to allow 3rd party tracking because they aren’t using it in any way which serves the public.
Worst of all is that cookie banners are explicitly a private industry way of dealing with their refusal to respect “do-not-stab”. Public websites could simply put their bullshit into their privacy page. Of course nobody would go there and turn on 3rd party cookies, but why should the public care?
Re: RFC 35140: HTTP Do-Not-Stab (2023)
#110The Do Not Track header was originally proposed in 2009 by researchers Christopher Soghoian and Sid Stamm.[2] Mozilla Firefox became the first browser to implement the feature. https://en.wikipedia.org/wiki/Do_Not_Track#:~:text=The%20Do%... .
I wonder how many web developers actually honour Do Not Track. I do, in all the websites I've made for my employer too, but I think I'm only getting away with it because my employer doesn't know. I've even made it so that browsing with Do-Not-Track enabled also skips the cookie consent banner and just assume the user wants no cookies other than the strictly necessary ones (like their session/login cookie), and doesn'…
I can dream...