News for hackers. Stuff that matters.
Re:Purge site data when site identified via old tracking coo... by JMTQp8lwXL on Thursday March 05, 2020 @03:05PM (#22497559)
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.
Re:Purge site data when site identified via old tracking coo... by JohnFen on Thursday March 05, 2020 @04:12PM (#22498331)
> 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 coo... by ghostpepper on Thursday March 05, 2020 @04:25PM (#22498474)
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.

Re:Purge site data when site identified via old tracking coo... by JohnFen on Thursday March 05, 2020 @04:36PM (#22498602)
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 coo... by pferde on Friday March 06, 2020 @04:35AM (#22502213)
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 coo... by DavideNL on Friday March 06, 2020 @07:55AM (#22503183)
I do approximately the same in macOS:

/Applications/Firefox.app/Contents/MacOS/firefox" --no-remote --profile "$(mktemp -d)

Re:Purge site data when site identified via old tracking coo... by pferde on Friday March 06, 2020 @09:29AM (#22503796)
Mine has the advantage of the browser processes not having access to anything important, in case of a RCE vulnerability. An attacker would just see a vanilla debian install with no juicy user data, and only the ~/Downloads directory linked from my "real" system.
Re:Purge site data when site identified via old tracking coo... by s_gourichon on Friday March 06, 2020 @09:14AM (#22503696)
Isn't it what the "private browsing" option of Firefox does?
Re:Purge site data when site identified via old tracking coo... by DavideNL on Friday March 06, 2020 @11:40AM (#22504961)
Mostly, yes. The bonus is you don't use your normal settings + extensions. Which also means ALL websites work, regardless of privacy related settings that might break some websites. So it's a handy alternative.
Re:Purge site data when site identified via old tracking coo... by llarsson on Friday March 06, 2020 @07:48AM (#22503152)
That sounds very cool! Do you have that setup documented somewhere, or perhaps even pushed it to some public repo?
Re:Purge site data when site identified via old tracking coo... by pferde on Friday March 06, 2020 @09:27AM (#22503772)
I do not, sorry. I have to set up a blog some day, but I have been putting it off because most of the time I can't think of anything interesting to say. :)

Anyway, I was mostly inspired by an article on how to set up Steam in a container - it has all the details, including how to pipe Pulseaudio inside (so in my case, Youtube videos in Firefox can have sound). Except mine is debian-based (so debootstrap instead of pacstrap to populate the container).

http://ludiclinux.com/Nspawn-Steam-Container/

Re:Purge site data when site identified via old tracking coo... by wtallis on Friday March 06, 2020 @12:33AM (#22501216)
I've found that about half of the sites that render a blank page without JS are just setting style="visibility: hidden" on the <body> 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.
Re:Purge site data when site identified via old tracking coo... by onion2k on Friday March 06, 2020 @02:22AM (#22501620)
"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 tracking long before they give up users who care about styling, because there are just a lot more people who care about styling. It's an unfortunate fact of web life.

Re:Purge site data when site identified via old tracking coo... by wtallis on Friday March 06, 2020 @03:39AM (#22501938)
> and unfortunately that's often hiding everything until it's ready.

These sites usually aren't successful in that goal. Sure, they may be able to prevent content from showing up until the webfont has been loaded, but in my experience it's still extremely common for content to seriously jump around as the ads continue to load, especially on smaller screens (mobile).

So using "flash of unstyled content" as an excuse just doesn't hold up: users still have to learn to give a site a few extra seconds to settle before it's safe to interact without the content reflowing under your finger to put an ad where you wanted to tap, and breaking accessibility "for the sake of preventing FOUC" is dumb when you still have FOUC.

A similar tactic I've also seen that is even more unjustifiably anti-user is when the <body> element has "overflow: hidden" set until some heinous script that does it's own poor implementation of smooth scrolling can get up and running. These sites are universally improved by blocking such scripts and enabling native scrolling. This is one of the reasons why I believe browsers should be bundling together a large number of permissions that are off by default for every site the user has not flagged as being a web app. Google Maps has a good reason to interfere with scroll behavior; a news article does not.

Re:Purge site data when site identified via old tracking coo... by pjc50 on Friday March 06, 2020 @06:11AM (#22502691)
> 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 coo... by onion2k on Friday March 06, 2020 @07:20AM (#22503009)
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 coo... by pjc50 on Friday March 06, 2020 @07:54AM (#22503177)
And the second part - where does the bug lie that this happens at all?
Re:Purge site data when site identified via old tracking coo... by saagarjha on Friday March 06, 2020 @12:34AM (#22501220)
> "Flash of unstyled content" is not a valid concern here.

Well, presumably it is to some people, or they wouldn't be setting it…

Re:Purge site data when site identified via old tracking coo... by ohithereyou on Thursday March 05, 2020 @04:36PM (#22498604)
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 coo... by DarthGhandi on Friday March 06, 2020 @01:13AM (#22501354)
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.

Re:Purge site data when site identified via old tracking coo... by mcv on Friday March 06, 2020 @02:52AM (#22501747)
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 coo... by DarthGhandi on Friday March 06, 2020 @05:15AM (#22502408)
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 coo... by tyingq on Thursday March 05, 2020 @09:37PM (#22500569)
Maybe less frustrating than a site that works, and then doesn't. Like a checkout path with a hard dependency near the end.
Re:Purge site data when site identified via old tracking coo... by numpad0 on Thursday March 05, 2020 @11:55PM (#22501086)
What would be the ways to keep JavaScript virtually “off” but viewable?

I mean, it’s all the same framework-min.js working like a modern COBOL, not like custom mathematically significant compression or advanced dynamic P2P webpage distribution, right? Feels to me like a meta rendering engine could be created so none of the functions needs to be runtime evaluated or content be fetched by it or whatnot.

Re:Purge site data when site identified via old tracking coo... by saagarjha on Friday March 06, 2020 @12:35AM (#22501224)
Trying to emulate running JavaScript will quickly devolve into running it, but slowly and poorly.
Re:Purge site data when site identified via old tracking coo... by JMTQp8lwXL on Thursday March 05, 2020 @06:08PM (#22499357)
Hit or miss. I find a noticeable number of sites to be unusable. Some sites send completely usable HTML on the initial response and it's a great experience.

Back when this used to be my default policy, I'd whitelist sites that I deemed worthy. I had maybe 1-2 dozen sites (e.g., my bank among them) enabled.

Re:Purge site data when site identified via old tracking coo... by mcv on Friday March 06, 2020 @02:03AM (#22501539)
On Mobile I've got NoScript active, but it does break a lot of sites. Most sites are easily fixed by allowing first-party javascript while blocking third-party javascript. Third-party javascript is most likely to be trackers and ads anyway.
Re:Purge site data when site identified via old tracking coo... by smichel17 on Thursday March 05, 2020 @11:37PM (#22501031)
Agreed. Particularly blatant example: Android developer documentation. Once you allow it to run the gstatic script, it slows to an absolute crawl.
Re:Purge site data when site identified via old tracking coo... by reificator on Thursday March 05, 2020 @03:08PM (#22497591)
If "reasonably formatted" means CSS comes along for the ride, prepare for tracking pixels behind onhover rules, and on and on we go...
Re:Purge site data when site identified via old tracking coo... by a1369209993 on Thursday March 05, 2020 @04:10PM (#22498299)
Why would that matter? If the browser fetches images hidden behind onhover, then presumably it would also fetch plain <img> 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 coo... by ojame on Thursday March 05, 2020 @04:29PM (#22498523)
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 coo... by a1369209993 on Thursday March 05, 2020 @06:33PM (#22499562)
> Because after you hover on something, it can be an indication of intent.

Yes, that's (one of the many reasons) why javascript needs to die.

> Just loading an image when the webpage loads doesn't give you any insight into what the user 'interacted' with.

That's what I said: regardless of whether the browser, when loading a page, does or does not include hidden images in what it fetches, that cannot possibly tell you anything about what the user interacts[0] with after the page has loaded and browser is no longer communicating with your server.

0: edit: obviously excluding clicking links or other navigation-causing interactions, but that's a separate problem.

Re:Purge site data when site identified via old tracking coo... by reificator on Thursday March 05, 2020 @07:58PM (#22500133)
> > > Because after you hover on something, it can be an indication of intent.

> Yes, that's (one of the many reasons) why javascript needs to die.

You're missing the point. CSS allows you to load tracking pixels on hover, so you can do that without Javascript.

Re:Purge site data when site identified via old tracking coo... by a1369209993 on Saturday March 07, 2020 @06:06PM (#22514894)
I was going to say "no it doesn't, that's blatantly stupid, you load things during page load, that's why it's called page load" but on further research, Firefox apparently does do that now. I hate everything and I'm once again glad I stopped updating years ago.[0]

0: I decline to treat the unintentional flaws of [Firefox] as more important than the intentional ones.[1]

1: https://www.gnu.org/philosophy/upgrade-windows.html

Re:Purge site data when site identified via old tracking coo... by rovr138 on Thursday March 05, 2020 @07:31PM (#22499978)
> Yes, that's (one of the many reasons) why javascript needs to die.

On hover can be easily done with css.

selector:hover{background-image: url();}

That can trigger a tracking pixel.

Re:Purge site data when site identified via old tracking coo... by moring on Friday March 06, 2020 @02:21AM (#22501616)
A browser that disables Javascript could easily circumvent this too, either pre-loading URLs in :hover rules or ignoring those rules.
Re:Purge site data when site identified via old tracking coo... by JMTQp8lwXL on Thursday March 05, 2020 @03:11PM (#22497629)
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.
Re:Purge site data when site identified via old tracking coo... by ficklepickle on Thursday March 05, 2020 @05:01PM (#22498823)
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 coo... by matheusmoreira on Friday March 06, 2020 @12:01AM (#22501111)
Browsers could disable downloading of external resources for CSS :hover and :active. When the user interacts with the interface, the CSS will still get applied but the tracking URL won't be accessed.
Re:Purge site data when site identified via old tracking coo... by moring on Friday March 06, 2020 @02:28AM (#22501647)
Alternatively, such URLs can always be pre-fetched on page load.
Re:Purge site data when site identified via old tracking coo... by JMTQp8lwXL on Thursday March 05, 2020 @06:09PM (#22499368)
Agreed, but it would likely break things that don't matter much to me. A well defined semantic document should say what it has to say, without the use or necessity of :hover or :active states.
Re:Purge site data when site identified via old tracking coo... by GoblinSlayer on Friday March 06, 2020 @07:10AM (#22502958)
Turned off javascript is more about usability than tracking prevention.
Re:Purge site data when site identified via old tracking coo... by _jal on Thursday March 05, 2020 @03:56PM (#22498133)
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.

Re:Purge site data when site identified via old tracking coo... by forgotmypw16 on Thursday March 05, 2020 @04:11PM (#22498315)
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 coo... by tekstar on Thursday March 05, 2020 @04:43PM (#22498678)
And if you want messages access just use mbasic.facebook.com
Re:Purge site data when site identified via old tracking coo... by overcast on Thursday March 05, 2020 @03:09PM (#22497610)
Nothing stopping you from doing this on your next / current project. I've been 100% committed on getting the web back to as lightweight as possible for the last couple years worth of development.
Re:Purge site data when site identified via old tracking coo... by simple_phrases on Thursday March 05, 2020 @03:26PM (#22497788)
Almost all front-end development jobs are looking for React or Vue skills.
Re:Purge site data when site identified via old tracking coo... by swiley on Thursday March 05, 2020 @03:56PM (#22498132)
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.
Re:Purge site data when site identified via old tracking coo... by simple_phrases on Thursday March 05, 2020 @04:32PM (#22498561)
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 coo... by illumanaughty on Thursday March 05, 2020 @04:25PM (#22498473)
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 coo... by swiley on Friday March 06, 2020 @08:52AM (#22503492)
There absolutely is a place for the interactive web. But this is rare, and it’s done well even less often.
Re:Purge site data when site identified via old tracking coo... by JMTQp8lwXL on Thursday March 05, 2020 @06:10PM (#22499382)
You can server-side render React (not sure about Vue, but wouldn't be surprised if you could).
Re:Purge site data when site identified via old tracking coo... by artificial on Thursday March 05, 2020 @08:24PM (#22500257)
Yes, you’re right about Vue having server side rendering. It’s called Nuxt.
Re:Purge site data when site identified via old tracking coo... by mcv on Friday March 06, 2020 @02:56AM (#22501757)
Nuxt is a tool that sets up your entire project including the option for server-side rendering. There are other SSR tools for Vue, and I think in Vue 3 it might be built-in. There's a lot of focus on server-side rendering lately.
Re:Purge site data when site identified via old tracking coo... by throwsprtsdy on Thursday March 05, 2020 @03:14PM (#22497655)
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.
Re:Purge site data when site identified via old tracking coo... by ryantgtg on Friday March 06, 2020 @12:47AM (#22501264)
I pay for the LA Times, and I also block ads. A couple weeks ago they updated the site so that I got a giant “you are blocking ads!!” banner even when I was logged in. I complained to them (directly), saying that I pay for a subscription so that I can give them money without viewing ads. And... they agreed that paying readers should not see those warnings! And they updated the site within the same day.

I thought that was cool.

Re:Purge site data when site identified via old tracking coo... by ComputerGuru on Friday March 06, 2020 @09:28AM (#22503786)
I just block the “you’re not seeing my ads!” div itself. Some of us have issues that prevent us from focusing on the content when there are highly contrasting alerts screaming something.
Re:Purge site data when site identified via old tracking coo... by phkahler on Thursday March 05, 2020 @03:27PM (#22497806)
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.

Re:Purge site data when site identified via old tracking coo... by GoblinSlayer on Friday March 06, 2020 @07:21AM (#22503012)
>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 coo... by throwsprtsdy on Thursday March 05, 2020 @03:59PM (#22498166)
> 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 coo... by ohithereyou on Thursday March 05, 2020 @04:39PM (#22498639)
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 coo... by throwsprtsdy on Thursday March 05, 2020 @05:34PM (#22499076)
I was thinking more about investigative reporters and news outlets than buggy-whip makers.
Re:Purge site data when site identified via old tracking coo... by ohithereyou on Thursday March 05, 2020 @10:22PM (#22500737)
If you're going to treat investigative reporting and news gathering as a profit making venture then you can only charge what the market is willing to pay, and for the vast majority of people, that's nothing.
Re:Purge site data when site identified via old tracking coo... by mcv on Friday March 06, 2020 @03:02AM (#22501781)
Investigative reporting is in a tough spot in a capitalist democracy. In a democracy, good reporting is a vital part of the system, but in capitalism, people pay for what they want to see and hear, and that's not always the truth.

Advertisers directly or indirectly impacting the kind of news that gets reported doesn't help.

Re:Purge site data when site identified via old tracking coo... by phkahler on Thursday March 05, 2020 @06:50PM (#22499716)
>> 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?

They're not. Think about news sites that rewrite stories from paywalled sites and collect ad revenue. They are parasites that make money from other peoples work. Same thing for all those YouTube channels (though they are not other sites) that repackage other peoples content and make money doing so.

What we need is not so much a way to advertise on the net, but a way to make small payments and subscriptions simple. If sites needed their users to pay them, the quality of the content might go up dramatically. Places like HN could still exist just fine too.

Having said that, I think there are ways to verify ads without cookies and such. It's just that it takes more effort on the server side.

Re:Purge site data when site identified via old tracking coo... by throwsprtsdy on Thursday March 05, 2020 @07:15PM (#22499854)
> If sites needed their users to pay them, the quality of the content might go up dramatically

What do you mean by "if"? There are already many sites that require users to pay them (e.g. The New York Times) but everyone simply circumvents their paywalls.

Every method that high-quality sites use to generate the revenue they need to operate is defeated either by ad blockers or someone reproducing their content outside their paywalls. You may be right that news and reporting are not viable, but it is a shame.

Re:Purge site data when site identified via old tracking coo... by mcv on Friday March 06, 2020 @02:58AM (#22501765)
Some sites handle their own advertising, and a few do it in a really cool way. For example, the Penny Arcade web comic only advertises games they like[0], and they hand-draw their own ads for it in the same style as the comics. Sounds like incredibly valuable advertising for those games, and it fits the style of the site.

[0] Or used to. I haven't checked them in years.

Re:Purge site data when site identified via old tracking coo... by a3n on Friday March 06, 2020 @08:31AM (#22503366)
The reason it's worth it for advertisers to pay sites for placing ads is because of the data they collect.

You only buy something because of an ad occasionally. But data is collected each and every time.

Re:Purge site data when site identified via old tracking coo... by mumblemumble on Thursday March 05, 2020 @03:34PM (#22497868)
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.

Re:Purge site data when site identified via old tracking coo... by jtolmar on Thursday March 05, 2020 @05:21PM (#22498976)
Most site interactivity could be handled with forms (though some form inputs need improvement) or some sort of conditional view state (for menus and HN's collapse comment feature). For anything more complex I think the "click to enable" model that flash and applets eventually followed is compatible with anything that actually deserves custom code.
Re:Purge site data when site identified via old tracking coo... by ComputerGuru on Friday March 06, 2020 @09:48AM (#22503944)
I’ve given this a lot of thought over the years and I think html needs slightly more functionality to completely obviate JS. The hardest impact of no JS is dynamic input forms, and I remember when ajax first became a thing and forms that didn’t lose their content on an input error became commonplace. There was never a good reason for them to lose their input, of course, as that’s just lazy coding.

But when writing JS-free front ends for my web apps, the ugliest UX is trying to fill out a form that requires either filling out n identical sections (eg a fieldset for each student you want to add) or selecting an item from a drop-down w/ the option of adding to it if the desired option doesn’t exist.

Error validation is now clean and easy with modern MVC frameworks that take as input the same structure of data they used to generate the page in the first place, so it is easy to rebuild the page exactly as it was but also include an error message. There is no jarring user experience when the page is submitted and reloaded with the error shown inline. But having to navigate to a separate page to add an entity then refresh the form to fill out the data selecting the newly added entity sucks.

HTML needs some sort of functionality that would enable a) dynamic non-Turing-complete remote resource backing of form input values, b) allowing a form input to return post submission to a dom element rather than a document (E.g. imagine an input to “add location” to a drop down; submitting that field would return the new content of the select option elements to replace the existing). A JS powered example is intercooler JS.

More generally, a content response type that says “patch the existing DOM with the following” would preserve pretty much all the good parts of Web 2.0 without the crap that came with it; keeping in mind that submissions could only happen when a user explicitly requested them.

Re:Purge site data when site identified via old tracking coo... by mosburger on Thursday March 05, 2020 @04:02PM (#22498208)
Hear me out - we could all start using Gopher?
Re:Purge site data when site identified via old tracking coo... by mcv on Friday March 06, 2020 @02:09AM (#22501569)
> "I know not all tracking is based on JS, but the browser provides so many heuristics this way: screen size, cursor location, installed plugins."

Installed plugins? Why would javascript need to know my installed plugins? I'd like my browser to more actively restrict what javascript has access to. I get a popup when it wants access to my location (which I generally deny). Why not do the same with these other features?

"This site wants to view your installed plugins. Allow/deny?" "This site wants to set a non-login cookie" Deny, deny, deny.

Re:Purge site data when site identified via old tracking coo... by akiselev on Friday March 06, 2020 @02:35AM (#22501674)
I don't think they can see the plugins themselves but any code that the plugins run in the document context will throw exceptions that can be caught by any fingerprinting code. I see a variety of uncaught exceptions with obvious plugin names on my Sentry feeds.
Re:Purge site data when site identified via old tracking coo... by 3xblah on Thursday March 05, 2020 @04:39PM (#22498644)
"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 coo... by XCSme on Thursday March 05, 2020 @07:46PM (#22500073)
How do you collapse comments on HackerNews?
Re:Purge site data when site identified via old tracking coo... by 3xblah on Friday March 06, 2020 @01:02AM (#22501312)
When I started visiting HN around 2008-2009, if I am not mistaken, the website used no JavaScript. Anyway, in the browser I use, HN is "flat" threads, all posts visible and left justified, no indentation. It still looks just the same as it did in 2008-2009.
Re:Purge site data when site identified via old tracking coo... by saagarjha on Friday March 06, 2020 @12:37AM (#22501231)
I keep JavaScript on, but I rarely collapse comments. I could probably browse Hacker News without JavaScript if I wanted to, because they've taken care to make most of it work.
Re:Purge site data when site identified via old tracking coo... by donnellycc on Thursday March 05, 2020 @04:52PM (#22498745)
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 coo... by JohnFen on Thursday March 05, 2020 @04:57PM (#22498793)
I'm not 3xblah, obviously, but I deal with those sites by not using them.
Re:Purge site data when site identified via old tracking coo... by code_duck on Thursday March 05, 2020 @06:22PM (#22499481)
I wish that was a choice for me. Often I have to interact with websites for services such as phone accounts, banks or taxes where I don’t have the reasonable option of choosing to not use the site.
Re:Purge site data when site identified via old tracking coo... by JohnFen on Friday March 06, 2020 @01:48PM (#22506138)
Oh, that sucks. I'm lucky -- I can do all those things without having to bring the internet into the equation.
Re:Purge site data when site identified via old tracking coo... by code_duck on Friday March 06, 2020 @11:24PM (#22509721)
I could make a phone call, but I don't see how that is making my life better.
Re:Purge site data when site identified via old tracking coo... by 3xblah on Thursday March 05, 2020 @06:39PM (#22499621)
"How do you deal with pages that use Javascript to fetch page content after the initial markup is loaded?"

Provide an example page and I will demonstrate how I would solve the problem.

Not every user visits the same websites and web pages, so without giving specific examples, discussions about how to deal with these pages never go anywhere on HN.

To be honest, out of all the websites I have visited over entire lifetime using the www, the number where I have had to make any extra effort because of Javascript in order to retrieve some text/html, image or video is very small proportion. Not one that is large enough to justify using a JavaScript-enabled browser as default. For me, these are exceptional cases, not the norm.

The extra effort is usually a one-off script, not something I need to save.

Occasionally it is something I save for future use. One example of a saved script would be for non-commercial YouTube channels. Goal was a 2-column CSV of all videos from a channel in the form of title, url. Goal was not "perfection", just quick solution.

yy025 and yy032 are custom utilties for generating HTTP and decoding HTML, respectively.

Using a short script called "ytc" the process would be something like the following. openssl s_client is used as an example of a TLS client. "XYZ" is the name of the channel.

   echo https://www.youtube.com/channel/XYZ/videos|ytc|sed wXYZ

   Connection=keep-alive yy025 < XYZ|openssl s_client -connect www.youtube.com:443 -servername whatever -ign_eof > 1.html

   ytc title < 1.html > XYZ.1

   ytc url < 1.html > XYZ.2

   paste -d, XYZ.[12] > XYZ.csv
Here is the "ytc" script

   case $1 in 
   "")exec 2>/dev/null;
   export Connection=close;
   yy025|openssl s_client -connect www.youtube.com:443 -servername whatever -ign_eof |sed 's/%25/%/g'|yy032 > 1.tmp;
   while true;do
   x=$(sed 's/%25/%/g;s/\\//g' 1.tmp|yy032|grep -o "[^\"]*browse_ajax[^\"\\]*" |sed 's/u0026amp;/\&/g;s/&direct_render=1//;s,^,https://www.youtube.com,')
   echo > 1.tmp;
   test ${#x} -gt 100||break;
   echo "$x";
   echo "$x"|yy025|openssl s_client -connect www.youtube.com:443 -ign_eof > 1.tmp;
   done;rm 1.tmp

   ;;-h|-?|-help|--help)echo usage: echo https://www.youtube.com/user/XYZ/videos \|$0;echo "usage: $0 {title|url} < html-file"
   ;;1|title) sed 's/\\//g;s/u0026amp;//g;s/u0026quot;//g;s/u0026#39;//g'|grep -o "ltr\" title=\"[^\"]*"|sed 's/ltr..title=.//'  
   ;;2|url) sed 's/\\//g;s/u0026amp;//g;s/u0026quot;//g'|grep -o "[^\"]*watch?v=[^\"]*" |sed 's,^,https://www.youtube.com,'|uniq
   esac
Re:Purge site data when site identified via old tracking coo... by meerita on Friday March 06, 2020 @04:15AM (#22502108)
I've moved my blog long time ago to static pages. I've removed Google Analytics long time ago too. Now I have a slickest web experience and the reports of searchs and server usage is increasing.
Re:Purge site data when site identified via old tracking coo... by ck2 on Thursday March 05, 2020 @05:50PM (#22499202)
Alternatively since nojs breaks a bunch of things, also try uMatrix, really locks things down and shows you what kind of nonsense is going down in a nice (blockable) grid.
Re:Purge site data when site identified via old tracking coo... by XCSme on Thursday March 05, 2020 @07:48PM (#22500081)
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 coo... by s188 on Friday March 06, 2020 @05:13AM (#22502396)
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 coo... by jimbob45 on Thursday March 05, 2020 @03:11PM (#22497623)
uMatrix basically does that for you now.
Re:Purge site data when site identified via old tracking coo... by mgbmtl on Thursday March 05, 2020 @03:14PM (#22497651)
Blocking trackers helps a lot for performance, and I second uMatrix. I even showed my 13 year old kid how to use it. However, uMatrix on mobile is not particularly easy to use (I use it, but would not recommend it).
Re:Purge site data when site identified via old tracking coo... by OJFord on Thursday March 05, 2020 @03:37PM (#22497901)
I didn't even realise it worked on mobile, I use uBlock on Android but uMatrix otherwise (actually I think both, maybe because of synchronisation).

The zapper's fairly easy to use to get rid of annoyances on mobile, until you make a mistake. Editing the rules file isn't the nicest UX even on desktop FF. (It'd be good, for example, to be able to preview what's being blocked, and selectively re-allow them.)

For an example of how it can go wrong: you block 'overlay', then it reveals and you block 'grey-blur-modal-focus', allowing you to click whatever you wanted, except it turns out that it uses 'overlay' and you shouldn't have blocked that one.