Live data from Hacker News

Purge site data when site identified via old tracking cookies

bugzilla.mozilla.org

111–120 of 135 posts

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

#111
post #33

Earlier quoted context omitted.

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 wa…

I have an ephemeral container (systemd-nspawn with -x switch) with almost-default configuration of firefox (only uBlock Origin added) for such websites. After I'm done, I close the browser and everything gets deleted.

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

#113
post #60

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.

This just made me think of something. How do the GDPR popups work if you don't have JavaScript enabled? Are the sites still GDPR compliant if they track you using cookies because you disabled the JS which should have disabled the cookies?

The JavaScript ones simply don't appear - which is nice. And yes, I believe they're in breach of GDPR if they use cookies and tracking pixels to track me without giving me the opportunity to deny consent. Please note I'm not a lawyer but I don't think there is a legal obligation for me to use their sites with JavaScript enabled.

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

#114
post #92

Earlier quoted context omitted.

A pious stance, for sure. Yet I'm convinced you probably do enable js for various payment portals and govt/financial websites, and they often tend to go blank or loop out far more than the average site. Apart from carefully cultivating a working noscript over years , the simplest solution may be to use a different browser for these sorts of interactions. Reminds me to backup my whitelist. It's actually quite valuable…

On the other hand, I would hope that government and banking sites don't use ads and tracking cookies.

Agree but you can usually block such things perfectly fine on govt websites without losing any functionality whatsoever.

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

#115
post #89
post #73

Earlier quoted context omitted.

I've found that about half of the sites that render a blank page without JS are just setting style="visibility: hidden" on the element. I cannot think of any good reason for browsers to continue to allow that CSS property to be set on that element. "Flash of unstyled content" is not a valid concern here.

"Flash of unstyled content" is not a valid concern here. Except it really is. Most websites are attached to businesses in some way. If you see statistics that the flash of unstyled content means 10% of your traffic leaves the site after less than a second you do what you can to fix it, and unfortunately that's often hiding everything until it's ready. Pragmatically, most businesses would give up users who don't like…

> flash of unstyled content means 10% of your traffic leaves the site after less than a second

Really?

Why does this happen at all? After all the "visible=false" is a styling..

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

#116
post #84
post #57

Earlier quoted context omitted.

Best decision I have made so far is setting up a catch-all polic for my domain. any_random_address@mydomain.com is saved in a "dummy" inbox, I check it from time to time and give different emails for different services to identify who sold my email. instagram is insta@mydomain.com, netflix is nflx@mydomain.com etc. If someone needs pointers: I use webfaction for MX, setup mailboxes with catch-all policy and setup a r…

I've used migadu.com for well over a year now and been very happy with them. They let you setup multiple regex based catchalls, so I can create any address prefixed with shop and have it forwarded to one address, while ones prefixed with game get forwarded to another. If you aren't planning on sending any emails from the domain, their free single domain plan might work very well for you.

Occasionally I have to send emails especially when I have to respond to a customer care response. But will take a look, I am willing to pay for this(I am already paying for webfaction).

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

#117

Earlier quoted context omitted.

By reasonably formatted, I would actually exclude onhover. To clarify, I meant a document that would be readable without any interaction. You've got me wondering if privacy-focused browsers like Brave have the ability to disable potential tracking mechanisms like onhover.

Disabling CSS :hover and :active states might break sites. Tracking pixels could be as simple as a background image set for either of those CSS states.

Turned off javascript is more about usability than tracking prevention.

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

#118
post #115
post #89

Earlier quoted context omitted.

"Flash of unstyled content" is not a valid concern here. Except it really is. Most websites are attached to businesses in some way. If you see statistics that the flash of unstyled content means 10% of your traffic leaves the site after less than a second you do what you can to fix it, and unfortunately that's often hiding everything until it's ready. Pragmatically, most businesses would give up users who don't like…

> flash of unstyled content means 10% of your traffic leaves the site after less than a second Really? Why does this happen at all? After all the "visible=false" is a styling..

Some people decide whether or not a site is worth looking at extremely quickly - if it looks "old" or "broken" they hit the back button immediately. They will wait for the first paint though, so it can be better to delay anything appearing until everything is ready. The impact depends a lot on demographics.

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

#119

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.

>verification that an ad has actually been shown to a human

Is it useful? https://en.wikipedia.org/wiki/Banner_blindness

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

#120
post #57
post #45

Earlier quoted context omitted.

Or a sign-in with Apple-like system so tracking is limited to each site.

Best decision I have made so far is setting up a catch-all polic for my domain. any_random_address@mydomain.com is saved in a "dummy" inbox, I check it from time to time and give different emails for different services to identify who sold my email. instagram is insta@mydomain.com, netflix is nflx@mydomain.com etc. If someone needs pointers: I use webfaction for MX, setup mailboxes with catch-all policy and setup a r…

That's grand until someone runs a dictionary spamming attack on your domain. One of the interesting complexities here is if you forward to gmail from a domain, and there's too much spam, it'll blacklist your mail forwarder as a spammer.

(n.b., I've done something like this for ~nearly 20~ 23 years, and I've scaled back to prefix+tag with some aggressive blocking of email addresses that have been leaked/sold)

Post reply on HN