3 ms·
This is run in your browser after the page content downloads and renders. It doesn't matter what tricks the server does.
by timdorr 6y ago
This is run in your browser after the page content downloads and renders. It doesn't matter what tricks the server does.
- Aissen 6y agoThe page does not contain the content. If you don't have the proper cookie, it redirects to a separate consent page; it looks like it's a popup, but the page has no content. It does not matter how much you massage the DOM or CSS: there's nothing below the "popup".
- timdorr 6y agoAh, I see what you mean. Yeah, that wouldn't apply here. It's likely that simply setting a particular cookie with a dummy value would bypass this.
- kevingadd 6y agoWashington Post's paywall has a fun variant on this where not only does it omit the content, it changes the current URL so you can't reopen it in another browser or share it with someone. It's exciting seeing how creative services will get when they're trying to get you to give away your data and/or money for something you can't see.
- neltnerb 6y agoNot to worry, I had a paid subscription and they still tried to track me constantly with 3rd party cookies on top of being able to track me from being logged in (and paying over a hundred dollars a year for the privilege). Just use NPR and donate the amount you'd willingly pay for the paper to your local station.
- chrisseaton 6y ago> It doesn't matter what tricks the server does. The server doesn't serve you the content until you accept... so it does matter what the server does.