<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Ban on Know the Tech</title>
        <link>https://knowthe.tech/tags/ban/</link>
        <description>Recent content in Ban on Know the Tech</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en</language>
        <copyright>knowthe.tech</copyright>
        <lastBuildDate>Wed, 08 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://knowthe.tech/tags/ban/index.xml" rel="self" type="application/rss+xml" /><item>
        <title>Discord&#39;s Safety Bug Falsely Banned Thousands of Accounts Over Square Images</title>
        <link>https://knowthe.tech/p/discords-safety-bug-falsely-banned-thousands-of-accounts-over-square-images/</link>
        <pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate>
        
        <guid>https://knowthe.tech/p/discords-safety-bug-falsely-banned-thousands-of-accounts-over-square-images/</guid>
        <description>&lt;img src="https://knowthe.tech/imgs/discord-chat-moderation.jpg" alt="Featured image of post Discord&#39;s Safety Bug Falsely Banned Thousands of Accounts Over Square Images" /&gt;&lt;p&gt;Discord has acknowledged that a bug in its automated safety systems has been incorrectly banning accounts since May 2026, with thousands of users caught in the crossfire due to an overzealous content moderation algorithm.&lt;/p&gt;
&lt;p&gt;The issue, which Discord&amp;rsquo;s support team addressed on X on Monday, centered on how the platform&amp;rsquo;s AI-powered moderation tools flagged certain images. Specifically, posts containing square grid images — including innocuous content like spreadsheets, chessboards, and Minecraft inventory menus — were mistakenly identified as child sexual abuse material (CSAM).&lt;/p&gt;
&lt;h2 id=&#34;8200-accounts-affected-since-may&#34;&gt;8,200 Accounts Affected Since May
&lt;/h2&gt;&lt;p&gt;While Discord confirmed that roughly 200 accounts were erroneously banned over the most recent weekend alone, the company estimates the bug may have impacted approximately &lt;strong&gt;8,200 accounts&lt;/strong&gt; since the problem first surfaced in May 2026.&lt;/p&gt;
&lt;p&gt;The company uses automated, AI-driven content moderation systems that compare uploaded media against known harmful material. Discord&amp;rsquo;s Trust &amp;amp; Safety team acknowledged that false positives are a known limitation of this approach, and ordinarily, flagged content is reviewed by a human moderator before any enforcement action is taken against the user.&lt;/p&gt;
&lt;h2 id=&#34;a-double-bug-wrongful-bans-that-couldnt-be-undone&#34;&gt;A Double Bug: Wrongful Bans That Couldn&amp;rsquo;t Be Undone
&lt;/h2&gt;&lt;p&gt;Discord explained that the intended system behavior is to &lt;strong&gt;temporarily pause uploads&lt;/strong&gt; during the human review period, not to ban the account outright. However, a bug caused accounts to be banned instead. Even worse, when the Trust &amp;amp; Safety team reviewed the flagged content and cleared it as harmless, &lt;strong&gt;a second bug prevented the ban from being automatically lifted&lt;/strong&gt;, leaving affected users locked out of their accounts.&lt;/p&gt;
&lt;p&gt;&amp;ldquo;The intended behavior is to temporarily pause uploads during that review, not ban the account. We had a bug that caused the latter,&amp;rdquo; Discord&amp;rsquo;s support team wrote on X. &amp;ldquo;When our staff reviewed and cleared those accounts, the same bug prevented the ban from being lifted automatically, so it just stayed in place.&amp;rdquo;&lt;/p&gt;
&lt;h2 id=&#34;what-kind-of-content-triggered-the-bug&#34;&gt;What Kind of Content Triggered the Bug?
&lt;/h2&gt;&lt;p&gt;The bug&amp;rsquo;s trigger was surprisingly broad. Any image featuring a square grid pattern could set off the false positive:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Spreadsheets&lt;/strong&gt; from productivity software&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Chessboards&lt;/strong&gt; showing game positions&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Minecraft inventory screens&lt;/strong&gt; from the popular game&lt;/li&gt;
&lt;li&gt;Other grid-based images&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This wide trigger range meant that users sharing innocuous gaming screenshots, productivity content, or hobby-related images all risked being banned.&lt;/p&gt;
&lt;h2 id=&#34;discords-response-and-apology&#34;&gt;Discord&amp;rsquo;s Response and Apology
&lt;/h2&gt;&lt;p&gt;Discord has apologized for the incident, calling it an &amp;ldquo;embarrassing mistake&amp;rdquo; to have remained active for approximately two months. The company stated that all accounts wrongfully banned due to the bug should now be reinstated.&lt;/p&gt;
&lt;p&gt;The incident highlights the ongoing challenges platforms face when relying on AI-powered moderation tools. While automated systems are necessary to handle the enormous volume of content uploaded to platforms like Discord every day, false positives remain a persistent problem — and when those false positives are compounded by software bugs, the consequences for users can be severe.&lt;/p&gt;
&lt;h2 id=&#34;lessons-for-the-industry&#34;&gt;Lessons for the Industry
&lt;/h2&gt;&lt;p&gt;This episode serves as a cautionary tale for the &lt;a class=&#34;link&#34; href=&#34;https://discord.com/blog&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;
    &gt;broader tech industry&lt;/a&gt;, where AI moderation is increasingly relied upon to police content at scale. Discord&amp;rsquo;s experience underscores the importance of building robust fallback mechanisms, ensuring that human review processes work as intended, and thoroughly testing automated enforcement systems before deploying them widely.&lt;/p&gt;
&lt;p&gt;For now, Discord users who found themselves unexpectedly banned over the past two months should check whether their accounts have been reinstated. If the issue persists, reaching out to Discord&amp;rsquo;s support team is the recommended next step.&lt;/p&gt;
</description>
        </item>
        
    </channel>
</rss>
