Live data from Hacker News

Purge site data when site identified via old tracking cookies

bugzilla.mozilla.org

21–30 of 135 posts

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

#21
post #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.

Pi-hole is on my TODO list for quite some time. Yeah, its definitelly a portal I should get to fast (summon, not get to, hence the TODO entry). Currently using uMatrix and friends but its not network wide and that sux a lot.

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

#22

Earlier quoted context omitted.

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.

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

That's true, but if a site is not ad-supported, and "paywall" is almost an epithet (and circumvented to boot), how is any site supposed to remain viable?

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

#23

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.

Hear me out - we could all start using Gopher?

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

#25

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.

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

Not really. It doesn't delete indexeddb for instance.

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

#26

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.

If "reasonably formatted" means CSS comes along for the ride, prepare for tracking pixels behind onhover rules, and on and on we go...

Why would that matter? If the browser fetches images hidden behind onhover, then presumably it would also fetch plain tags, so why not use those. If it doesn't fetch onhover images (which admittedly might break the "reasonably formatted" bit), then tracking pixels are useless because, well, it doesn't fetch them.

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

#27
post #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.

For Facebook, turn off JS and then go to m.facebook.com.

It is quite usable, and I probably wouldn't use FB without it.

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

#28

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 wouldn't mind going back to a JavaScript-less web experience.

My default policy is to not allow JS to run, so my experience is already mostly Javascriptless. And, I have to say, my user experience on most web sites is actually better when I don't allow Javascript to execute.

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

#29
post #19

Earlier quoted context omitted.

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.

There's nothing wrong with non-interactive html web pages just like there's nothing wrong with JS rich web applications. The web is big enough for everyone.

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

#30
post #28

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 wouldn't mind going back to a JavaScript-less web experience. My default policy is to not allow JS to run, so my experience is already mostly Javascriptless. And, I have to say, my user experience on most web sites is actually better when I don't allow Javascript to execute.

I run a similar sort of policy but I would say the number of sites I visit that display nothing but a blank page without javascript is more than half.

Sites that function without it are the exception, not the rule.

Post reply on HN