Live data from Hacker News

Purge site data when site identified via old tracking cookies

bugzilla.mozilla.org

11–20 of 135 posts

Re: Purge site data when site identified via old tracking cookies

#11
I have been using “Cookies Autodelete” for years. Except for a short list of 20 sites, nothing can store data on my Firefox.

These tracking sites would not be able to show me ads anyway because I have “uBlock origin”

And finally “I don’t care about cookies” to automatically dismiss these stupid GDPR “we’re going to use cookies” prompts.

Without these the Internet feels broken.

Re: Purge site data when site identified via old tracking cookies

#12
post #5

I wouldn't mind going back to a JavaScript-less web experience. I know not all tracking is based on JS, but the browser provides so many heuristics this way: screen size, cursor location, installed plugins. Give me reasonably formatted HTML, and something a little bit more powerful than curl.

Nothing stopping you from doing this on your next / current project. I've been 100% committed on getting the web back to as lightweight as possible for the last couple years worth of development.

Almost all front-end development jobs are looking for React or Vue skills.

Re: Purge site data when site identified via old tracking cookies

#13

I wouldn't mind going back to a JavaScript-less web experience. I know not all tracking is based on JS, but the browser provides so many heuristics this way: screen size, cursor location, installed plugins. Give me reasonably formatted HTML, and something a little bit more powerful than curl.

I wish there was simply a way where ad-supported sites I visit could collect their revenue without having me submit to advertiser surveillance. I don't mind seeing ads. I hate being tracked.

I think the issue is verification that an ad has actually been shown to a human. Even print and TV advertisers can have companies do audits to verify ads get run as expected.

Thing is, nobody ever said ad supported sites have to be viable.

Re: Purge site data when site identified via old tracking cookies

#14
The relevant code comment from the bug-linked changes is:

> This loops through all cookies saved in the database and checks if they are a tracking cookie, if it is it checks that they have an interaction permission which is still valid. If the Permission is not valid we delete all data associated with the site that owns that cookie.

Re: Purge site data when site identified via old tracking cookies

#15

I wouldn't mind going back to a JavaScript-less web experience. I know not all tracking is based on JS, but the browser provides so many heuristics this way: screen size, cursor location, installed plugins. Give me reasonably formatted HTML, and something a little bit more powerful than curl.

Perhaps create a new and separate Web, that's designed from the ground up to take into account the lessons of the past 25 years, and provide a more mellow experience?

It would be an eternal niche, but it might be a nice, cozy little niche.

Re: Purge site data when site identified via old tracking cookies

#16
post #9
post #6

Earlier quoted context omitted.

uMatrix basically does that for you now.

Blocking trackers helps a lot for performance, and I second uMatrix. I even showed my 13 year old kid how to use it. However, uMatrix on mobile is not particularly easy to use (I use it, but would not recommend it).

I didn't even realise it worked on mobile, I use uBlock on Android but uMatrix otherwise (actually I think both, maybe because of synchronisation).

The zapper's fairly easy to use to get rid of annoyances on mobile, until you make a mistake. Editing the rules file isn't the nicest UX even on desktop FF. (It'd be good, for example, to be able to preview what's being blocked, and selectively re-allow them.)

For an example of how it can go wrong: you block 'overlay', then it reveals and you block 'grey-blur-modal-focus', allowing you to click whatever you wanted, except it turns out that it uses 'overlay' and you shouldn't have blocked that one.

Re: Purge site data when site identified via old tracking cookies

#18

And in v80 in alternate universe, Firefox will purge the sites from the Internet, after the data. Somebody please point me to the portal...

That's called pi-hole and having it network wide is a game changer. 30% of all dns requests are blocked.

Re: Purge site data when site identified via old tracking cookies

#19
post #5

Earlier quoted context omitted.

Nothing stopping you from doing this on your next / current project. I've been 100% committed on getting the web back to as lightweight as possible for the last couple years worth of development.

Almost all front-end development jobs are looking for React or Vue skills.

An argument for non-interactive semantic html is an argument against the front-end/back-end dichotomy. That is to say your application should directly generate the page you want the user to see and you shouldn’t need to spend all your time designing custom JavaScript for it.

Re: Purge site data when site identified via old tracking cookies

#20

I wouldn't mind going back to a JavaScript-less web experience. I know not all tracking is based on JS, but the browser provides so many heuristics this way: screen size, cursor location, installed plugins. Give me reasonably formatted HTML, and something a little bit more powerful than curl.

Completely agree. I default to JS-disabled, and will sometimes enable it. More often, though I just move on. Of course if you want to use FB or other surveillance sites, this won't work well for you.

What methods are there to exert more control over the JS engine in Firefox? Screw performance, I'd have a lot of fun writing my own hooks/wrappers to overload certain method calls.

Post reply on HN