Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Purge site data when site identified via old tracking cookies

bugzilla.mozilla.org

Post reply on HN
Print view View original

31–40 of 135 posts

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

#31

Post by ojame »

a1369209993 wrote: post #26
reificator wrote: post #4

Earlier quoted context omitted.

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.

Because after you hover on something, it can be an indication of intent. Just loading an image when the webpage loads doesn't give you any insight into what the user 'interacted' with.

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

#32

Post by simple_phrases »

swiley wrote: post #19
simple_phrases wrote: post #12

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.

I agree, but no one is hiring down those lines. People are being paid to write JavaScript where it isn't needed per se, but where it will still get the job done.

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

#33

Post by JohnFen »

ghostpepper wrote: post #30
JohnFen wrote: post #28

Earlier quoted context omitted.

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

Well, yes, how well this works depends on what sites you tend to use. The vast majority of the sites I frequent either degrade gracefully in the absence of JS, or never used it in the first place.

I think there are three or four that both require Javascript and that I want to use badly enough to allow JS.

When I encounter a web site that doesn't work without JS, I just move on. But I understand that others may not want to do the same.

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

#34

Post by ohithereyou »

ghostpepper wrote: post #30
JohnFen wrote: post #28

Earlier quoted context omitted.

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

A site that renders completely blank without JavaScript is a site that I don't enable JavaScript for. They don't want me to view it, and nine times out of ten I can find the information elsewhere.

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

#35

Post by Drdrdrq »

gruez wrote: post #25
jackjeff wrote: post #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.

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

And cache, local storage, basically anything that changes state.

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

#36

Post by ohithereyou »

throwsprtsdy wrote: post #22
phkahler wrote: post #13

Earlier quoted context omitted.

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?

Think of the poor buggy whip makers!

Not every desirable activity in life is profitable. If your business plan is "make website -> get money" then perhaps you're in the wrong business.

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

#37

Post by 3xblah »

JMTQp8lwXL wrote: post #3

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 experience."

By not using a graphical, JavaScript-enabled browser, I have been experiencing the web this way for the last 15 years. It works just fine for the purposes I use if for, mainly informational retrieval. For me, there is no such thing as "page load time". This shifts all awareness to "server response time". This is more or less the same from one website to another and therefore differences are not noticeable, unless a server is misconfigured or has some problem.

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

#38

Post by tekstar »

forgotmypw16 wrote: post #27
_jal wrote: post #20

Earlier quoted context omitted.

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.

And if you want messages access just use mbasic.facebook.com

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

#39

Post by donnellycc »

3xblah wrote: post #37
JMTQp8lwXL wrote: post #3

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 experience." By not using a graphical, JavaScript-enabled browser, I have been experiencing the web this way for the last 15 years. It works just fine for the purposes I use if for, mainly informational retrieval. For me, there is no such thing as "page load time". This shifts all awareness to "server response time". This is more or less the same from one website to an…

How do you deal with pages that use JavaScript to fetch page content after the initial markup is loaded?

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

#40

Post by JohnFen »

donnellycc wrote: post #39
3xblah wrote: post #37

Earlier quoted context omitted.

"I wouldn't mind going back to a JavaScript-less experience." By not using a graphical, JavaScript-enabled browser, I have been experiencing the web this way for the last 15 years. It works just fine for the purposes I use if for, mainly informational retrieval. For me, there is no such thing as "page load time". This shifts all awareness to "server response time". This is more or less the same from one website to an…

How do you deal with pages that use JavaScript to fetch page content after the initial markup is loaded?

I'm not 3xblah, obviously, but I deal with those sites by not using them.
Post reply on HN