Whilst using the SE Android application last night I noticed I had an upvote on  I wrote a while back. This answer features the ♦ character which is the same character used to distinguish moderators. Rather than treating this as a regular ♦ character, it gives it the same larger, orange style that the moderator diamonds have, both in text and within a code block:      This affects the listing screen as well as question titles:
124118
Related:   I noticed that the mod diamond shows up red. I'm pretty sure it wasn't red not long ago. Has anything changed recently?    I'm on:   Android 6, Nexus 5 Stack Exchange v. 1.0.73     This is also true for the mobile view in Chrome (45.0.2454.94):    But not in Firefox (where it matches the surrounding text, or is black):
55491
It's been more than a month since I have started using . It has these users with user names in the format of "user-random number". I have observed them in some of the stack activities, most of the time asking questions.   Does the moderators create them for their own purpose. If yes what purpose do they serve?   I mean a user is free to have any user name. But it's just a hunch that such users are actually moderators. I may be wrong; just need some clarification.
41156
Starting today, all staff member accounts will have "Staff" next to their name on their user profile.  It looks like this:    For reference, it used to look like this:    We took our cue from the existing design of the "top n% overall" label which we've actually inverted for everyone (not just staff) to stand out from the others. Additionally, we've updated the moderator label from "(moderator)" to an actual label, so it's easier to see and stands out. Staff with diamonds will have both of the indicators.    Clearing up confusion to improve interactions  We've noticed a shared point of friction for users and staff alike - staff often need to post answers on meta sites to explain how a tool or feature works or to respond to bugs. This is a great opportunity for them to interact with the people asking the questions but, sometimes, not having an indicator for every employee makes these interactions more challenging than they already are.  You might say "But what about diamonds, that's used for staff"... and you'd be right, in some cases. The primary purpose of the diamond is to indicate the moderators on a site. These are non-staff users who have extra tools at their disposal and special access to information. While we gave these to staff in the past, we now only grant them to specific types of staff members who need access to these tools - generally community managers and developers.  As such, for the rest of our cohort, we have relied on them mentioning their status in their "about me" sections. This simply isn't a sustainable option both because it's easy to forget but also because it's not actually proof. Anyone can edit their profile to state they're staff.  Adding an indicator like this isn't an original idea. Y'all have been asking for a way to recognize us for years and we're so excited to be able to deliver this change:        Fortunately, we already indicate staff status at the account level, so we can use that information to add a marker to staff profile pages that anyone can see. So this update makes most of these requests !  We'll still encourage our staff to be more specific about their job title in their "about me" but this marker will let y'all quickly and easily know if the person supporting a feature or answering a bug report is staff.  I'm really excited about this change and I hope it helps smooth out interactions across the network a bit. Questions? Ask them in the answers.
28846
Currently, SE employees are given diamonds wherever they need them. I agree with  on this to some degree, employees shouldn't be treated any different.  But... on meta, employees are different. They have the power to dole out official responses, and thus we should be able to differentiate between an employee and a normal user. Currently, only some employees have a diamond on MSO (see , ). This makes it confusing, especially when you see official-sounding posts like .  Now, giving diamonds to all employees on meta may not be the best solution to this. I don't think all employees want their precious inboxes spammed with all the suspensions that are doled out on meta, and other mod stuff. They won't really need the diamond powers either (though it wouldn't hurt).  So, I propose this:  Similar to how moderators have "Moderator" clearly on their profile    display "employee" on an employee's profile, along with the diamond if they have one. At least on meta.    It would imho be even better to display it on their usercards in some form, but that has already been shot down.  It would be even even better if non-MSO mods had greyed out diamonds, similar to , but that's just me wanting more shiny stuff ;-)
52740
There are users listed under the "Users" tab. How do I know who the moderators are? Is there any specific thing to look for on a user, I mean a icon or some other sign? How do I contact a moderator? Is the a way other than using "flag" link?
109096
.  A diamond moderator rolled back a question to a state where it had .  This effectively recreated the tag, despite it being blacklisted.  This should not happen, and is .
61154
I use Stack Exchange site through my phone (iPhone) way more frequently than I do through the desktop website. When I do that, I really wish that typing the @ symbol would offer the same auto-completion of names that it triggers on the desktop site.  Is anyone working on getting that feature working? If not, I'd like to ask that you prioritize it.
53529
Private beta  shows **private beta** instead of making the text bold. Based on this question the  on the login page (however 4 years ago it was shown in italics).
74524
Is it possible to get a combined flair like the ones on Area 51?  See follower list on the right side of an  for examples.
98689
RECENTLY ON THE ANDROID SITE WE GOT  WRITTEN IN ALL CAPS.  THIS WAS SURPRISING TO ME, SINCE I ASSUMED IT WOULD HAVE BEEN CAUGHT BY THE QUALITY FILTER &mdash; BESIDES BEING INDICATIVE OF OTHER POST QUALITY ISSUES, IT'S AWFUL TO LOOK AT AND REQUIRES A LARGE AMOUNT OF EDITING TO FIX (EVEN IF YOU RUN IT THROUGH TOLOWER() FIRST).  WE ALL KNOW THAT CAPS LOCK IS , BUT STILL: CAN WE BLOCK THESE QUESTIONS?    RICK  RICK  OH MAN THAT STUFF JACOB G  IS COMEDY GOLD  RIIICK     Note to editors: This post looks exactly like it is supposed to look, as an example of a question in all-caps. Please do not replace the uppercase letters with lowercase.
75288
A question from  popped up in the "Hot Network Questions" list, and I couldn't help but notice that its icon is a little bit... lacking.        Shouldn't there be some letters there or something? Maybe "Ec"? Both the main site and the meta are equally nondescript.             As pointed out by  in the comments, this is a high-DPI specific issue.     This is another one of those "shows up on normal DPI, but breaks on high DPI" bugs because  is missing the Ec, but  is not.
69754
Update  Sorry for the delay! I’ve been thinking about this feedback in between my other projects, and I’ve landed where I’ve started 😕  I’ve made sure to continue highlighting spoilers in gray. The differentiation from normal blockquotes is super important since their behavior is so different. I explored keeping spoilers yellow, but that still has the same theming issues throughout the network. Red seemed too powerful, with its error connotations.  I understand completely that folks are using blockquotes to highlight images. However, I don’t think that’s a  we want to formally pave. I’m ok with being opinionated here—blockquotes should be used for quoting, not as a way to highlight images. I understand that this will be frustrating to Machavity who made excellent points about differentiation in his answer, but I don’t think image highlighting ought to dictate how blockquotes are styled.  I’m also cautious of adding borders to images as explored by user1306322 for the same reasons and for the additional fear of being too prescriptive in how we display images there.  It’s a tough one! I went back and forth with the design team and I still think this is the best path forward.  Original post  We’re making a few changes to blockquotes soon. Historically, we had a bit of feedback that the yellow backgrounds were overpowering, reducing the contrast of the quote itself. The yellow border also lacks contrast with the background. Others have indicated that there should be  and between .  These yellows also compete with theming in our communities, especially those with backgrounds that aren’t perfectly white like English Language &amp; Usage and Role-Playing Games.   We’re proposing we switch to a single gray bar in our blockquotes. This should fix those theming issues and make it easier to distinguish between quotes, spoilers and code.  This will also improve blockquote nesting, since our current nesting is a mess because the darker yellow bar is barely noticeable on the paler yellow background.  Spoilers should pretty much behave exactly the same way. More room for later improvements there.  Here’s how our current blockquotes look. You can click to expand:    Here’s what we propose:    There is a lot of prior art out there for this approach. GitHub has styled theirs this way for a long time. So has Slack.     Let me know what y’all think. I think these changes will be an improvement, and I hope you do too.  Huge thanks to Catija for gathering some meta posts on blockquotes and creating an awesome blockquote playground post for testing.
6773
Some people have a diamond after their username (e.g. )    What special privileges do diamond moderators have? How can I become a diamond moderator? Who are the diamond moderators?  How many are there?      For more information, see  in the .     Note: not to confuse with certain Stack Exchange employees, for example  members or "community managers", who often have diamonds as well, but are not ordinary moderators.
4831
I added a comment to  but something strange is happening. The end code reads "); but SO decided to change that to ";);.    I did not add a ; in front of the ).  To further explain what's happening here, the following:  "http://example.com/." http://example.com/. "http://example.com." http://example.com. "http://example.com" http://example.com   renders as:
31273
Switching mode for how the questions with ignored tags will be handled has weird visual behavior (blue circle size is too large) on localized sites, e.g. :        Seems this is happens due to the existence of the second line of option description.  Here is on MSE it looks valid:
109819
Over on , I have just tried to create a tag synonym of  for &dagger; since there seems to be some confusion as to which to use, and people end up adding both.  &dagger; Although looking at the tag synonyms of  here, I should probably have done it the other way around.  Instead of just creating the synonym as I expected, it showed me  (which obviously I couldn't vote on myself) as if I were not a moderator. I guess I should have noticed that the button said "Suggest" rather than "Create", but elsewhere on the site, diamond moderator 'suggestions' are rather more binding. *8')  It was then suggested that I needed to do this via the moderation tools, so I had a hunt around and managed to find the moderator tool for tag synonyms and approve my own synonym from there. I now see however that just clicking on the  link would have taken me there anyway.  It seems odd that we can't just create the tag synonym directly from the tag synonym page, and the suggestion mechanism breaks the expectation of moderator suggestions being immediately binding (like flags), so it would be nice if this behaviour could be made more consistent.   Incidentally, I fully expect this to be , and rightly so since it only saves one click, but at least this post will serve as a searchable answer for future diamond moderators who are confused about this. *8')
58988
According to , using §1 in an item's name should make the text colored dark blue.  However, when I copy-paste a command like this one into chat:  /give @p diamond_sword{display:{Name:"{\"text\":\"§1Sword\"}"}}   it comes out like this:  /give @p diamond_sword{display:{Name:"{\"text\":\"1Sword\"}"}}   See the problem? I can't copy § into chat!  Which means the name ends up being "1Sword" rather than "Sword" colored dark blue.  Why can't I copy § into chat? What can I do to fix it?  Note: I've tested this issue on Minecraft versions 1.14.3 and 1.12.2. It worked the same on both. Feel free to leave a comment if you need more details.