Links don't imply that something shouldn't have been posted! They are just for curious readers to explore further. It's a way of sharing the riches of HN's archives.
(Separately, it's true that HN normally shouldn't have a new front page thread for each incremental release of a project, because there are many more of those than there are slots on the front page. Users tend to upvote them reflexively as a sort of referendum on projects they like, and the threads is almost always a discussion of the project in general rather than of the specifics of a release. Those do get repetitive. But I wasn't implying anything about that with links.)
You could use the first paragraph of this comment in every post with links. For me that's explicit enough, even if a bit long to type. But you could save it somewhere and paste in the comment.
Comments
Links don't imply that something shouldn't have been posted! They are just for curious readers to explore further. It's a way of sharing the riches of HN's archives.
Sometimes I spell this out explicitly: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que.... But it gets tedious to keep repeating. I'm still looking for a brief, unambiguous wording that doesn't lead to misunderstanding.
(Separately, it's true that HN normally shouldn't have a new front page thread for each incremental release of a project, because there are many more of those than there are slots on the front page. Users tend to upvote them reflexively as a sort of referendum on projects they like, and the threads is almost always a discussion of the project in general rather than of the specifics of a release. Those do get repetitive. But I wasn't implying anything about that with links.)
You could use the first paragraph of this comment in every post with links. For me that's explicit enough, even if a bit long to type. But you could save it somewhere and paste in the comment.
Alas, that would be too pasty. The hivemind breaks out in hives with that much repetition.