<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Stack Exchange Community Moderator Blog</title>
	<atom:link href="http://moderator.stackexchange.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://moderator.stackexchange.com</link>
	<description>The Community Moderator Stack Exchange Blog</description>
	<lastBuildDate>Thu, 13 Jun 2013 21:01:19 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>May 2013 Newsletter</title>
		<link>http://moderator.stackexchange.com/2013/06/may-2013-newsletter/</link>
		<comments>http://moderator.stackexchange.com/2013/06/may-2013-newsletter/#comments</comments>
		<pubDate>Thu, 13 Jun 2013 21:01:19 +0000</pubDate>
		<dc:creator>Grace Note</dc:creator>
				<category><![CDATA[newsletter]]></category>

		<guid isPermaLink="false">http://moderator.stackexchange.com/?p=203</guid>
		<description><![CDATA[New “Help Center” is Live! We just rolled out the new ‘help’ center linked at the top of your site. The gist of this project is to consolidate the various FAQs, meta posts, and blog posts into a much more comprehensive, educational resource. See Introducing a brand new, consolidated, Help Center. This is an on-going [...]]]></description>
				<content:encoded><![CDATA[<h2><strong><span style="color: #003300;">New “Help Center” is Live!</span></strong></h2>

<p>We just rolled out the new ‘help’ center linked at the top of your site. The gist of this project is to consolidate the various FAQs, meta posts, and blog posts into a much more comprehensive, educational resource. See <a href="http://meta.stackoverflow.com/questions/182812/introducing-a-brand-new-consolidated-help-center">Introducing a brand new, consolidated, Help Center</a>. This is an on-going project, so we’ll be adding many more articles and features addressing your ideas and concerns.
</p>

<p>Please note that the article, “what topics can I ask here?” replaces the old on- and off-topic section of the FAQ — so please be sure yours is up to date. If your site has particular needs not addressed by the Help Center, please discuss your ideas with the community in meta, tagged <strong>[help-center]</strong>.
</p>

<h2><strong><span style="color: #003300;">Changes to the Closing System are Rolling Out</span></strong></h2>

<p>After months of discussion, work, and input from the community, we’ve begun rolling out changes to the close system. These changes are designed to improve the closing experience for both the community and the author of the post. Please read through the <a href="http://meta.stackoverflow.com/questions/184154/closing-changes-on-hold-unclear-too-broad-opinion-based-off-topic-reasons">Closing Changes</a> meta post for more information. The new reasons are being tested on Meta Stack Overflow this week, and we’re aiming to launch them everywhere else early next week.
</p>

<h2><strong><span style="color: #003300;">Suspensions Limited to One Year</span></strong></h2>

<p>We are capping the length of time you can suspend a user to one year. If you are currently using the suspension system to, essentially, lock an account with multi-year suspensions, please simply ‘destroy’ the account instead. We maintain access to account information (IP addresses, email, access logs, etc), even after the account has been destroyed, so there is no need to hold an account hostage just to preserve those records. 
</p>

<p>If you have clear evidence that an account is being used inappropriately (spam, sock puppets, persistent trolls, circumventing suspensions, etc), continue to message or suspend the user as you see fit. If the account is clearly not made in good faith (i.e. promoting discount gucci handbags), feel free to proceed to deleting it. If there’s any doubt, please contact the community team before deleting the account outright.</p>

<h2><strong><span style="color: #003300;">Finding Problem Users in Chat</span></strong></h2>

<p>We’ve added a few simple reports to the chat system, listing users with potential problems like ‘multiple flagged messages’, ‘ignored by multiple people’, and ‘users who have invited multiple people’. 
</p>

<p>These reports are are located in the chat directory:</p>

<ul>
    <li>For Stack Exchange Sites → <a href="http://chat.stackexchange.com/admin/users">http://chat.stackexchange.com/admin/users</a></li>
    <li>For Stack Overflow → <a href="http://chat.stackoverflow.com/admin/users">http://chat.stackoverflow.com/admin/users</a></li>
    <li>For Meta Stack Overflow → <a href="http://chat.meta.stackoverflow.com/admin/users">http://chat.meta.stackoverflow.com/admin/users</a></li>
</ul>

<h2><strong><span style="color: #003300;">Leaving Comments on Deleted Posts</span></strong></h2>

<p>Moderators are now able to leave comments on deleted and locked posts. This will allow you to leave helpful guidance when a post need to be deleted quickly (or has already been deleted). Remember that your comments will appear in a user’s inbox, even after it has been deleted (<a href="http://moderator.stackexchange.com/2011/07/june-newsletter/">July 2011</a>), so please leave a short note when a user’s post disappears unexpectedly!
</p>

<h2><strong><span style="color: #003300;">Swag Changes</span></strong></h2>

<p>With the network getting bigger and the number of moderators growing, we unfortunately have to stop doing customized business cards for moderators on graduated sites. Designing and producing those ended up taking more time than anyone had anticipated. We&#8217;ll still offer and send out business cards to any moderator who wants them, but they&#8217;re going to look a lot more like the cards we have for our employees: <a href="http://i.stack.imgur.com/h3ZKz.png">front</a> <a href="http://i.stack.imgur.com/TJMp2.png">back</a>
</p>

<p>On the upside, we are also introducing a new item to show our appreciation for everything you all do: 
</p>

<p><img src=http://i.stack.imgur.com/JPn7d.jpg /></p>

<p>These will be available exclusively to moderators and employees and should go into production shortly. If you&#8217;d like one, please fill out your information <a href="https://docs.google.com/a/stackoverflow.com/forms/d/1quNyjJaclBBGjixlhXP1rOzYloT_y0MQoBl-_o0qP2Y/viewform">here</a> and we&#8217;ll have them shipped out ASAP once they&#8217;re ready.
</p>
]]></content:encoded>
			<wfw:commentRss>http://moderator.stackexchange.com/2013/06/may-2013-newsletter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>April 2013 Newsletter</title>
		<link>http://moderator.stackexchange.com/2013/05/april-2013-newsletter/</link>
		<comments>http://moderator.stackexchange.com/2013/05/april-2013-newsletter/#comments</comments>
		<pubDate>Fri, 10 May 2013 19:37:26 +0000</pubDate>
		<dc:creator>Grace Note</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://moderator.stackexchange.com/?p=197</guid>
		<description><![CDATA[Deleted Question Visibility We’re happy to announce that going forward, any user can see their own deleted questions if they are given a link. They still cannot access it via the profile page, but any link will suffice. We hope that this new functionality will make guidance for new users a lot easier for mods, [...]]]></description>
				<content:encoded><![CDATA[<h2><strong><span style="color: #003300;">Deleted Question Visibility</span></strong></h2>

<p>We’re happy to announce that going forward, <strong>any user can see their own deleted questions if they are given a link</strong>. They still cannot access it via the profile page, but any link will suffice. We hope that this new functionality will make guidance for new users a lot easier for mods, as well as making the experience as a whole much smoother.
</p>

<p>As a reminder, if a moderator leaves a comment within an hour before deleting a post, this leaves a permanent entry in the post author’s inbox that links to the post. This, combined with the new visibility of deleted questions, allows you to communicate with the users even if you have to remove the post.
</p>

<h2><strong><span style="color: #003300;">Early Deletion Privilege Tweak</span></strong></h2>

<p>We’re introducing a tweak into the existing 20k privilege that allows users to delete closed questions before the first two days pass. Now, in the first two days, <strong>users with 20,000 reputation can only delete a closed question if it has a score of -3 or less</strong>. After the first two days, deletion requirements are the same as always.
</p>

<p>Deletion within the first two days is meant to handle egregious posts and terrible spam. We hope that by altering the privilege in this fashion, it should avoid issues with removing otherwise salvageable posts too quickly and allow time for askers to learn and/or edit their posts.
</p>

<h2><strong><span style="color: #003300;">New Audit Stats Available with Advanced Review Stats</span></strong></h2>

<p>We have added some new statistics for your studying pleasure to the Review Audit Stats <a href="http://moderator.stackexchange.com/2013/04/march-2013-newsletter/">we introduced in last month&#8217;s issue</a>. We have also made the page a lot more accessible with a simpler route than before:
</p>

<p>   <em>From the page top ‘mod’ link → ‘links’ » ‘Advanced review stats’</em></p>

<p>The following new statistics are available on this page in each queue:</p>

<ul>
<li><p><strong>AvgDuration(s)</strong> notes the average time that the user spends on each task in that queue in seconds;</p>
</li>
<li><p><strong>AuditTotal</strong> notes the total number of audit tasks that the user has run into in that particular queue;</p>
</li>
<li><p><strong>AuditPass%</strong> notes what percentage of audit tasks that the user has successfully completed compared to all tasks run into within that particular queue.</p>
</li>
</ul>

<p>We believe these stats will be helpful in identifying or analyzing suspicious or curious activity within the review queues.
</p>

<h2><strong><span style="color: #003300;">A Small Note About Contacting The Community Team</span></strong></h2>

<p>When you send us an email as a moderator, especially through the team@ support address that everyone uses, please be sure to identify that you are a moderator and on which site you are a moderator. This will help us parse the information of the email faster.</p>
]]></content:encoded>
			<wfw:commentRss>http://moderator.stackexchange.com/2013/05/april-2013-newsletter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>March 2013 Newsletter</title>
		<link>http://moderator.stackexchange.com/2013/04/march-2013-newsletter/</link>
		<comments>http://moderator.stackexchange.com/2013/04/march-2013-newsletter/#comments</comments>
		<pubDate>Mon, 01 Apr 2013 21:21:30 +0000</pubDate>
		<dc:creator>Grace Note</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://moderator.stackexchange.com/?p=193</guid>
		<description><![CDATA[Calling for Elections &#8211; Need More Help? Just Ask! In the past, the community team was monitoring sites to determine when they needed more mods in order to maintain good coverage. Recently,we realized that we’re usually not the people most qualified to know when there’s a need. You are! Going forward, the main trigger for [...]]]></description>
				<content:encoded><![CDATA[<h2><strong><span style="color: #003300;">Calling for Elections &#8211; Need More Help? Just Ask!</span></strong></h2>

<p>In the past, the community team was monitoring sites to determine when they needed more mods in order to maintain good coverage.  Recently,we realized that we’re usually not the people most qualified to know when there’s a need. You are!
</p>

<p>Going forward, the main trigger for us to consider holding elections will be the existing mod team telling us they need more help.  As of now, any time you feel that your site is understaffed, either because the workload is increasing or because there aren’t enough active moderators, please get as much team consensus as possible, and then <a href="mailto:community@stackexchange.com">email the Community Team</a> to let us know how many additional mods you think make sense to add.
</p>

<p>After reviewing these requests, we may suggest a different number, or offer to reach out to any less active mods first, etc.   But most of the time, since you’re in the best position to tell us what your team needs, and we’ll work with you to get an election scheduled.
</p>

<h2><strong><span style="color: #003300;">Review Queue &#8211; Advanced Statistics</span></strong></h2>

<p>We have made a more in-depth set of review statistics available to moderators.  Each queue now includes the number of times a reviewer has picked each available action, and what percent of their total actions it represents. This should provide you with a much better overview of how your community is using review, as well as a way to detect those who seem to be reviewing in bad faith and may need to be temporarily blocked (see below).
</p>

<p><em>&nbsp;&nbsp;&nbsp;&nbsp;Go to review via the top navigation bar → Pick any queue » &#8216;stats&#8217; » &#8216;Advanced stats&#8217; in the right sidebar</em></p>

<p>You can change the queue you’re viewing at any time using the dropdown labeled “Queue:”.
</p>

<h2><strong><span style="color: #003300;">Suspending Users from Reviewing</span></strong></h2>

<p>We have implemented a system for <a href="http://meta.stackoverflow.com/questions/158675/why-am-i-getting-the-message-youve-failed-too-many-recent-review-audits">blocking users from using the review queues</a> for 1 to 30 days.
</p>

<p>Most people using Review do so in a helpful manner, but you may encounter a few users who do not. If someone does not appear to be reviewing in good faith (always choosing the same action, regardless of content, repeatedly approving poor edits, etc.) short time-out may be a gentle reminder to slow down and pay attention.
</p>

<p><em>&nbsp;&nbsp;&nbsp;&nbsp;From the page top &#8216;mod&#8217; link → &#8216;links&#8217; » &#8216;Review bans&#8217; » Enter user ID or URL</em></p>

<p>This page also includes a list of user who are currently banned, either by a moderator or due to failing audits. This functionality is available regardless of whether your site has audits enabled.
</p>

<h2><strong><span style="color: #003300;">New Unicode Tag System</span></strong></h2>

<p>Full Unicode support for tags now available and can be turned on for sites that need it. If you think your site would benefit from it, make a meta post, including examples of how it would be beneficial, gather community support, and  propose a plan for how you’d use these tags either alongside or instead of &#8220;normal&#8221; tags. The more information you can provide, the more easily we can implement your request. Once you have all of the information gathered, <a href="mailto:community@stackexchange.com">email the Community Team</a>, and we’ll be happy to review the thread.</p>

<h2><strong><span style="color: #003300;">How to Contact Users</span></strong></h2>

<p>This is mostly a reminder. It is rare that a moderator should need to directly email a user at their email address, especially with regards to normal moderator duties. Most of your private contact needs should be done through moderator messages – it’s both less intrusive to the user and also automatically informs the rest of the moderators and the Community Team that something is happening. If you find yourself needing to email a user for moderator reasons but not using a moderator message, make sure to also BCC the rest of your team, and the Community Team, on every exchange so that everyone is on the same page. </p>
]]></content:encoded>
			<wfw:commentRss>http://moderator.stackexchange.com/2013/04/march-2013-newsletter/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>February 2013 Newsletter</title>
		<link>http://moderator.stackexchange.com/2013/03/february-2013-newsletter/</link>
		<comments>http://moderator.stackexchange.com/2013/03/february-2013-newsletter/#comments</comments>
		<pubDate>Mon, 11 Mar 2013 19:57:05 +0000</pubDate>
		<dc:creator>Grace Note</dc:creator>
				<category><![CDATA[newsletter]]></category>

		<guid isPermaLink="false">http://moderator.stackexchange.com/?p=183</guid>
		<description><![CDATA[Always Leave a Paper Trail It is sometimes necessary for a moderator to take unilateral action without community process or review. Whenever possible, it is extremely helpful to leave artifacts about what happened. Comments can be left, even on deleted posts, to be a public-facing notice of the action. Flags can be used when deleting [...]]]></description>
				<content:encoded><![CDATA[<h2><strong><span style="color: #003300;">Always Leave a Paper Trail</span></strong></h2>

<p>It is sometimes necessary for a moderator to take unilateral action without community process or review. Whenever possible, it is extremely helpful to leave artifacts about what happened. Comments can be left, even on deleted posts, to be a public-facing notice of the action. Flags can be used when deleting troublesome comments to separate from simple cleanup. A strange run-in with a user or concerns about a user&#8217;s recent activity, can be annotated on their profiles.</p>

<p>These artifacts will help your fellow moderators, the Community Team, or even regular users of the site to understand why actions were taken. It can help not only for their own information seeking benefit, but also as an easy way for yourself to remember why you may have taken an action.</p>

<h2><strong><span style="color: #003300;">User Merge Clarifications and Process</span></strong></h2>

<p>In last month’s issue, we announced a major policy change regarding how user merges are handled – namely that they are to be sent to the Community Team. The removal of moderator access to the tool has been completed.</p>

<p>To speed up the process, moderators may use the same form that a user uses in order to submit a merge request on their behalf. It remains a part of our quick help center available at the bottom of every page.</p>

<p><em>&nbsp;&nbsp;&nbsp;&nbsp;From any page footer → ‘contact us’ » ‘Merge user profiles’</em></p>

<p>In order to prevent confusion, please enter your own email address and not the email address of the user that requires merging when submitting the form.</p>

<h2><strong><span style="color: #003300;">Audits in Review Tasks</span></strong></h2>

<p>Audits have been inserted into the review tasks as a means for catching users who try to skim past the review tasks unscrupulously. At the moment, this is only enabled for Stack Overflow, Super User, Server Fault, and Programmers. On those sites you may observe progress on how users are faring on the audits in your mod tools as follows:</p>

<p><em>&nbsp;&nbsp;&nbsp;&nbsp;From the page top ‘mod’ link → ‘links’ » ‘Review Audits’</em></p>

<p><em>&nbsp;&nbsp;&nbsp;&nbsp;Follow updates on the development on Meta Stack Overflow → <a href="http://meta.stackoverflow.com/questions/tagged/review-audits">review-audits tag</a></em></p>

<p>We’re constantly working out the kinks as new reports come in about the process. As we smooth things out, this will eventually be able to be deployed across more sites in the network.</b></p>
]]></content:encoded>
			<wfw:commentRss>http://moderator.stackexchange.com/2013/03/february-2013-newsletter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>January 2013 Newsletter</title>
		<link>http://moderator.stackexchange.com/2013/02/january-2013-newsletter/</link>
		<comments>http://moderator.stackexchange.com/2013/02/january-2013-newsletter/#comments</comments>
		<pubDate>Fri, 01 Feb 2013 19:57:21 +0000</pubDate>
		<dc:creator>Grace Note</dc:creator>
				<category><![CDATA[newsletter]]></category>

		<guid isPermaLink="false">http://moderator.stackexchange.com/?p=153</guid>
		<description><![CDATA[Brand New About Page — a Quick Start to the Network We’re rolling out a massively revamped ‘about’ page for each site, designed to help introduce new users to Stack Exchange. It replaced the original about page on all non-Meta sites. Your feedback is appreciated. We also have some guidelines to keep in mind when [...]]]></description>
				<content:encoded><![CDATA[<h2><strong><span style="color: #003300;">Brand New About Page — a Quick Start to the Network</span></strong></h2>

<p>We’re rolling out a massively revamped ‘about’ page for each site, designed to help introduce new users to Stack Exchange. It replaced the original about page on all non-Meta sites. Your feedback is appreciated. We also have some guidelines to keep in mind when making changes to /about.</p>

<p><em>    Learn more → <a href="http://meta.stackoverflow.com/q/163254/98786">“Quick Start” guide to help new users learn the basics</a></em></p>

<p><em>    See the /about guidelines → <a href="http://meta.stackoverflow.com/questions/164778/what-should-we-put-on-our-about-page">What should we put in our about page?</a></em></p>

<h2><strong><span style="color: #003300;">User Merge Guideline Changes</span></strong></h2>

<p>We are changing our guidelines with respect to how users are merged. From now on, users who request to have accounts merged (accidental duplicate accounts, unregistered user replicants, people who lose access to their original account) should all be directed to the appropriate user merge Help section on your site.</p>

<p><em>    From any page footer → &#8216;contact us&#8217; » &#8217;Merge user profiles&#8217;</em></p>

<p>On the topic of sockpuppetry for voting or other unacceptable behavior, please do not merge these accounts on your own. Please review such cases with the community team by sending us word at <a href="mailto:community@stackexchange.com">community@stackexchange.com</a>.</p>

<h2 dir="ltr">New Moderator Message for Targeted Voting</h2>

<p>A new ‘contact user privately’ template has been added.</p>

<p><em>    From the user profile → &#8216;mod&#8217; » &#8217;contact user privately&#8217; » &#8217;select message template&#8217; » &#8221;targeted votes&#8221;</em></p>

<p>This is designed for handling users who may not have sockpuppets, per se, but are engaged in sketchy voting practices with friends or associates.</p>

<h2><strong><span style="color: #003300;">Analyzing Review Tasks on Posts</span></strong></h2>

<p>Moderators have a new tool to list the review tasks performed on a post. Similar to observing flag history, posts now have a review history that can be studied. It’s available from any post that has had /review actions.<b><b></b></b></p>

<p><em>    From any post → &#8216;mod&#8217; » &#8217;show review history&#8217;</em></p>

<p><em>    Learn more → <a href="http://meta.stackoverflow.com/q/160751/98786">Add moderator-visible review task links to posts that are enqueued</a></em></p>

<h2><strong><span style="color: #003300;">Votes Analysis Tool Update</span></strong></h2>

<p>We have improved the voting analysis tool used to examine voting trends from one user against others, especially on the end of invalidated votes.</p>

<p><em>    From the user profile → &#8216;mod&#8217; » &#8216;info&#8217; tab » &#8217;votes&#8217;</em></p>

<p>Separate instances of vote invalidation is shown as separate events. The date of each incident is also displayed. Additionally, we now display invalidations both incoming and outgoing on the user.</p>

<h2><strong><span style="color: #003300;">System messages are now unavailable</span></strong></h2>

<p>System messages (a bit of text displayed near the top of every page on the site) have always been intended for system-critical notifications &#8211; the site going into read-only mode for maintenance, zombie hordes attacking, etc. However, they were often used for rather more mundane events.</p>

<p>Some time ago, we added a <a href="http://meta.stackoverflow.com/questions/130892/nailing-it-up-on-your-community-bulletin-board">Community Bulletin Board </a>tool for non-critical announcements of general interest to the community. Now that it’s been out in the wild for a bit, we’ve removed moderator access to the system message tool.</p>
]]></content:encoded>
			<wfw:commentRss>http://moderator.stackexchange.com/2013/02/january-2013-newsletter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Summer and Fall 2012 Omnibus Newsletter</title>
		<link>http://moderator.stackexchange.com/2012/12/summer-and-fall-2012-omnibus-newsletter/</link>
		<comments>http://moderator.stackexchange.com/2012/12/summer-and-fall-2012-omnibus-newsletter/#comments</comments>
		<pubDate>Tue, 18 Dec 2012 20:25:57 +0000</pubDate>
		<dc:creator>Grace Note</dc:creator>
				<category><![CDATA[newsletter]]></category>

		<guid isPermaLink="false">http://moderator.stackexchange.com/?p=145</guid>
		<description><![CDATA[New /help System We always provide an avenue for users of our sites to contact us. Using information gathered from the volume of emails we received, we developed a new “help” page dedicated to answering a lot of the most common support questions. It can be found from the “contact us” link at the bottom [...]]]></description>
				<content:encoded><![CDATA[<h2><strong><span style="color: #003300;">New /help System</span></strong></h2>

<p>We always provide an avenue for users of our sites to contact us. Using information gathered from the volume of emails we received, we developed a new “help” page dedicated to answering a lot of the most common support questions. It can be found from the “contact us” link at the bottom of every page, and you can see Stack Overflow’s version here.</p>

<p><a href="http://stackoverflow.com/help">http://stackoverflow.com/help</a></p>

<p>This may have been developed primarily to assist users who are heading to ask the team questions, but we hope it can still be helpful to our moderation team. The many links contained within, and the guides written for them, should be usable for meta, chat, and comment inquiries from new users who run into these issues.</p>

<div>
<h2 dir="ltr"><strong><span style="color: #003300;">Changes to Migration</span></strong></h2>
After many discussions regarding the complications that arise from migrating old and highly voted questions from the larger sites over to smaller sites, we have implemented some new regulations and systems regarding migration.

First, <a href="http://meta.stackoverflow.com/questions/151890/disable-migration-for-questions-older-than-60-days">migrations are no longer permitted for questions older than 60 days</a>. This is a simple block that prevents the migration from happening, even from moderators.

Should it be important to move older posts, there is <a href="http://meta.stackoverflow.com/questions/152597/how-to-migrate-old-questions-to-a-new-graduated-site">an alternative method for performing these</a>. It’s a three step process. First, the destination site will build a listing of questions which would be acceptable to migrate. Then, the source and destination communities will confer together and help confirm which posts are valid to move over, by vetting the losses. Finally, once the two communities have come to a consensus, the list can be brought before the Stack Exchange Team to perform a one-time migration of all the posts.

</div>

<div>
<h2 dir="ltr"><strong><span style="color: #003300;">New Under-Age User Policy</span></strong></h2>
We have amended the process for handling users who are found to be less than 13 years of age. Suspension until they reach the required age is no longer a valid option as it still leaves potentially sensitive information online.

Therefore, the new policy is to please send any discovery of such individuals to the Community Team. We will handle the disposal of the user’s private and identification data. You can reach us through <a href="mailto:community@stackexchange.com">community@stackoverflow.com</a>.

</div>

<div>
<h2 dir="ltr"><strong><span style="color: #003300;">Plagiarism</span></strong></h2>
We have added a new template to the selection of pre-written moderator messages that you can work from when sending a message to a user. This message is for handling users who are plagiarizing their posts from other sources, be it in our network or completely external. Below is an excerpt from it.

</div>

<div>
<blockquote>
<p dir="ltr">It has come to my attention that several of your answers consisted primarily or entirely of text copied from other answers or websites, without any indication that you were quoting nor any reference to the source of the text. Such <a href="http://en.wikipedia.org/wiki/Plagiarism" target="_blank">plagiarism</a> disrespects those authors who put effort into the original answers, and will not be tolerated.</p>
</blockquote>
<div>Please remember that plagiarism and copyright are two separate things. We do not place the duty of seeking and enforcing copyright on moderators.</div>
<h2><strong><span style="color: #003300;">Enhancements to /review System</span></strong></h2>
As announced much earlier in the year, we implemented a /review system to help reduce the load on moderators. It is aimed at streamlining the access of normal users to the elements that need their privileges (namely, editing and closing). Two new features have been introduced in the past months.

First, there is what we call “audit” tasks. These are items in the review queue that are not actual items from the site, but rather tests to confirm that users are actually paying attention. Their job is to catch users who would blow through the queue without proper review. Information on failed audits is logged (and the reviewer chided) &#8211; repeated failures may result in users being blocked from /review for some period of time (we’re currently sending warnings and imposing blocks manually).

Second, the <a href="http://meta.stackoverflow.com/questions/140893/add-a-review-posts-with-reopen-votes-review-task">much-requested</a> “reopen queue” has been introduced. The sister component to the close queue, this queue contains questions that have votes to reopen them. Reviewers may elect to further vote for reopening, or to opine that the question should stay closed (one moderator “leave closed” response &#8211; or three such responses from ordinary users &#8211; will remove the post from the queue).

</div>

<div>
<h2><strong><span style="color: #003300;">Private Email Contact</span></strong></h2>
This is just a small reminder of our policies regarding email contact. Contacting a user by private email should be exceedingly rare. Whenever it is at all possible, please use the following from a user&#8217;s profile page.

&gt; &#8216;mod&#8217; &gt; &#8216;contact user&#8217;

This provides full disclosure and visibility to the other moderators (and the Community Team), as well as keeps records on the site and linked to the user for easy reference.

If you absolutely MUST contact users via private email, please BCC the Community Team and the rest of the moderators.

And please note that use of email addresses for personal use (i.e. outside strict issues of moderation) is against our privacy policy. If you have need to contact users outside these conditions, please contact us for clarification.

</div>
]]></content:encoded>
			<wfw:commentRss>http://moderator.stackexchange.com/2012/12/summer-and-fall-2012-omnibus-newsletter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>May/June 2012 Newsletter</title>
		<link>http://moderator.stackexchange.com/2012/07/mayjune-2012-newsletter/</link>
		<comments>http://moderator.stackexchange.com/2012/07/mayjune-2012-newsletter/#comments</comments>
		<pubDate>Sun, 08 Jul 2012 19:01:50 +0000</pubDate>
		<dc:creator>Robert Cartaino</dc:creator>
				<category><![CDATA[newsletter]]></category>

		<guid isPermaLink="false">http://moderator.stackexchange.com/?p=134</guid>
		<description><![CDATA[Wow, Moderator FAQs and Cheat Sheets We have never published a &#8220;Moderator Manual&#8221; for Stack Exchange. Learning the ins and outs of moderation is largely done &#8220;on the job.&#8221; But our intrepid Moderator community has stepped up and produced some fantastic compilations that should be part of every moderator toolbox: Stack Exchange Moderator FAQ Moderator [...]]]></description>
				<content:encoded><![CDATA[<h2>Wow, Moderator FAQs and Cheat Sheets</h2>

<p>We have never published a &#8220;Moderator Manual&#8221; for Stack Exchange. Learning the ins and outs of moderation is largely done &#8220;on the job.&#8221; But our intrepid Moderator community has stepped up and produced some fantastic compilations that should be part of every moderator toolbox:</p>

<p style="padding-left: 30px;"><strong><a href="http://meta.stackoverflow.com/questions/118972/stack-exchange-moderator-faq">Stack Exchange Moderator FAQ</a></strong></p>

<p style="padding-left: 30px;"><a href="http://meta.stackoverflow.com/questions/119111/moderator-cheat-sheet"><strong>Moderator Cheat Sheet</strong></a></p>

<p>These posts include many common issues raised by Moderators in the Teachers&#8217; Lounge. Give these a once-over and bookmark them for later; you&#8217;ll no doubt find them useful.</p>

<h2>Community Bulletin Board</h2>

<p>We&#8217;ve discouraged the use of system-message banners for general announcements and non-critical events. As the <a href="http://en.wikipedia.org/wiki/Emergency_broadcast_system">Emergency Broadcast System</a> for your site, it must remain clear under normal circumstances. But long last, we have a feature <em>explicitly</em> designed for you to post announcements, events, site news and such:</p>

<p style="padding-left: 30px;"><strong><a href="http://meta.stackoverflow.com/questions/130892/nailing-it-up-on-your-community-bulletin-board">Nailing it upon your Community Bulletin Board</a></strong></p>

<p>The Community Bulletin Board is a place for you to post scheduled events, featured meta posts, or to simply highlight anything of interest to your community. The basic guidelines for using this are:</p>

<ul>
    <li>Items should generally involve the scope of your site.</li>
    <li>Descriptions (separate from titles for scheduled events) should be short but descriptive.</li>
    <li>Add your scheduled events far enough ahead of time to allow folks to make time for them.</li>
</ul>

<p>Also, please remember to remove the [featured] tags from posts once they are no longer relevant. This happens automatically if you wait long enough, but let&#8217;s try to keep the &#8216;featured&#8217; posts both relevant and timely.</p>

<h2>View Deleted Comments</h2>

<p>You can now display all the comments left by a specific user in one listing, including those comments which have been deleted.</p>

<p>To view a user&#8217;s comments, navigate to their profile and click the &#8216;mod&#8217; link. Select the &#8216;info&#8217; tab and click &#8216;comments&#8217;.</p>

<p>Using the tabs across the top, you can view &#8216;active&#8217;, &#8216;deleted&#8217;, or &#8216;all&#8217; comments. This is a useful feature when you are looking into the general behavior of a user, or investigating a reported pattern of abuse.</p>

<h2>A More-Readable Privacy Policy</h2>

<p>Have you seen our reformatted, easier-to-read Privacy Policy?</p>

<p style="padding-left: 30px;"><a href="http://stackexchange.com/legal/privacy-policy"><strong>Stack Exchange Inc. Official Privacy Policy</strong></a></p>

<p>While updating the Safe Harbor/EU privacy requirements, we went ahead and included a much-welcomed <em>&#8220;English for the rest of us&#8221;</em> description for each section. These headings make it easier to find what you need when privacy issues come up.</p>
]]></content:encoded>
			<wfw:commentRss>http://moderator.stackexchange.com/2012/07/mayjune-2012-newsletter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>April 2012 Newsletter</title>
		<link>http://moderator.stackexchange.com/2012/04/april-newsletter-2/</link>
		<comments>http://moderator.stackexchange.com/2012/04/april-newsletter-2/#comments</comments>
		<pubDate>Sun, 15 Apr 2012 19:07:56 +0000</pubDate>
		<dc:creator>Robert Cartaino</dc:creator>
				<category><![CDATA[newsletter]]></category>

		<guid isPermaLink="false">http://moderator.stackexchange.com/?p=127</guid>
		<description><![CDATA[On Cross Posting, Migrations, and Scope Gerrymandering Finally, a blog post that tackles some of problems faced by sites with overlapping domains. This is a good read with some notable policies for dealing with this issue. It&#8217;s worth familiarizing yourself with, particularly for younger sites. Have a look. Respect the community – your own, and [...]]]></description>
				<content:encoded><![CDATA[<h2>On Cross Posting, Migrations, and Scope Gerrymandering</h2>

<p>Finally, a blog post that tackles some of problems faced by sites with overlapping domains. This is a good read with some notable policies for dealing with this issue. It&#8217;s worth familiarizing yourself with, particularly for younger sites. Have a look.</p>

<p style="padding-left: 30px;"><strong><a href="http://blog.stackoverflow.com/2012/03/respect-the-community-your-own-and-others/">Respect the community – your own, and others’</a></strong></p>

<h2>Your Role in Copyright Enforcement</h2>

<p>What do you do when someone claims an answer was copied illegally, or maybe a teacher is claiming that a student is posting test questions on your site? Here in the States, the Digital Millennium Copyright Act (<a href="http://en.wikipedia.org/wiki/Digital_Millennium_Copyright_Act">DMCA</a>) tells us very specifically how to handle claims of copyright infringement.</p>

<p><strong>Your role in enforcement</strong> — As moderators, you are not employees of Stack Exchange. In essence, you are free to moderate the site for content how you see fit. If you are ever notified about copyrighted material, and feel like taking it down, that&#8217;s cool&#8230; <strong>but you are not required to do so.</strong> You are not DMCA agents (we have those of our own). If you get a request for takedown, you can either remove the post <strong>OR</strong> point the person to the Copyright Policy linked below.</p>

<p>Here at Stack Exchange central, we have to be concerned about claims of copyright infringement that may not be valid. If WE (Stack Exchange Inc.) get notices to take down offending content, the claimants need to follow DMCA procedure and contact us with the correct form. It&#8217;s all outlined in the Terms Of Service:</p>

<h3 style="padding-left: 30px;"><a href="http://stackexchange.com/legal/terms-of-service"><strong>Stack Exchange Network Terms of Service</strong></a></h3>

<h3 style="padding-left: 30px;">&#8220;Reporting Copyright Infringements&#8221;</h3>

<p>Our TOS covers all the relevant info about DMCA.The claimants will have to contact us with the necessary forms and information. That makes the issue pretty simple and straightforward on your end. Delete or reply with link.</p>
]]></content:encoded>
			<wfw:commentRss>http://moderator.stackexchange.com/2012/04/april-newsletter-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>March 2012 Newsletter</title>
		<link>http://moderator.stackexchange.com/2012/03/march-newsletter/</link>
		<comments>http://moderator.stackexchange.com/2012/03/march-newsletter/#comments</comments>
		<pubDate>Tue, 20 Mar 2012 19:07:19 +0000</pubDate>
		<dc:creator>Robert Cartaino</dc:creator>
				<category><![CDATA[newsletter]]></category>

		<guid isPermaLink="false">http://moderator.stackexchange.com/?p=122</guid>
		<description><![CDATA[New Voting Fraud Detection Tools The primary way to gain reputation is by posting good questions and useful answers. But with any competitive system, there will always be a few people who try to cheat (Vote Fraud and You). We take this very seriously, and provide some serious tools for detecting and dealing with voting [...]]]></description>
				<content:encoded><![CDATA[<h2>New Voting Fraud Detection Tools</h2>

<p>The primary way to gain reputation is by posting good questions and useful answers. But with any competitive system, there will always be a few people who try to cheat (<a href="http://blog.stackoverflow.com/2008/12/vote-fraud-and-you/" target="_blank">Vote Fraud and You</a>). We take this very seriously, and provide some serious tools for detecting and dealing with voting fraud. This tool set got a recent upgrade:</p>

<p style="padding-left: 30px;"><code>'mod' &gt; 'links' &gt; 'Suspicious vote patterns'</code></p>

<p>If there is suspicious voting activity (an unusual number of votes shared between accounts), the links found in this list will provide some nice visualization tools to see where shared activity might be occurring.</p>

<p><strong>A note of caution</strong> — Not everything listed here is necessarily bad. Unless you are familiar with these tools, I would encourage you to bring suspected fraud issues to the <a href="http://chat.stackexchange.com/rooms/4/teachers-lounge" target="_blank">Teacher&#8217;s Lounge</a> where we&#8217;ll walk you through the process to investigate it further. For details, see this <a href="http://chat.stackexchange.com/rooms/4/conversation/fraud-detection-tools" target="_blank">fraud detection tools discussion</a> in chat and <a href="http://chat.stackexchange.com/rooms/4/conversation/voting-fraud-handling-protocol" target="_blank">what to do if you find fraudulent activity</a>.</p>

<h2>Reputation Recalc Removed</h2>

<p>The ability to recalculate a user&#8217;s reputation has been removed from the &#8216;mod&#8217; menu. The function is no longer necessary because the displayed score is now kept current with all the voting activity.</p>

<p>Up until recently, a user&#8217;s reputation score was only an approximation user&#8217;s actual score. Actions like deleting posts or removing users (and their votes) weren&#8217;t always reflected in the user&#8217;s displayed score. Over time, these discrepancies would add up, so a recalculation was the only remediation. That action is no longer necessary.</p>

<p>A system-wide recalculation was performed, so if your users are asking about unexpected changes in their reputation score, you can refer them to this blog post:</p>

<p><strong><a href="http://blog.stackoverflow.com/2012/03/reputation-and-historical-archives/" target="_blank">Reputation and Historical Archives</a></strong></p>

<h2>New Stack Exchange Beta Theme</h2>

<p>If your site is in beta, it&#8217;s about to get a much-needed facelift. We are retiring the familiar “Sketchy” theme and rolling out a more-polished and finished design for the beta sites. The blog post below will answer any questions your users may have. It also outlines some of the reasons behind this change and how it will benefit your community.</p>

<p><strong><a href="http://blog.stackoverflow.com/2012/03/the-new-stack-exchange-beta-theme-2/" target="_blank">The New Stack Exchange Beta Theme</a></strong></p>
]]></content:encoded>
			<wfw:commentRss>http://moderator.stackexchange.com/2012/03/march-newsletter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>January/February 2012 Newsletter</title>
		<link>http://moderator.stackexchange.com/2012/02/januaryfebruary-2012-newsletter/</link>
		<comments>http://moderator.stackexchange.com/2012/02/januaryfebruary-2012-newsletter/#comments</comments>
		<pubDate>Wed, 22 Feb 2012 19:01:57 +0000</pubDate>
		<dc:creator>Robert Cartaino</dc:creator>
				<category><![CDATA[newsletter]]></category>

		<guid isPermaLink="false">http://moderator.stackexchange.com/?p=112</guid>
		<description><![CDATA[Flag Weight is Dead, Long Live Flag Weight! Due to popular request, flag weight has been removed from user profiles. It is gone. Instead, when users flag posts, they will see a &#8216;helpful flags&#8217; count on their profile which links to a flag audit page. This listing contains a breakdown of flag outcomes by flag [...]]]></description>
				<content:encoded><![CDATA[<h2>Flag Weight is Dead, Long Live Flag Weight!</h2>

<p>Due to popular request, flag weight has been <a href="http://meta.stackoverflow.com/questions/84859/we-dont-need-to-see-flag-weight">removed from user profiles</a>. It is gone.</p>

<p>Instead, when users flag posts, they will see a &#8216;helpful flags&#8217; count on their profile which links to a flag audit page. This listing contains a breakdown of flag outcomes by flag type (moderator attention, spam, offensive, etc).</p>

<p>Users can only see their own count, but moderators can see the count on every user&#8217;s profile page. This allows you to see if a user is doing a good job of flagging posts&#8230; or letting you know if they are consistently misusing flags in some way. Now with the transparency of the audit pages, moderators can feel easier about &#8216;declining&#8217; flags as a learning experience to help users improve their flagging activity.</p>

<h2>Moderator Capacity Issues</h2>

<p>Moderating is a volunteer activity and everyone needs a vacation once in awhile. If moderation starts to become a daily grind, don&#8217;t hesitate to take a break. If you&#8217;re going to step away for more than a few days, just let us know. We can cover for you.</p>

<p>And if the moderation overload becomes chronic, please tell us! With 268 moderators, sometimes obvious signs of under-staffing are missed. If we know there&#8217;s a problem, we can take corrective measures to address the workload.</p>

<h2>Tag Wikis on Your Meta are Now Editable</h2>

<p>If you&#8217;re a <a href="http://moderator.stackexchange.com/2011/05/april-newsletter/">long-time reader</a> of our Moderator Newsletter, you&#8217;ll remember the significance of filling out your Tag Wikis. Now you can edit the wikis on your meta site, too. Sometimes the default tag wikis are not right for your site. Now you have full control to design the tag wikis to fit your community.</p>

<h2>Direct Links to Comments Now Supported</h2>

<p>Did you know you can link directly to a comment for reference? The time stamp following a comment is now a permalink to that comment. Try it out for yourself; it&#8217;s been enabled everywhere: <a href="http://meta.stackoverflow.com/questions/5436/direct-link-to-a-comment#comment319463_120688">http://meta.stackoverflow.com/questions/5436/direct-link-to-a-comment#comment319463_120688</a>.</p>

<h2>The Canonical FAQ on Meta SO</h2>

<p>I&#8217;m not generally a big fan of crowd-sourced FAQs. They tend to accumulate increasingly obscure issues which eventually devolves into the bulleted list from hell. But the Meta Stack Overflow questions tagged &#8216;faq&#8217; have actually shaped up into a nice collection of the most-asked questions users have. Next time you&#8217;re not quite sure how a feature works, use this resource as your &#8220;cheat sheet&#8221; to find the answers: <strong><a href="http://meta.stackoverflow.com/questions/tagged/faq">Meta Stack Overflow Questions Tagged &#8216;faq&#8217;</a>.</strong></p>

<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://moderator.stackexchange.com/2012/02/januaryfebruary-2012-newsletter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- This Quick Cache file was built for (  moderator.stackexchange.com/feed/ ) in 0.83971 seconds, on Jun 20th, 2013 at 11:53 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Jun 20th, 2013 at 11:58 am UTC -->