I've changed this phrasing on the /help/privileges/moderator-tools page from "elected community moderators" to "site moderators", and added a link to the "Who are the site moderators, and what is their role here?" help center page (/help/site-moderators).
Be annoyed no more. :)
I've fixed the issues you pointed out with those first two help center pages (/help/duplicates and /help/reopen-questions) network-wide.
I've also made substantial updates to the former (the duplicates help page) to correct other inaccuracies and bring it up to date. Please take a look at the updated help center article to make sure it's accurate.
As for ...
I've updated the close reason descriptions on the /help/closed-questions help center page network-wide to match those in the "Close" dialog.
I've also updated the names listed in that help center article for 2 of the listed closed reasons to match those in the "Close" dialog. Specifically, I've changed the "Duplicate of..." ...
Thank you for reporting this issue! I just deployed an update.
The message displayed when the author of a post approves a suggested edit has been changed to:
Thanks for reviewing the suggested edit - the changes (if any) are now live. [Click here] to return to the post.
Also, the message displayed when the author of a post returns to the review page for a ...
Sorry about that, should be all fixed now.
We were trying out a new way to deploy the code for stackexchange.com to production. Due to an oversight on my end, plus really unfortunate timing, that deployment picked up a bad commit from the master branch (which just slipped through our test automation - another freak coincidence).
We're putting a few ...
So my suggestion: If a message is deleted as rude/abusive in chat, any inbox notifications coming from its mentions should be deleted too.
The change went live earlier this month. If you see any issues, please let us know.
Unfortunately, I made a typo in the reported amounts on the blog post. Thanks for catching that! The mistake was with UNICEF which originally had $6,160 reported. The actual donated amount however, was $6,166, which has been verified with our finance team. This amount has been corrected on the blog post as well.
As noted in Sonic's answer, the /help/closed-questions page of the help center (titled "What does it mean if a question is "closed"?") has this line at the end of the article:
For more about reopening questions, see "What if I disagree with the closure of a question? How can I reopen a closed question?"
This text links to the /...
This was closed as similar to this related bug fix in our review queue workflows mega-thread.
However, there were multiple root issues causing the empty blue box. In this case, when you hit the daily up/down vote limit - we restrict reviewing First Answers, because one of the possible ways to handle a review is to upvote the post in question.
Should be all ...
First of all: thanks a lot to everybody for notifying us about this issue. We have been able to reproduce and fix it. Please do let us know (in a comment to this answer) if you're still encountering any issues with this.
This feature has been implemented since October 2016 for comments edited after October 2012. Moderators can click the pencil icon on the edited comment to see its comment history.
As of January 2022, it looks like this (moderator's name is manually redacted on here)
This is a CSS reset issue that is deploying now. For historical reasons, we allow for Stacks to be configurable with 2 different CSS resets. Our testing environment had one. Production had the other. How fun!
We're exploring not having any CSS reset in the future, but this is now fixed.
Thank you for the report! This has been fixed sitewide, along with another 21 other "occurrences" of the same misspelling.
Interestingly, this is one of the 100 most common misspellings and not a single person in my house could spell it either.
As I just posted on this report (but copying here for posterity):
This should be fixed now. Audits broke on November 8 on the First Question and First Answer queues when a deliberate switch fall-through in the typescript ... un-fell-through?... and a critical part of the audit code was no longer being correctly referenced. I fixed this in December and fully ...
The syncing of display names between the sites and the WB mini-site doesn't always work. I have manually fixed the final stats for WB2021 (but this could very well happen again next year, since the less-than-perfect sync is a status-declined type issue).
The same issue popped again as I reported here:
Consequence was that Thunderbird was unable to load the feed until the invalid characters slid out of the feed.
The error that popped on this feed is now gone, but here is the error reported by the validator from W3C:
This feed does not validate.
Yes, the hat awards were hung for about 12 hours network-wide. I have run it manually a few times, trying to figure out some timeout issues with it (but limited with how much I can fix over the weekend).