<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[TalkativeTurtles - Staff Lounge]]></title>
		<link>https://talkativeturtles.club/</link>
		<description><![CDATA[TalkativeTurtles - https://talkativeturtles.club]]></description>
		<pubDate>Wed, 05 Aug 2026 13:53:25 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[[Staff] Dealing With Difficult Users — Practical Scenarios]]></title>
			<link>https://talkativeturtles.club/showthread.php?tid=144</link>
			<pubDate>Mon, 29 Jun 2026 18:31:25 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://talkativeturtles.club/member.php?action=profile&uid=1">Zero Two</a>]]></dc:creator>
			<guid isPermaLink="false">https://talkativeturtles.club/showthread.php?tid=144</guid>
			<description><![CDATA[Theory is in the standards guide. This thread covers specific scenarios and how to handle them.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">The rules lawyer</span><br />
User who responds to every moderation action with a detailed argument about why it does not technically violate the rules. Approach: engage once, briefly. Explain the spirit of the rule, not just the letter. If they continue arguing, stop replying and flag the thread here. Do not get drawn into extended debates. Moderators do not need to win arguments.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">The ban evader</span><br />
New account that is clearly the same person as a banned user (same writing style, same topics, same targets). Action: permanent ban on the new account, note the original account in the reason. Do not engage with the account before banning. Flag to admin if you are unsure.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">The low-grade antagonist</span><br />
User who never quite crosses a clear line but consistently creates friction - slightly rude replies, borderline dismissive comments, never constructive. This is the hardest category. Action: informal PM warning early, documenting the pattern. If it continues across multiple threads over weeks, a formal warning is appropriate even if no single post is a clear violation.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">The good-faith boundary pusher</span><br />
User asking about security techniques that could be dual-use. They seem genuine. Approach: answer the educational question, watch the thread for follow-ups that clarify intent. If follow-ups push toward operational help for unauthorised activity, warn and lock.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Targeted harassment between users</span><br />
Two users in a recurring conflict that follows them across threads. Action: warn both if both are contributing to it. Move the conflict to a PM resolution if possible. If it continues publicly, temporary ban on the instigator or both. Do not pick sides publicly.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">The "I was just joking" post</span><br />
Something that violates the rules, removed, then defended as humour. Jokes can violate rules. Remove the content, issue the appropriate action, note that the intention does not change the impact.]]></description>
			<content:encoded><![CDATA[Theory is in the standards guide. This thread covers specific scenarios and how to handle them.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">The rules lawyer</span><br />
User who responds to every moderation action with a detailed argument about why it does not technically violate the rules. Approach: engage once, briefly. Explain the spirit of the rule, not just the letter. If they continue arguing, stop replying and flag the thread here. Do not get drawn into extended debates. Moderators do not need to win arguments.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">The ban evader</span><br />
New account that is clearly the same person as a banned user (same writing style, same topics, same targets). Action: permanent ban on the new account, note the original account in the reason. Do not engage with the account before banning. Flag to admin if you are unsure.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">The low-grade antagonist</span><br />
User who never quite crosses a clear line but consistently creates friction - slightly rude replies, borderline dismissive comments, never constructive. This is the hardest category. Action: informal PM warning early, documenting the pattern. If it continues across multiple threads over weeks, a formal warning is appropriate even if no single post is a clear violation.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">The good-faith boundary pusher</span><br />
User asking about security techniques that could be dual-use. They seem genuine. Approach: answer the educational question, watch the thread for follow-ups that clarify intent. If follow-ups push toward operational help for unauthorised activity, warn and lock.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Targeted harassment between users</span><br />
Two users in a recurring conflict that follows them across threads. Action: warn both if both are contributing to it. Move the conflict to a PM resolution if possible. If it continues publicly, temporary ban on the instigator or both. Do not pick sides publicly.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">The "I was just joking" post</span><br />
Something that violates the rules, removed, then defended as humour. Jokes can violate rules. Remove the content, issue the appropriate action, note that the intention does not change the impact.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[[Staff] New Moderator Onboarding Checklist]]></title>
			<link>https://talkativeturtles.club/showthread.php?tid=143</link>
			<pubDate>Sun, 28 Jun 2026 14:44:45 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://talkativeturtles.club/member.php?action=profile&uid=1">Zero Two</a>]]></dc:creator>
			<guid isPermaLink="false">https://talkativeturtles.club/showthread.php?tid=143</guid>
			<description><![CDATA[Welcome to the team. Work through this in order before taking any moderation actions.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">1. Read first</span><ul class="mycode_list"><li>Site-Wide Rules (Rules &amp; Guidelines forum)<br />
</li>
<li>Posting Etiquette &amp; Community Standards<br />
</li>
<li>Security &amp; Hacking Topics guide<br />
</li>
<li>Warnings, Bans &amp; Appeals Policy<br />
</li>
<li>Moderation Standards &amp; Consistency Guide (this forum)<br />
</li>
<li>How to Handle Reports (Reports &amp; Mod Queue forum)<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">2. Familiarise yourself with the tools</span><ul class="mycode_list"><li>Locate the Moderator CP - it is linked in the header when logged in as staff<br />
</li>
<li>Practice using the inline moderation tools (split, merge, move threads)<br />
</li>
<li>Find the warning system - Admin CP &gt; Users &gt; Warnings<br />
</li>
<li>Understand how reports appear in the Reports &amp; Mod Queue forum<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">3. Shadow for one week</span><br />
For your first week, do not take unilateral action on anything beyond obvious spam or clearly rule-breaking content. Flag everything else here first and discuss. This is not a trust issue - it is how you build pattern recognition for our specific community.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">4. Ask questions here</span><br />
If you are unsure about a situation, post it here before acting. There are no stupid questions in this forum. A wrong moderation action is worse than a delayed one.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">5. Check in regularly</span><br />
Staff are expected to check the forum at least a few times a week and respond to reports within 48 hours where possible. If you need to step back for a period, post here so we know.]]></description>
			<content:encoded><![CDATA[Welcome to the team. Work through this in order before taking any moderation actions.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">1. Read first</span><ul class="mycode_list"><li>Site-Wide Rules (Rules &amp; Guidelines forum)<br />
</li>
<li>Posting Etiquette &amp; Community Standards<br />
</li>
<li>Security &amp; Hacking Topics guide<br />
</li>
<li>Warnings, Bans &amp; Appeals Policy<br />
</li>
<li>Moderation Standards &amp; Consistency Guide (this forum)<br />
</li>
<li>How to Handle Reports (Reports &amp; Mod Queue forum)<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">2. Familiarise yourself with the tools</span><ul class="mycode_list"><li>Locate the Moderator CP - it is linked in the header when logged in as staff<br />
</li>
<li>Practice using the inline moderation tools (split, merge, move threads)<br />
</li>
<li>Find the warning system - Admin CP &gt; Users &gt; Warnings<br />
</li>
<li>Understand how reports appear in the Reports &amp; Mod Queue forum<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">3. Shadow for one week</span><br />
For your first week, do not take unilateral action on anything beyond obvious spam or clearly rule-breaking content. Flag everything else here first and discuss. This is not a trust issue - it is how you build pattern recognition for our specific community.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">4. Ask questions here</span><br />
If you are unsure about a situation, post it here before acting. There are no stupid questions in this forum. A wrong moderation action is worse than a delayed one.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">5. Check in regularly</span><br />
Staff are expected to check the forum at least a few times a week and respond to reports within 48 hours where possible. If you need to step back for a period, post here so we know.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[[Staff] Moderation Standards & Consistency Guide]]></title>
			<link>https://talkativeturtles.club/showthread.php?tid=142</link>
			<pubDate>Sat, 27 Jun 2026 10:58:05 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://talkativeturtles.club/member.php?action=profile&uid=1">Zero Two</a>]]></dc:creator>
			<guid isPermaLink="false">https://talkativeturtles.club/showthread.php?tid=142</guid>
			<description><![CDATA[This guide exists so that moderation decisions are consistent across the team regardless of which staff member handles a situation.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Core principle</span><br />
We moderate behaviour, not people. A user with 500 good posts who has one bad moment should be treated differently than a brand new account that opens with a rule violation. Context matters.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">The action ladder</span><br />
Start at the lowest appropriate action. Escalate only if the behaviour continues.<ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Edit or remove content</span> - for accidental rule breaks, off-topic posts in the wrong section, or minor issues. Leave a note explaining the action.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Informal warning (PM only)</span> - first time for most minor violations. Friendly tone. No formal warning point.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Formal warning</span> - for repeat minor violations or single significant ones. Adds a warning point. Short explanation of the rule broken.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Temporary ban</span> - when warnings have not changed behaviour, or for a serious single incident.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Permanent ban</span> - spam accounts, illegal content, doxxing, ban evasion.<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">When to loop in admin</span><ul class="mycode_list"><li>Any permanent ban decision<br />
</li>
<li>Disputes involving other staff members<br />
</li>
<li>Legal threats or complaints<br />
</li>
<li>Anything you are genuinely unsure about<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">Documenting actions</span><br />
All formal warnings and bans should have a note in the report queue with the reason and any context. This protects both the user and the moderator if an appeal is filed later.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Conflicts of interest</span><br />
If you have a prior personal conflict with a user, do not be the one to handle their reports or issue warnings. Flag it in here and another staff member will take it.]]></description>
			<content:encoded><![CDATA[This guide exists so that moderation decisions are consistent across the team regardless of which staff member handles a situation.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Core principle</span><br />
We moderate behaviour, not people. A user with 500 good posts who has one bad moment should be treated differently than a brand new account that opens with a rule violation. Context matters.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">The action ladder</span><br />
Start at the lowest appropriate action. Escalate only if the behaviour continues.<ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Edit or remove content</span> - for accidental rule breaks, off-topic posts in the wrong section, or minor issues. Leave a note explaining the action.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Informal warning (PM only)</span> - first time for most minor violations. Friendly tone. No formal warning point.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Formal warning</span> - for repeat minor violations or single significant ones. Adds a warning point. Short explanation of the rule broken.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Temporary ban</span> - when warnings have not changed behaviour, or for a serious single incident.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Permanent ban</span> - spam accounts, illegal content, doxxing, ban evasion.<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">When to loop in admin</span><ul class="mycode_list"><li>Any permanent ban decision<br />
</li>
<li>Disputes involving other staff members<br />
</li>
<li>Legal threats or complaints<br />
</li>
<li>Anything you are genuinely unsure about<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">Documenting actions</span><br />
All formal warnings and bans should have a note in the report queue with the reason and any context. This protects both the user and the moderator if an appeal is filed later.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Conflicts of interest</span><br />
If you have a prior personal conflict with a user, do not be the one to handle their reports or issue warnings. Flag it in here and another staff member will take it.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[[Staff] Staff Lounge Guidelines]]></title>
			<link>https://talkativeturtles.club/showthread.php?tid=17</link>
			<pubDate>Sun, 21 Jun 2026 09:34:07 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://talkativeturtles.club/member.php?action=profile&uid=1">Zero Two</a>]]></dc:creator>
			<guid isPermaLink="false">https://talkativeturtles.club/showthread.php?tid=17</guid>
			<description><![CDATA[The <span style="font-weight: bold;" class="mycode_b">Staff Lounge</span> is a private space for the moderation team to communicate, coordinate, and decompress.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Guidelines:</span><ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Keep discussions confidential.</span> Do not share what happens here with regular members unless explicitly agreed.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Discuss moderation decisions here before acting</span> on anything complex or contentious.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Treat each other professionally.</span> Disagreements about moderation policy should be constructive.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Flag urgent issues to admins directly</span> if this forum is too slow (use PM or off-forum contact).<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Document important decisions</span> so staff who are offline can catch up.<br />
</li>
</ul>
]]></description>
			<content:encoded><![CDATA[The <span style="font-weight: bold;" class="mycode_b">Staff Lounge</span> is a private space for the moderation team to communicate, coordinate, and decompress.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Guidelines:</span><ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Keep discussions confidential.</span> Do not share what happens here with regular members unless explicitly agreed.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Discuss moderation decisions here before acting</span> on anything complex or contentious.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Treat each other professionally.</span> Disagreements about moderation policy should be constructive.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Flag urgent issues to admins directly</span> if this forum is too slow (use PM or off-forum contact).<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Document important decisions</span> so staff who are offline can catch up.<br />
</li>
</ul>
]]></content:encoded>
		</item>
	</channel>
</rss>