Live data from Hacker News

Things not available when someone blocks all cookies

blog.tomayac.com

131–140 of 231 posts

Re: Things not available when someone blocks all cookies

#131

Earlier quoted context omitted.

I’m in adtech and we manage to do ads in a completely user respecting way within the retail space. We monetize on search traffic without user data, cookies, local storage. The only browser feature we leverage are click events and img tags. Though I appreciate your frustration, your aggression is a little off target. :)

> The only browser feature we leverage are click events Do the users want their click events fed into an advertising engine? Did you ask them? If you made this opt-in, how many would say, yes, please track my clicks in order to advertise to me? Even if its anonymized/aggregated. A huge amount of advertising is enabled by tracking users against their will, exploiting the fact that many users aren't aware of what's goi…

I should have known my comment would only make you more aggressive. Walked into that I guess.

You are right in that a huge amount of ads leverage user data at the expense of the user.

The point I’m trying to make is that not all involved in the advertising technology are exploitive. We do zero ad targeting based on user data. You make a search for specific products, we take the response and shuffle the order a bit based on vendor campaigns. That’s it. Nothing is associated or even collected from the user. It’s all system metrics.

The greatest harm that my team does is hurting optimized relevancy, which is inherit to advertising but also something we work hard to alleviate.

That misused proverbs quote is a nice touch. Shows a lot of self awareness.

Re: Things not available when someone blocks all cookies

#132
post #36

Earlier quoted context omitted.

I totally understand your point and I think I agree, except—well, the setting says “disable cookies”. It should do what it says. If the goal is to disable all persistent information, the setting should be called “disable persistent storage”. Of course, I also know why it’s not called that: a lot of people know what cookies are at this point, at least relative to the number who'd understand “persistent storage”. A tog…

“Cookies” is shorthand for “persistent storage” because nobody outside of web developers knows other methods exist. When people, laws, banners, etc. refer to cookies, they mean “any technology that stores information on the client side systems”. Whatever mechanism is used is irrelevant to the meaning/concept.

> “Cookies” is shorthand for “persistent storage”

"Cache" is also “persistent storage” to me.

Re: Things not available when someone blocks all cookies

#133
post #129

Earlier quoted context omitted.

Came here to say this. If anything, a cookie that is not cross-domain is more innocent than localStorage.

What would make it "more innocent"?

Perhaps the comment was about HttpOnly which cannot be read by random ad / tracking scripts on the page. It is still storing data, but now the server needs to actively transmit it to other parties.

Re: Things not available when someone blocks all cookies

#134
post #73

Earlier quoted context omitted.

In what way is it more complex than it has to be? I don't work in front-end but whenever I've used localstorage for personal projects it's as simple as getting/setting a javascript object with keys & values.

It’s described in the first section of the article.

Care to elaborate? I just re-read the article and honestly still don't know what complexity OP was referring to.

Do you mean the fact that cookies and LocalStorage (or other APIs able to persist data) are often considered the same thing when using the term "cookies"?

Re: Things not available when someone blocks all cookies

#135
post #92

Earlier quoted context omitted.

Same, I absolutely love this extension. You can whitelist the websites you use frequently, and for everything else it's like a groundhog day every day. The cookie banners can be super annoying sometimes, but they are easily removed with uBlock Origin. I also frequently have to solve captchas, but it's not so bad. For example, every time I visit amazon.com to order toilet paper or whatever, it thinks I'm a bot, but at…

If you go to Amazon a lot why not whitelist?

One of the last companies I'd whitelist.

Re: Things not available when someone blocks all cookies

#136

Earlier quoted context omitted.

You can store the state in the URL, can you not? That used to be done anyhow.

I have written a web app that does this so you can share links which have the same state. You can't have that long of URLs actually - especially for some browsers. Having to base64 encode most/all of it so you can safely use any kind of data makes it even worse. My use case was very basic and I quickly hit limits that made it so I couldn't "persist" all of the data I wanted.

Er, you'd store the data in your DB of course and only a comparatively small, encrypted index to it in the URL. You wouldn't trust the client to "persist" the data anyhow.

Re: Things not available when someone blocks all cookies

#139
post #129

Earlier quoted context omitted.

Came here to say this. If anything, a cookie that is not cross-domain is more innocent than localStorage.

What would make it "more innocent"?

A cookie is a tiny plaintext file limited at 4kb. Your browser keeps an inventory of them, lets you read or delete them, and automatically clears them out regularly.

Local storage can contain just about any type of user data without letting users know, and theoretically forever.

If you have to store local data, and you cared about "innocence" (author's word), it seems to me a cookie set to the local domain leaves less room for shenanigans. Hence why Google probably disables it when you disable cookies as well.

Re: Things not available when someone blocks all cookies

#140
post #17

> All I am using is some innocent localStorage and IndexedDB to persist user settings like the values of the sliders or the chosen color scheme. When you turn off cookies you're telling the browser not to let sites persist information. Otherwise, whatever goals you had in disabling cookies would just be worked around through these other technologies.

I disagree. For example, a simple todo-list web-app doesn't need any cookies but stores everything in localStorage. Cookies are made for a server, localStorage for a client.
Post reply on HN