Live data from Hacker News

Firefox 72.0

mozilla.org

331–340 of 543 posts

Re: Firefox 72.0

#331
post #314

Earlier quoted context omitted.

The "I don't care about cookies" addon[0] seems to do a pretty good job of it, I've not seen a banner in ages. I assume it works on a mixture of detecting popular cookie popup js libraries, and user feedback for the rest (although I can't seem to find a github or any code for it so it's hard to say). I think ublock also has a filter list for it built-in. 0: https://www.i-dont-care-about-cookies.eu/

I don't know if I'm paranoid but on the Mozilla add-on page, it says the code is licensed under GPLv3. So the source code MUST be available somewhere. Seems very odd.

I can't find the source repo either (source must be made available, can be on-demand to the author, hell the author could send it to you on CD-ROMs if they felt like it and still be compliant).

That said, it makes an ABP-compatible filter list available. This works with ublock origin:

https://www.i-dont-care-about-cookies.eu/abp/

Re: Firefox 72.0

#333
Haven't been paying attention or keeping up and noticed the version number is 72. One thought is "Wow - that's a lot" and another is "That doesn't sound like semantic versioning."

Re: Firefox 72.0

#334
post #325

Earlier quoted context omitted.

I don't remember the website, but I ran across one on hacker news a while ago that had the best cookie popover I've ever seen. It floated over from the left hand side of the page. Had simple and clean UX allowing for user configuration of cookies. Felt a little more like a cookie control panel than a popup disclaimer. Allowed the user to select which cookies to allow with a small description of what they did. Wish I…

Sounds like something users want. Unfortunately, that’s not what most website owners want. They want to be as annoying as possible so that you smash “agree” just to get it over with.

What users want? GDPR allows you explicitly to serve strictly necessary cookies without asking for consent. You only have to ask if you track people or don’t know what cookies your site stores with your users.

It is 2020 and totally possible to create websites without cookies or with only functionally needed cookies. You do your users a favour and your site will look better.

The very idea of the GDPR wasn’t to force websites to display cookie banners. It was to clarify that cookies can contain identifyable personal data and can be used for tracking, which is why we should avoid using them in that way or ask for consent if it really must be used.

Re: Firefox 72.0

#335
Are they doing anything about floating videos? It's annoying on desktop, but on mobile it's so bad I just don't bother. Typically it's "news" sites that use it.

Re: Firefox 72.0

#336

Still no pinch to zoom. No chance on macOS.

A workaround if you really want that might be to set a bettertouchtool hotkey mapping pinch to CMD+/- when in the Firefox app.

I actually mean double tap zoom that zooms to HTML element that your cursor on. Amazing feature for browsing experience. Chromium has this feature since a lot.

Re: Firefox 72.0

#337
post #325

Earlier quoted context omitted.

I don't remember the website, but I ran across one on hacker news a while ago that had the best cookie popover I've ever seen. It floated over from the left hand side of the page. Had simple and clean UX allowing for user configuration of cookies. Felt a little more like a cookie control panel than a popup disclaimer. Allowed the user to select which cookies to allow with a small description of what they did. Wish I…

Sounds like something users want. Unfortunately, that’s not what most website owners want. They want to be as annoying as possible so that you smash “agree” just to get it over with.

As a user, I want websites to just send cookie headers without asking. I'll decide if I want to store them and send them back.

Re: Firefox 72.0

#338
post #303

With notification spam fixed, how about tackling cookie banners spam next? Let's work on a standard to allow user to set their preferred cookie settings level once in browser UI and keep websites clean.

Unfortunately, they are required by law (at least in Europe) and we can't do much about it. You can't say use a browser API to set a global setting for them, because GDPR explicitly requires that every website must get the user consent for them. Of course the real solution (and the reason why GDPR introduced the banner) is for website to stop using cookies for tracking their users and thus have no reason to put the b…

Important point: GDPR allows you to use strictly necessary cookies without asking for consent.

So if you hate to put cookie banners onto a site, just stick with storing only strictly necessary cookies without data that identifies your users and you are fine.

The problem is, many people don’t even know what cookies their own site stores with their users and they store a ton of tracking cookies on their user’s devices.

Re: Firefox 72.0

#339
post #338

Earlier quoted context omitted.

Unfortunately, they are required by law (at least in Europe) and we can't do much about it. You can't say use a browser API to set a global setting for them, because GDPR explicitly requires that every website must get the user consent for them. Of course the real solution (and the reason why GDPR introduced the banner) is for website to stop using cookies for tracking their users and thus have no reason to put the b…

Important point: GDPR allows you to use strictly necessary cookies without asking for consent. So if you hate to put cookie banners onto a site, just stick with storing only strictly necessary cookies without data that identifies your users and you are fine. The problem is, many people don’t even know what cookies their own site stores with their users and they store a ton of tracking cookies on their user’s devices.

Isn't the whole point of cookies to identify users (for session persistence and the like, not just ads)? If you're not identifying users what are you achieving?

Re: Firefox 72.0

#340

Haven't been paying attention or keeping up and noticed the version number is 72. One thought is "Wow - that's a lot" and another is "That doesn't sound like semantic versioning."

Semantic versioning doesn't make sense for user facing software. Maintaining API compatibility on the software -> user interface isn't really a problem/doesn't make sense compared to software -> software interfaces.
Post reply on HN