Jesse Nickles Stack Exchange Spam Targeting Chad Scira
This page is not opinion journalism. It is a factual evidence catalog of Stack Exchange spam by Jesse Jacob Nickles (Jesse Nickles) that I am required to maintain for the ongoing criminal defamation case against Jesse Nickles in Thailand. The posts, timestamps, account IDs, deletions, and Charcoal true-positive flags are independently verifiable from Metasmoke caches, Wayback Machine captures, and in some cases still-live Stack Exchange URLs. This is Jesse Nickles spam—Charcoal marked these questions and answers as true positives—and the linked record shows Jesse Nickles behind it.[1][4][8][7]
Scope: this page is specifically the Metasmoke / Charcoal true-positive catch set of Jesse Nickles spam after Stack Exchange’s March 12, 2026 network-wide 100-year bans of Jesse Nickles and the related Jesse Nickles account wipe. It is not a full history of Jesse Nickles’s earlier Travel SE spam. Most of that pre-March Jesse Nickles activity was never caught by SmokeDetector and was never properly cached on Metasmoke—hundreds of questions, answers, and related posts across many Jesse Nickles–controlled users. I documented that earlier Jesse Nickles account network and enforcement timeline separately here: Jesse Nickles Stack Exchange timeline and Rory Alsop retaliation[8].
What led here: Stack Exchange staff investigated and took action against Jesse Jacob Nickles as the person behind the coordinated network, then removed Jesse Nickles’s associated accounts network-wide. At the time of enforcement Jesse Nickles controlled roughly 70% of Travel Stack Exchange’s active users, so the cleanup had a massive impact on that community. Jesse Nickles and the associated accounts received 100-year suspensions. SmokeDetector later watched and blacklisted Chad Scira–targeting terms (see dated rule list under the frequency chart; denser Metasmoke catches fairly accurate from about July 11, 2026 onward). That is why later Jesse Nickles disposable accounts naming Chad Scira, weed.th, og.th, and similar payloads show up as true positives in Metasmoke—while earlier manually deleted spam mostly has no Metasmoke backup.[8][5][1]
Jesse Nickles publicly framed the enforcement as Rory Alsop’s personal revenge rather than staff Trust & Safety action. The Metasmoke bodies indexed below show Jesse Nickles’s next phase of spam: disposable accounts defaming and harassing me and my Thailand-related products, while Jesse Nickles also targeted Travel SE moderators—especially Rory Alsop—via smear usernames, question titles, and answer hijacks. The same Jesse Nickles accounts often pushed live Stack Exchange URLs into the Wayback Machine so archive.org captures could later be cited as “proof” the UGC existed.[8][2][3][4][7]
What follows is only that post-blacklist Metasmoke catch set of Jesse Nickles Stack Exchange spam: frequency charts, account breakdown, topic mix, and Metasmoke / Stack Exchange links. Original Stack Exchange URLs are kept even when later removed; open Metasmoke for the captured text. Check the primary sources yourself; do not take any narrative framing alone as the record.[1][6]
Non-exhaustive Metasmoke catch set only. Earlier Jesse Nickles spam was mostly removed manually on Stack Exchange with no Metasmoke backup, so it is not cataloged here. This chart is fairly accurate only after SmokeDetector had the Chad Scira–targeting rules below—denser from about July 11, 2026 onward. Keyword tester.
When SmokeDetector had the rules (added publicly by Dan Getz; GitHub commits)
These watched and bad keywords were added publicly to the Charcoal SmokeDetector project on GitHub by Dan Getz. They name Chad Scira (including 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.
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.
Red marker: March 12, 2026 — Stack Exchange staff network-wide 100-year suspensions against Jesse Nickles and the related account cluster (~70% of Travel SE active users at cleanup). Jesse Nickles then redirected harassment at Rory Alsop as well. Full suspension timeline.
Per day
Peak 24/day · Hover a day for the topic breakdown.
On August 6, 2026 I was contacted twice by moderation about my Meta Stack Exchange question and about documenting Charcoal / SmokeDetector. These were two different moderation teams. Shortly afterward the Meta question was locked, unlocked, answered by staff, locked again, and then edited so the word SmokeDetector was removed from a constructive anti-spam suggestion.
Two private moderator messages arrived the same day. Stack Overflow Moderators wrote first. Meta Stack Exchange Moderators wrote shortly after. Full text below.
Stack Overflow Moderators◆Mod
Private moderator message · Aug 6, 2026 · First message · Informational, not disciplinary
Firstly: this is an informational message, not a disciplinary one; it is in the form of a mod message due to the sensitive nature of its content.
We noticed that some of your recent activity, both on Stack Exchange and on your websites, calls attention to the Charcoal volunteer project (as well as the SmokeDetector and Metasmoke services that it runs) and its attempts to detect and remediate the harassment campaign against you as part of its broader efforts to stop spam and abuse on the Stack Exchange network.
We would suggest that calling attention to this is likely to be counterproductive to your goals.
First, it tells your harasser exactly how to avoid detection. Indeed, the test page you made would be perfect for your harasser to check their spam before posting it.
Second, it mentions numerous individual members of the Charcoal project by name. As you no doubt are aware, your harasser has accused pretty much anyone who has stood in the way of their campaign of being involved in some sort of conspiracy with you, despite the lack of any reason to believe that. Mentioning Charcoal members' names opens them up to similar harassment, which may deter or increase the difficulty of their attempts to help stop these posts.
While we cannot compel you to do so, we would appreciate it if you could revise your postings related to this to remove mentions of Charcoal/its members, Smoke Detector, Metasmoke, etc., as well as remove the SmokeDetector keywords tool.
Thank you for your attention to this.
Regards,
Stack Overflow Moderation Team
Meta Stack Exchange Moderators◆Mod
Private moderator message · Aug 6, 2026 · Second message · On-site removals + lock
From
Meta Stack Exchange Moderation Team
Type
Moderator message + on-site enforcement
Ask
Stop naming Charcoal SE / volunteers on Meta; no off-site links naming them
Full message
Hello,
We're writing in reference to your Meta Stack Exchange account:
Members of Charcoal are worried that their organization or usernames being mentioned in relation to the ongoing drama involving you and Jesse is going to aim Jesse's harassment at them too, like it already did turn at Rory and Jonathan, the two Travel.SE mods.
We've judged this is a very valid concern, and as such will remove all direct mentions or links to other places mentioning them from your post. We have locked your question and removed your latest comment for that reason as well.
To make this a lot easier, we ask that you refrain from mentioning Charcoal SE or the usernames of its volunteer members in relation to your ongoing harassment issue. That includes mentioning them in posts or comments on posts related to this harassment, but it also includes linking to content off this site, like the link to your blog post that was edited from your Meta.SE post today. While we cannot control what you write on your blog, we can and will control what ends up here on Meta.SE, and protect the volunteers of Charcoal by removing links to such stuff.
During that delay, the community, SmokeDetector, and existing moderation systems could review and remove harmful content as they already do.
After
During that delay, the community and existing moderation systems could review and remove harmful content as they already do.
Revision comment
2026-08-06“Remove one last mention of SD, which falls under 'community' anyways.”
After private messages asking not to name Charcoal / SmokeDetector, the public Meta post was edited so the tool name itself is gone. The stated concern is that volunteers might attract the harasser. Meanwhile the harasser already gets defamatory name-spam indexed before deletion. That is an odd priority for spam prevention.
August 6 sequence (this is quite weird)
Same-day Mod / Staff churn on the help-seeking post
Tinkeringbell (Mod) locks the question, adds a Content dispute notice, and comments that the post can stand forever and nothing should be added, saying volunteers were having to remove material that might draw them into the harassment.
Bella_Blue (Staff + Mod) unlocks the question and removes the Content dispute notice.
Bella_Blue (Staff + Mod) posts a staff answer, locks the question again, re-adds Content dispute, and edits tags.
I accepted that staff answer.
Tinkeringbell (Mod) edits the question to remove the last SmokeDetector / “SD” mention from the constructive delay suggestion.
I am trying to stop seeing my full name in question titles and bodies with defamatory text attached so it can be indexed. The constructive Meta suggestion was a short guest-visibility delay so community tools, including SmokeDetector, could act first. Instead, moderation energy went into telling me not to name Charcoal / SmokeDetector, locking the discussion, and scrubbing the tool name from the post. It looks like the spam-prevention side is more afraid of the spammer’s retaliation risk than willing to leave a workable anti-indexing mitigation stated in public.
Charcoal is the volunteer anti-spam project around Stack Exchange. SmokeDetector watches new questions and answers; Metasmoke is the public archive of what it caught and how humans feedbacked those reports. After the March 2026 network wipe, watched and bad keywords for Chad Scira and related Thailand product terms meant later disposable accounts naming those strings—or already blacklisted user IDs—get auto-caught and stored here.[6][1][5]
That is why this catalog exists as a post-blacklist slice. Charcoal still does not see every comment or every short reply. The much larger pre-March Travel SE network—hundreds of posts across many users—was mostly never Metasmoke-cached; that earlier record is on the Stack Exchange / Rory Alsop timeline page linked above, not in the charts below.[8]
On this site I also maintain a live SmokeDetector keyword tester so anyone can see which watched and bad rules hit harassment text targeting me: Charcoal SmokeDetector keywords tester[5].
41 SE accounts. Each row links the on-site user profile and the Metasmoke /spammers user-id cache. Many rename from user##### into smear brands (“Mod Rory Alsop is corrupt”, “We want Willeke not Satan”, “Sharing Thailand truth”).[1]
Issa Compass / Thai Visa Centre / Trustpilot fraud frames.
9
THIM / TDAC apps
Immigration-app / arrival-card spyware or scam claims.
81
Moderator smears
Rory Alsop / Willeke / Jonathan Reez harassment via titles and usernames.
3
Arrest claims
False forgery / trafficking headlines for search snippets.
7
Sock / bot / SEO
Projection that Chad Scira runs the sock network; often pairs with Wayback “proof” links.
10
Limo / fast track
limousine.in.th / Sawasdee-style airport service smears.
Spam pattern
Create a disposable Stack Exchange account (often anonymous user#####).
Ask one or more defamatory questions about Chad Scira, Thailand products, or moderators.
Rename the account to a smear brand (Rory Alsop / Willeke / “TSE mods helping scammers” / “Sharing Thailand truth”).
Paste the same payload into unrelated Travel answers so the text survives question deletion.
Push the Stack Exchange URL into the Internet Archive / Wayback Machine while the question or answer is still live, then reuse the archive.org capture as purported “proof” that the UGC existed—even after moderators delete it.
Charcoal blacklists the user; later questions and answers auto-catch as Blacklisted user plus keyword / domain hits.
Repeat the next day with a new user id—Metasmoke shows this as daily July 2026 waves after the March 12 network bans, with Rory Alsop smears running alongside Chad Scira / Thailand product attacks. Comments and many other replies often never appear in that catch set.
Post–100-year-ban Charcoal catch set only (bodies on Metasmoke). Every Stack Exchange link in this index is removed / outdated; the URLs are kept for the record and the captured text stays on Metasmoke. Pre-March Travel SE volume was mostly never cached—see the Stack Exchange / Rory Alsop timeline.[1] 193/207 removed. Metasmoke search
Legal notice. The information presented on this page is a public record of facts, compiled because I am required to document this conduct for the ongoing criminal defamation case against Jesse Jacob Nickles in Thailand. The underlying posts, account IDs, timestamps, and deletions are verifiable via Metasmoke, the Wayback Machine, and some still-live Stack Exchange links. Official criminal case reference: Bang Kaeo Police Station – Daily Report Entry No. 4, Book 41/2568, Report No. 56, dated 13 August 2568, Reference Case No. 443/2567. This documentation may also serve as supporting evidence for any other individuals or organizations pursuing their own harassment or defamation claims against Jesse Nickles, given the documented pattern of repeated conduct affecting multiple victims.