No, it's not a bug. Upon accessing the review queue, answers dating all the way back to a few years ago can be seen, as the reputation thresholds for Late Answers have been changed. Answers are now eligible to go into the queue if the person answering has any less than 50 reputation earned on the site rather than just 1 reputation.
It may well have been is ...
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.
This is intended, the last sentence is meant to be explicit as to remove any confusion.
We previously had issues with network users with association bonuses and 0 involvement with a site causing issues, so at least 1-2 upvotes on the site is the barrier we set on protected questions. This is the only place I can think of where we actually lock privileges ...
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.
Not all badges are awarded immediately.
For some badges, there is a cron job that checks every so often to see if that badge should be awarded. The cron jobs for less common badges run less frequently.
For more information see https://meta.stackexchange.com/a/112873/134175
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
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. :)