Maybe someone can come up with a better solution, avoiding the hacky upward selection and avoiding repetition of the domain match.
The idea here is that we match an <a> element whose href contains the unwanted domain. Then upward(3) selects the great-grandparent element: we are assuming that the <a> is buried three levels within a <tr> element, and we nuke that <tr> element.
Even if a nicer rule is found, it's still not great UX to have to go into the filter panel and copy-paste rules.
Then we repeat the entire rule and add "+ tr" to nuke the successor also. The successor row has the small print: the story's points, who submitted it, number of comments, flag/hide buttons.
I made hackerer.news[0] that filters all stories for the day into groups. I should add a paywalled group since I usually skip them too.
Sometimes I'll just google part of the title and read a different article on the topic. It's rare for a story to only be reported by one source and I usually only care about deep details for tech which tends not to be paywalled much as business or politics.
Edit: I just wanted to make an issue for this and realized this is still on GitLab[1]--should move it too.
I'm still using an old extension called "Hacker News: Mark All Read" from 2015,
it marks all articles on the page as read once I click on the button (at the bottom of the page), it's very convenient.
It was updated un 2023 to keep on with new HTML formatting. Thanks to the authors (Guillaume Mouron, based on Daniele Mazzini code)! <3
This could definitely be done in a user script, or if someone's feeling especially bold, make a whole extension that redirects any paywalled news site to the archive.is equivalent
Go to My Filters, and add:
Maybe someone can come up with a better solution, avoiding the hacky upward selection and avoiding repetition of the domain match.The idea here is that we match an <a> element whose href contains the unwanted domain. Then upward(3) selects the great-grandparent element: we are assuming that the <a> is buried three levels within a <tr> element, and we nuke that <tr> element.
Even if a nicer rule is found, it's still not great UX to have to go into the filter panel and copy-paste rules.
Then we repeat the entire rule and add "+ tr" to nuke the successor also. The successor row has the small print: the story's points, who submitted it, number of comments, flag/hide buttons.
The list of keywords/domains is currently hard-coded (based on my preferences), but I intend to add an options page to set those.
The reason I wanted to just dim the stories is to make sure I can still read stories in case something got dimmed as a false positive.
[0] https://github.com/khaledh/hn-mod
Sometimes I'll just google part of the title and read a different article on the topic. It's rare for a story to only be reported by one source and I usually only care about deep details for tech which tends not to be paywalled much as business or politics.
Edit: I just wanted to make an issue for this and realized this is still on GitLab[1]--should move it too.
[0] https://hackerer.news/ [1] https://gitlab.com/karmakaze/hackerer-news
It was updated un 2023 to keep on with new HTML formatting. Thanks to the authors (Guillaume Mouron, based on Daniele Mazzini code)! <3
⁰ https://github.com/gabrielsroka/gabrielsroka.github.io/blob/...
¹ https://github.com/HackerNews/API
It filters and summarizes stories using LLM and your prompt on any site including HN!
This could definitely be done in a user script, or if someone's feeling especially bold, make a whole extension that redirects any paywalled news site to the archive.is equivalent
Most soon receive a comment having a bypassing link e.g. to archive.ph.