Live data from Hacker News

Things not available when someone blocks all cookies

blog.tomayac.com

181–190 of 231 posts

Re: Things not available when someone blocks all cookies

#181

Earlier quoted context omitted.

It’s trivial to emulate cookies with other Web APIs (storage + service worker, for one). You’re focusing on the label of the toggle and not user intent. If a website can send information about my visit 2 days ago to an upstream server, clearly my expectation of “Disable cookies” is broken.

Then it should be called disable client persistence or something more clear, imo. Cookies is already a ridiculous jargon word esp for the general public.

Firefox calls it "Cookies and site data".

Seems clear and to the point.

Re: Things not available when someone blocks all cookies

#182
post #100

Earlier quoted context omitted.

If there were a simple to examine and pick through localstorage, maybe. Of course if there were, localstorage would be intentionally obfuscated.

It's relatively straightforward. You open the console, type window.localStorage, and poke around. On the article I see: > window.localStorage Storage {dark-mode-toggle: 'light', cid: '2722...', length: 2} Ignore the "length" (implementation detail) and you can see it's storing whether I've turned on dark mode and some id that's likely per-user. If I switch the page to dark mode I see instead: > window.localStorage St…

You could also just use the Storage tab in the devtools of your browser of choice, Chrome and Firefox at least both provide a GUI for looking at storage. Not sure what all Chrome's shows, but Firefox's shows Cache Storage, Cookies, IndexedDB, LocalStorage, and SessionStorage.

Re: Things not available when someone blocks all cookies

#183

Earlier quoted context omitted.

Or we could just recognize that for the general population, "cookies" are any client storage by a website, and for technical people, cookies are a subset of options for client storage by a website. The public never needs to know the technical distinction because it is both 1) Arbitrary: "cookie" could just as well have been a general term for client storage, and 2) Insignificant: Virtually nothing the public is conce…

> Insignificant: Virtually nothing the public is concerned about hinges on specifically how client data is stored, except for lawyers trying to get around cookie laws or to deceive through the text and UI of cookie consent pop-ups. IMO, your exception is what makes the distinction significant. Defining a cookie two different ways gives companies a powerful new tool for purposefully misleading and manipulating end use…

It's a bit late, these things have been called "supercookies" since Flash started to support persisting data outside the browser's control.

Re: Things not available when someone blocks all cookies

#184

I always use a wrapper around local/session storage[1] to avoid this problem. Then you have your app sync settings with storage, never read from it except during startup. It becomes impossible to implement basic UI features like remembering open panes, etc when storage is disabled though. With the current policies around cookies - no cross-domain reads, Safari's ITP - there is no real need to turn them off for privac…

Basic UI features shouldn't need storage. In-memory or in the URL is enough. If you put it in storage then it is actually a (cookie) session, with some sort of configuration - that's not "basic UI".

If you define "basic" as not including "this remembers how you had it set last time" then, sure.

"In the URL" works for that, sort of, though not if you want it to still work for users that are just re-finding you through Google or typing in your address.

Re: Things not available when someone blocks all cookies

#185
post #77
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'd argue that being able to write to and read from storage for the lifetime of the session (i.e. until you close the tab) is not "persistence" in the sense that any privacy-conscious user cares about. If anything, making these features break loudly enables sites to detect that they can't be used for persistence and allows them to find ways to circumvent that. Contrast this with cookies which are silently discarded i…

> I'd argue that being able to write to and read from storage for the lifetime of the session

The web API doesn’t cater to that. If you only need storage to persist for the session you can just use memory.

Re: Things not available when someone blocks all cookies

#187
post #90
post #87

Earlier quoted context omitted.

That's not true -- many people think advertising as practiced is abusive in its own right.

"Society as a whole" and "many people" are not the same entities. Again, there was a time when serious discourse about internet privacy focused on abuse potential and how to provide data security guarantees. Now it's just "ads bad", and I think that's a real problem with the discourse. To repeat, you can win fights over privacy (c.f. the GDPR, which while pretty flawed was a real and tangible win for users). You'll n…

But "many people" and "no one serious", which is what you claimed, are also not the same.

Re: Things not available when someone blocks all cookies

#188
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.

[deleted]

Re: Things not available when someone blocks all cookies

#190
post #123

Earlier quoted context omitted.

Pair it with "I don't care about cookies". This one clicks Accept on all cookie banners, and Cookie AutoDelete deletes them when the tab is closed. https://addons.mozilla.org/en-GB/firefox/addon/i-dont-care-a...

This is great, thanks P. S. If I'm using a separate Firefox container just for Amazon, they would isolate my Amazon cookie right? So then I could just whitelist it and avoid capchas?

Yes. Each Firefox container has its own cookies.
Post reply on HN