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…
Purge site data when site identified via old tracking cookies
111–120 of 135 posts
Re: Purge site data when site identified via old tracking cookies
#112Try Baitblock https://baitblock.app Baitblock has tracking resistance that also deletes first party cookies/other tracking mechanisms when it detects that you're not logged into a website.
Re: Purge site data when site identified via old tracking cookies
#113I 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?
Re: Purge site data when site identified via old tracking cookies
#114Earlier 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.
Re: Purge site data when site identified via old tracking cookies
#115Earlier 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…
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
#116Earlier 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.
Re: Purge site data when site identified via old tracking cookies
#117Earlier 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.
Re: Purge site data when site identified via old tracking cookies
#118Earlier 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..
Re: Purge site data when site identified via old tracking cookies
#119Earlier 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.
Is it useful? https://en.wikipedia.org/wiki/Banner_blindness
Re: Purge site data when site identified via old tracking cookies
#120Earlier 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…
(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)