Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Sometime in the last day or so, the Community-created revisions that add the "Possible Duplicate" box to posts closed as duplicates started showing up on the post itself as edits by the owner. For example, on this post:

Screenshot of the post

The edit by Simon Brown was actually by Community, and shows up correctly in the revision history. The same thing happened on this post 5 hours ago, and this SO post 2 hours ago. These two SO posts that both closed yesterday are correct (they show no revision on the main page, and Community in the history)

share|improve this question
Nice catch. I've seen similar to this before when the latest editor of a post was deleted, but this is clearly not the case in this scenario. – Grace Note Jan 27 '11 at 19:17
What? But Community can't be Simon Brown's sockpuppet; it's Jon B's! – Pops Jan 27 '11 at 19:25
up vote 1 down vote accepted

The cause of this was fixed long ago (to be precise: on the same day you reported this). It was a side effect of a change that had the purpose to support the (then-new) suggested edits, but which had several undesired effects (also including the closing of a question to bump a post).

So this issue is (at most) only visible on questions that were closed as dupes on that day. In addition, the fix for When the last editor is deleted, the gravatar of the post owner is shown instead also affects this very case; after that's deployed, there won't be a double-signature anymore on those post; instead, the "anonymous avatar" will be shown as the editor, without a display name.

Granted, that's not 100% correct, but since it only affects very few posts (namely those that were closed as dupes on the day this bug was active, and have not been edited since) and isn't a real problem, I don't think it's worth doing some historical data fixup for this.

share|improve this answer

You must log in to answer this question.

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