This is not documented in an easy-to-find way, but a site must have at least 40 tags with 200+ questions in it before any Generalist badges are awarded. Since this site has only 27 tags with 200+ questions, the Generalist badge is not yet earnable.
Who can answer a protected question?
Users with 10 or more reputation can answer a protected question.
However, the +100 account association bonus is ignored for this check,
so you must have earned 10 or more reputation on that specific site to
answer a protected question.
So there isn't actually any bug here, and it takes some explanation of how the review queues work to get to why it's not a bug.
The review page is not a good indicator of whether your suggested edit is still pending.
The number of tasks displayed there is a live count of how many you, personally can review. That count does not include anything you own or ...
I had pointed this out 7 months ago when we were asked for feedback on the design. Refer to my earlier answer, which had 13 up-votes. Quote:
3. I suggest making the "Ask Question" link more prominent. I see the underline on close inspection, but even so, the link doesn't stand out
as much as it ought to, perhaps owing to the all-caps used for all the
After some help from StackExchange staff, it looks like you hit some variant of this bug:
Receiving incorrect WebSocket message "this post is locked - no more edits are allowed" when editing a post on which comments are disabled
The post was deliberately:
Comment locked - as the question had got lots of comments that were basically answers or ...
No problem here. Try another browser. Then flush the cache. Then try a third one.
On a lighter note -
On meta, the system considers you a new contributor, and reminded me to be nice. I hope I was sufficiently pleasant.
This is working as intended, for now. Officially, we do not fully support https access yet, and none of our certificates are valid for meta sites. You can get a full explanation of that by Adam Lear on our main meta:
... you can't have a wildcard in the middle of a cert, so meta.*.stackexchange.com could never be a thing and we're not about to start ...
Edit 7/18/2015: I think this is now complete with the changes announced here. It looks much better to me!
Edit 3/3/2015: I've asked about this issue on meta.SE.
This still hasn't been addressed, even though I've asked a duplicate question about it. And it's not just in the comments, but in the questions and answers that visited links are very difficult to ...
We don't run evaluations on graduated sites, and it looks like you guys happened to graduated while an evaluation was running... which threw a wrench into the checks the queue runs to determine if it should close down.
I added a developer-only route to force-close evaluations if necessary, so this is all cleaned up now. Thanks for the report!
Agreed this seems to be a bug [edit: I was wrong :-)]. The admin page for the review also shows it as having been put in the queue, not removed from the queue, and only having 1 review. The reviewer wasn't a moderator. I'll see if any S.E. staff want to take a look, though I'm not sure how high a priority it would be.
This should be fixed now that the site evaluation queue has been turned off.
You might still see counts in the top bar that are "off" since we show the total number of reviews there, not just the number available to you personally, but at least it won't be stuck on the same 10 anymore. :)