Engineering blog aggregation lists decay over time

“Aliases are duplicating in the graph view and the searching result ### What happened? I found the alias feature works in an unusual way, and after checking this issue https://github.com/logseq/logseq/issues/4342#issuecomment-1048049248 and the related discussion, I figured it out and think it's really nice. > this is actually a feature, not a bug : > * if [[aliaspage]] is empty, all links are redirected to [[sourcepage]] > * if [[aliaspage]] has a different content from [[sourcepage]],li”

“Show HN: Self-updating engineering blogs repo with GitHub Actions Hi HN, There’s a great engineering blog aggregation repo on github kilimchoi/engineering-blogs that I’ve used for a while. It’s an excellent resource, but it hasn’t been actively maintained in a few years — and many links have moved or broken. That made me wonder: why do most “awesome engineering blogs” lists eventually decay? So I built an open-source repo that aggregates engineering blogs and keeps itself updated automatica”

“Ask HN: Best static site generator for a docs site in 2026? I'm looking for recommendations for a static site generator to rebuild our documentation site in 2026. 1. Markdown support 2. Fast build ( 60s) 3. Search without JS 4. Deploy on GitHub Pages Budget: $0”

“Ask HN: How do you stay up to date without information overload? I'm a backend developer, but I'm interested in a lot of other areas too: frontend, AI, infrastructure, architecture, and system design. I want to keep up with new ideas and advances in all of these. My problem is that most changelogs and news sources throw too much raw information at me. I spend a lot of effort going through it all just to figure out what actually matters. After a while I get overloaded, and then I give u”

“Ask HN: Is this normal HN ranking? I came back looking for a TechCrunch story about SV undermining democracy [0], and was surprised to find it had already dropped off the front page. Found it on page 2, but it's ranking was lower (44) than articles that it should seemingly outrank—based on comments (211), points (247) and time posted (12 hours ago). See screenshot [1]. For instance, at 38 is an older article with only 3 comments and 29 points. At 41 was a significantly older article with on”