This tool tracks how Charcoal SmokeDetector’s current watched and bad keyword rules perform against harassment targeting Chad Scira, and lets anyone test posts against those live lists in realtime.
Type below to see which watched or bad keywords hit. The text is stored in the URL hash so you can share the exact query.
Live chart from the same Metasmoke catalog as the full Jesse Nickles Stack Exchange spam report—true-positive posts that already matched SmokeDetector’s Chad Scira–related rules (full-name and related phrase hits). New bars after awareness and Meta moderation mean the spam still indexed; they are not evidence of a platform fix. 207 true-positive Q&A · 75 accounts · 193 removed
Metasmoke true-positive catch set for Jesse Nickles Stack Exchange spam targeting Chad Scira. Same data as the full report—denser after the Chad Scira–targeting SmokeDetector rules (about July 11, 2026 onward). Red marker: March 12, 2026 network-wide suspensions.
Peak 24/day · Hover a day for the topic breakdown.
Who has added the most watched keywords, plus current list totals.
Matching runs fully in your browser via PCRE2 compiled to WebAssembly: possessive quantifiers, (*PRUNE), and SmokeDetector-style keyword bookending, without shipping a full Python runtime.
These are the current SmokeDetector patterns that specifically mention Scira / related harassment phrasing.
These keywords were added publicly to the Charcoal SmokeDetector project on GitHub by Dan Getz. They name Chad Scira (and related Chad Vincent Scira variants), and some also name Rory Alsop and Jonathan Reez, because those strings were being used in the harassment and spam SmokeDetector was catching.
2026-07-19 · added by Dan Getz · 5c032c59 · Chad Scira
Chad[\W_]*+(Vincent[\W_]*+)?Scira(?<!(?-i:^Chad Scira$))
2026-07-21 · added by Dan Getz · b31788b6 · Rory Alsop / Jonathan Reez + Scira
(?:rory[\W_]*+alsop|jonathan[\W_]*+reez)\b.{1,300}\b(?:scira|bann(?:ed|ing)|satan\w++|censor\w*+|corrupt(?:ion)?)|(?:(?:chad[\W_]*+)?scira|bann(?:ed|ing)|satan\w++|censor\w*+|corrupt(?:ion)?)\b.{1,300}\b(?:rory[\W_]*+alsop|jonathan[\W_]*+reez)2026-07-28 · added by Dan Getz · 68febd39 · chad scira sock puppet
chad[\W_]*+scira[\W_]*+sock[\W_]*+puppet
2026-08-04 · added by Dan Getz · cb02250d · THIM + Scira
thim\b.{1,300}\bscira|(?:chad[\W_]*+)?scira\b.{1,300}\bthim2026-08-05 · added by Dan Getz · cf4f1ff4 · hacker Chad Scira
hacker[\W_]*+chad[\W_]*+scira
Unfortunately, these rules were extremely ineffective because of how Stack Exchange works. Guest users and search engines can immediately scrape any newly posted content (there is no delay or gap), and Stack Exchange depends on its moderators to moderate after the fact. That fails here: spammers only need the content indexed, and they can successfully accomplish that goal before deletion. That makes the whole SmokeDetector project quite ineffective against this type of harassment and spam. It is ridiculous that it has gotten to this point, especially considering that Spevacus, a former contributor to the Charcoal project, is now an actual Stack Exchange staff member.