It might just be that the achievement was awarded correctly, it was the asker who did it wrong.
The way this badge works is as follows. When I click on Share on this post, I get this URL:
That's because I'm user 23. If you press it, you'll get:
Whenever one of ...
We did some testing and it appears that the issue was on comment limits. Election nominations only show up to 15 comments before expansion. However! There's no button to expand comments!
Posting a new comment auto-expands which is why people could see things only when commenting.
As a bandaid, we've increased the comment limit to 40 for now, but we're ...
This issue is happening because you typed out "age of" and then clicked "age-of-empires-2" from the suggestion drop down that shows up. When you do that it adds "age-of-empires-2", but it doesn't remove the "age of" tags that you included. I'm assuming this is expected behaviour, since it lets you add multiple tags at once. In order to avoid this issue, ...
Using the information I could gather, I found the post in the first screenshot was this one, which is your own. You can cast close votes on your own posts starting at 250 reputation (and you can delete your own posts that meet certain criteria, which is why delete is visible too).
Casting close votes on other questions requires 3,000 reputation.
My fault. Isn't it always? We had a problem with badges failing to award last night, so I added some extra logging to capture more info when it stumbled. In the process I accidentally broke something such that it appeared to work, but really didn't actually do anything. Deploying the fix now. Sorry folks.
It's perfectly normal. The first result is the answer to the question, which is the second result. (See the "A:" and "Q:" prefixes.) If you only want to see one, not the other, use is:answer or is:question in the search.
Excavator requires you edit someone else's post, not your own:
Self-edits do not count for the Excavator or Archaeologist badges. It must be an edit on another owner's (or anonymous/deleted user's) content.
We don't want to encourage self-bumping of content in an attempt to get votes by bumping it on the front page for the sake of doing so...it's meant to ...
Are you sure you've never seen that question before? If it wasn't you, who wrote this question? ;)
In the following screenshot, the first link is the question you've "never seen before":
It looks like you just forgot that you shared it. You can search a site for a part of a url with e.g. url:54525/145980
This is due to incorrect rounding. It has been partially fixed, but only for years: Post was closed before it even existed is status-completed.
I think your particular case might be the same as this meta SE bug report:
Inconsistent rounding of "months ago" which is currently status-deferred - according to JNat♦ (Community Manager at SE) there are ...
I outlines why we don't support this in a blog post here:
Stack Overflow: The road to SSL
If we do end up going full SSL, the domains will move to *.meta.stackexchange.com, which we can secure easily as we add sites. We don't have definite plans on this yet. We will be working on it in 2014 as we investigate the best way to make our sites faster all ...
With Stack Exchange's move to a standardized site design, this issue has been solved (albeit inadvertently). The 'Ask Question' button has been moved:
and the mothership now aligns properly:
Don't mind the horrible cropping on my part - the button and mothership ARE actually aligned. :)
This is not a bug. Retrosaur normally has tens of thousands of reputation points and earned those badges through normal use of the site. Right now this user is on a temporary suspension, so the rep was temporarily set to 1 by the system. You can see the suspension info by clicking on the user's profile page.
This account is temporarily suspended to cool ...
Thanks again for reporting. It definitely was a bug caused by the new footer UI across the whole network. The fix is now waiting in repo for build. You should be able to see the footer artwork in couple hours.
There is probably a small timing difference when an account is scheduled for deletion, vs when the script that processes deleted accounts actually runs.
It seems to have run now, in any case.
All Stack Exchange sites, including meta sites, run off a very similar code base. Because they're running basically the same code, meta sites like this one get the same list of badges. Removing them would potentially mean moving the meta sites to a separate code base, making the changes to remove them, then maintaining two code bases in the future.
Even if ...