<?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 - Reports & Mod Queue]]></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] Appeals Log & Decisions Record]]></title>
			<link>https://talkativeturtles.club/showthread.php?tid=147</link>
			<pubDate>Tue, 30 Jun 2026 22:18: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=147</guid>
			<description><![CDATA[Use this thread to log ban appeals and the decisions made on them. Format each entry as follows:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>Date: [date appeal received]<br />
Username: [appealing account]<br />
Original action: [warning/temp ban/permanent ban + reason]<br />
Appeal reason: [brief summary of what they said]<br />
Decision: [upheld/reduced/overturned]<br />
Decision by: [staff member]<br />
Notes: [any relevant context]</code></div></div><br />
Keeping this record serves two purposes:<ul class="mycode_list"><li>Consistency - we can see how similar appeals were handled in the past<br />
</li>
<li>Accountability - if a decision is later questioned, the reasoning is documented<br />
</li>
</ul>
<br />
If an appeal results in a ban being overturned, also update the original ban record in the system with a note.<br />
<br />
No active appeals at this time. This thread will be updated as appeals are received.]]></description>
			<content:encoded><![CDATA[Use this thread to log ban appeals and the decisions made on them. Format each entry as follows:<br />
<br />
<div class="codeblock"><div class="title">Code:</div><div class="body" dir="ltr"><code>Date: [date appeal received]<br />
Username: [appealing account]<br />
Original action: [warning/temp ban/permanent ban + reason]<br />
Appeal reason: [brief summary of what they said]<br />
Decision: [upheld/reduced/overturned]<br />
Decision by: [staff member]<br />
Notes: [any relevant context]</code></div></div><br />
Keeping this record serves two purposes:<ul class="mycode_list"><li>Consistency - we can see how similar appeals were handled in the past<br />
</li>
<li>Accountability - if a decision is later questioned, the reasoning is documented<br />
</li>
</ul>
<br />
If an appeal results in a ban being overturned, also update the original ban record in the system with a note.<br />
<br />
No active appeals at this time. This thread will be updated as appeals are received.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[[Staff] Spam Identification & Handling Procedures]]></title>
			<link>https://talkativeturtles.club/showthread.php?tid=146</link>
			<pubDate>Mon, 29 Jun 2026 04:38: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=146</guid>
			<description><![CDATA[Spam is the most common moderation task. This guide covers identification and the full handling workflow.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Types of spam we see</span><ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Bot registrations</span> - register and immediately post links. Usually obvious from the account age (minutes) and post content (generic compliment + link).<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Human spammers</span> - make a few legitimate-looking posts to build account credibility, then drop promotional content. Harder to catch early.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Necro-spam</span> - reviving old threads with a single promotional reply or link.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Signature spam</span> - user adds SEO links to their signature. May not post spam content itself.<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">Handling procedure</span><ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Step 1:</span> Remove the spam post(s) immediately.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Step 2:</span> Check the user profile - review all their posts for other spam you may have missed.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Step 3:</span> Ban the account. For obvious bots, permanent ban with reason "Spam account." For human spammers who have legitimate posts, use judgment - a warning first if the spam was isolated and recent.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Step 4:</span> If the spam contained a malicious link, flag it here with the URL (do not make it clickable) so it can be added to the domain blocklist.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Step 5:</span> If there is a surge of spam from similar accounts (same IP range, same content pattern), flag in the Staff Lounge so admin can review registration settings.<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">Do not engage with spam accounts</span><br />
Do not reply to their posts, even to call them out. Remove silently. Public callouts attract attention to the spam and sometimes the spammer.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">False positives</span><br />
Occasionally a legitimate new user will post something that looks like spam - low post count, link in first post, promotional-sounding. Check the context. A developer sharing their open source project in Project Showcase is not spam. If unsure, flag here rather than banning immediately.]]></description>
			<content:encoded><![CDATA[Spam is the most common moderation task. This guide covers identification and the full handling workflow.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Types of spam we see</span><ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Bot registrations</span> - register and immediately post links. Usually obvious from the account age (minutes) and post content (generic compliment + link).<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Human spammers</span> - make a few legitimate-looking posts to build account credibility, then drop promotional content. Harder to catch early.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Necro-spam</span> - reviving old threads with a single promotional reply or link.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Signature spam</span> - user adds SEO links to their signature. May not post spam content itself.<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">Handling procedure</span><ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">Step 1:</span> Remove the spam post(s) immediately.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Step 2:</span> Check the user profile - review all their posts for other spam you may have missed.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Step 3:</span> Ban the account. For obvious bots, permanent ban with reason "Spam account." For human spammers who have legitimate posts, use judgment - a warning first if the spam was isolated and recent.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Step 4:</span> If the spam contained a malicious link, flag it here with the URL (do not make it clickable) so it can be added to the domain blocklist.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Step 5:</span> If there is a surge of spam from similar accounts (same IP range, same content pattern), flag in the Staff Lounge so admin can review registration settings.<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">Do not engage with spam accounts</span><br />
Do not reply to their posts, even to call them out. Remove silently. Public callouts attract attention to the spam and sometimes the spammer.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">False positives</span><br />
Occasionally a legitimate new user will post something that looks like spam - low post count, link in first post, promotional-sounding. Check the context. A developer sharing their open source project in Project Showcase is not spam. If unsure, flag here rather than banning immediately.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[[Staff] Report Triage Guide — Priority & Response Times]]></title>
			<link>https://talkativeturtles.club/showthread.php?tid=145</link>
			<pubDate>Sun, 28 Jun 2026 00:51: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=145</guid>
			<description><![CDATA[Not all reports have equal urgency. This guide defines priority levels and expected response times.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Priority 1 — Act immediately (within 2 hours)</span><ul class="mycode_list"><li>Spam with malware, phishing, or scam links<br />
</li>
<li>Doxxing - personal information posted without consent<br />
</li>
<li>Illegal content of any kind<br />
</li>
<li>Direct threats against identifiable individuals<br />
</li>
</ul>
Action: remove the content first, handle the account after. Do not leave harmful content up while you deliberate.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Priority 2 — Same day</span><ul class="mycode_list"><li>Targeted harassment in an active thread<br />
</li>
<li>Ban evasion accounts actively posting<br />
</li>
<li>Misinformation being spread in a fast-moving thread<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">Priority 3 — Within 48 hours</span><ul class="mycode_list"><li>General rule violations (off-topic posts, minor rudeness)<br />
</li>
<li>Spam without malicious links (promotional posts, low-effort advertising)<br />
</li>
<li>Duplicate threads<br />
</li>
<li>Incorrect forum section<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">Priority 4 — When you get to it</span><ul class="mycode_list"><li>Requests to move or merge threads<br />
</li>
<li>Minor formatting issues flagged by users<br />
</li>
<li>Outdated information in old threads<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">After handling a report</span><br />
Post a brief update in the report thread here: what the report was, what action was taken, and by whom. This keeps the team aligned and creates a record for appeals.]]></description>
			<content:encoded><![CDATA[Not all reports have equal urgency. This guide defines priority levels and expected response times.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Priority 1 — Act immediately (within 2 hours)</span><ul class="mycode_list"><li>Spam with malware, phishing, or scam links<br />
</li>
<li>Doxxing - personal information posted without consent<br />
</li>
<li>Illegal content of any kind<br />
</li>
<li>Direct threats against identifiable individuals<br />
</li>
</ul>
Action: remove the content first, handle the account after. Do not leave harmful content up while you deliberate.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Priority 2 — Same day</span><ul class="mycode_list"><li>Targeted harassment in an active thread<br />
</li>
<li>Ban evasion accounts actively posting<br />
</li>
<li>Misinformation being spread in a fast-moving thread<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">Priority 3 — Within 48 hours</span><ul class="mycode_list"><li>General rule violations (off-topic posts, minor rudeness)<br />
</li>
<li>Spam without malicious links (promotional posts, low-effort advertising)<br />
</li>
<li>Duplicate threads<br />
</li>
<li>Incorrect forum section<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">Priority 4 — When you get to it</span><ul class="mycode_list"><li>Requests to move or merge threads<br />
</li>
<li>Minor formatting issues flagged by users<br />
</li>
<li>Outdated information in old threads<br />
</li>
</ul>
<br />
<span style="font-weight: bold;" class="mycode_b">After handling a report</span><br />
Post a brief update in the report thread here: what the report was, what action was taken, and by whom. This keeps the team aligned and creates a record for appeals.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[[Staff] How to Handle Reports]]></title>
			<link>https://talkativeturtles.club/showthread.php?tid=18</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=18</guid>
			<description><![CDATA[This forum tracks member reports and items in the moderation queue. Handle all reports logged here.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Process:</span><ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">First staff member to see a report takes ownership.</span> Post a reply saying you are handling it.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Act within 24 hours</span> of a report being filed where possible.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Document your action</span> - what you did and why - so there is a record.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Escalate to an admin</span> if the correct action is unclear or if the reported user is a veteran/VIP member.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Warn before banning</span> for first-time minor offences unless the violation is severe (spam bots, illegal content, doxxing).<br />
</li>
</ul>
]]></description>
			<content:encoded><![CDATA[This forum tracks member reports and items in the moderation queue. Handle all reports logged here.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">Process:</span><ul class="mycode_list"><li><span style="font-weight: bold;" class="mycode_b">First staff member to see a report takes ownership.</span> Post a reply saying you are handling it.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Act within 24 hours</span> of a report being filed where possible.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Document your action</span> - what you did and why - so there is a record.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Escalate to an admin</span> if the correct action is unclear or if the reported user is a veteran/VIP member.<br />
</li>
<li><span style="font-weight: bold;" class="mycode_b">Warn before banning</span> for first-time minor offences unless the violation is severe (spam bots, illegal content, doxxing).<br />
</li>
</ul>
]]></content:encoded>
		</item>
	</channel>
</rss>