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 seems the consensus is to change the wording to be geared towards editing the current question, rather than asking another. I propose the quote should be:
This question has been asked before and already has an answer. If those answers do not fully address your question, or if your question is actually different than the duplicate, [please edit your ...
What you've described is how it works already.
When the asker doesn't manually award the bounty, it goes to the highest up-voted answer posted since the start of the bounty. If no new answers have been posted (or none have received upvotes), the bounty fades away into the ether.
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 ...
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, ...
I have it on good authority that arqade.com will continue to redirect to gaming.stackexchange.com:
We had a long process in coming to this decision, part of it including actual mechanical nuisances involved with actually changing the domain name. I don't recall all of those, so I'll just stick with the other reason - consistency with the other domain ...
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 feature likely doesn't exist because it would be a lot of work for the dev team for absolutely no gain. Creating a new tag takes a matter of seconds, and handling the occasional tag creation request from new users doesn't take much longer.
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 ...
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 ...
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 ...
This has been discussed several times (in the meta of metas), and declined the same amount of times.
Moderators accepting answers on user's behalf after a certain time period
Feature request: moderator ability to accept an answer
So... who exactly do you think sees flags other than moderators?
While it's true that ordinary users can review Very Low Quality and Not-An-Answer flags, for the most part, (including those), they go straight to moderators. That's the whole point. There's already an 'other' option - it merely specifies that it's for 'Moderator Attention' because, y'know, ...
You can't know! If you do manage to work it out though, there could be more secret hats in it for you...
All secret hat secrets will become unsecret after winterbash.
Some secret hats have been desecreted here too.
Looking around, this Meta Stack Exchange answer indicates that this can happen when the review loads, and then the post is deleted. The review UI doesn't know about the deletion, so it doesn't tell you about it, but when you load the Flag Dialog, it contacts the server, which already knows that only the Other option is valid now.
Yeah it seems that support questions are excluded from 'Hot Meta Posts'. I would assume this is the case for bug and feature-request too.
Both badp and Invader Skoodge's posts used support, while Ash's used discussion. Editing Invader Skoodge's announcement to use discussion resulted in the question appearing under Hot Meta Posts after about an hour or so (...