Hacker News Reader

I never interact with those. If they get in the way of reading something I fix it with the DOM inspector (by hiding, not deleting them. In case javascript is looking for the presence of the element.)

This has more than tripled the amount of time it takes to read an answer from stack overflow but I refuse to do something just because of a bad GUI.

View on HN

uBlock Origin has a handy filter under "annoyances" that seems to clear out several of these. Not perfect, but it helps.

I'm still baffled at the way this was rolled out. Why are we putting the requirement on website authors, and not browser vendors? There's a lot fewer of those to regulate.

> Why are we putting the requirement on website authors, and not browser vendors?

Because the website authors are the ones misbehaving. Why would the browser vendors pay the price?

I'm in complete support for punishing any abuse of market position from the browser vendors too, but that's not the answer you seek. Anyway, the correct course of action is to punish the website authors further for using those anti-patterns.

I find the reader-mode (I think it is called?) in firefox to be great at doing this for me :)

Reply on news.ycombinator.com