That would contradict the intention of marking threads [dupe] in the first place. The story already had major attention, significant front page time, and hundreds of comments. Having a second major discussion about the same story soon afterward is just what the [dupe] system is trying to prevent. Otherwise the front page would consist mostly of the same hot stories, repeated over and over. HN users definitely don't want this, and such repetition is inconsistent with the mandate of the site: https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so...

It's true of course that for users who didn't see the first thread, the second is not a duplicate at all. But we don't have a good way to know who's who, so we have to rely on a global approach, hopefully one which is simple and easily explicable. (This is in the FAQ under "reposts": https://news.ycombinator.com/newsfaq.html).

In the end, there's nobody who sees all the threads on HN, or even all the major ones. Everyone misses tons of interesting material, but what it is varies for each person. This is a discoverability problem. Hopefully we can get better at solving it, but the solution is not to allow duplicates of major discussion, because that would just crowd out fresher interesting material.