Last I read, the policy on duplicate story-ID questions was that they both had to have accepted answers. This one that was just closed does not meet that criterion.

And it seems odd to close the one with an accepted answer, in favor of one that doesn't.

Not arguing, just asking if the policy changed.

| |
  • 2
    I edited your title to make it clearer that you're asking about a specific question and this meta post isn't simply a dupe of the policy on story-ID dupe closures. Hope you don't mind! – Rand al'Thor Sep 2 '16 at 19:25

The question you link to was closed as a duplicate by the Community ♦ user, which means that the OP themselves agreed it was a duplicate; see this announcement on main meta for when Community dupe-closures became a thing.

This is fine when the old question has an accepted answer but the new one doesn't, since by agreeing that it's a dupe the OP of the new question is essentially accepting an answer. (Some unanswered story-ID questions have even been closed this way in the past.)

However, in the example you link to, the new question has an accepted answer but the old one doesn't. This means that in the unlikely event that the current answer to the older question turns out to be incorrect and a different answer is posted and accepted, the dupe-closure will no longer be valid according to our policy. In view of this, I've reopened the question.

| |

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .