I hear this quite a bit, and think there’s actually a good deal of nuance to it. I’ve seen places that insisted on comments for everything, and it was silly, a significant number of comments had no value. This made people not read comments, as opposed to other places I’ve worked with very few comments - when you ran across a comment you gave it more weight (something here was complex, or not as simple as it seemed).
So imo, use comments which can communicate effectively, but use them sparingly for important parts that are complicated, for the rest attempt to communicate with the code itself.
I’m very lazy so I’d probably start by looking at filters on those sites, if i really wanted to tackle this with programming, i’d:
see if there’s an api, or rss feed for these sites, if so i’d pull that down with a cron job and do filtering locally with probably regex.
if not i’d scrape the html and pull out the relevant links with whatever the latest html parser is for the language i use (i.e. it used to be beautiful soup for python, but there’s i think a new better one).
but as i said i’m rather lazy, and haven’t been on the prowl for jobs for some time.