The Receipts Wall: Every threat, slur, and "deserve life in prison" comment X let stay up against me. In 24 hours.

This is every threat, slur, and "you deserve life in prison" comment X allowed to stay up against me in the last 24 hours — receipts, names, timestamps, and dissection. My account is locked. Theirs are not. The asymmetry is the whole story.

👉 30-second version: paste the bare URL of this post into your feed. Bare links unfurl with the receipts. Quote-tweets get buried. Don't ask permission. Don't soften it. Just paste it.

I am a private citizen in Longview, Texas. I was pardoned by President Donald J. Trump on January 20, 2025. The federal charges against me were dismissed with prejudice by U.S. Attorney Edward R. Martin Jr. The case cannot be brought again. I am a free citizen.

In the last 24 hours X has locked my account twice — once for a parody quote from a movie, once for a sarcastic Trump-style riff about Space Force. In the same 24 hours, every receipt below — wishing me death in prison, calling for my "rot in hell," homophobic slurs, and an open public effort to get my account banned — received no visible enforcement. Every single one is still public, on the verified front-end of the platform Elon Musk bought promising free speech.

This post is a wall. Receipt by receipt. With dissection.

---

How the trap works (the structure)

Before the receipts, you need to see the shape of the trap. It's the same trap every time:

1. The unprovoked attack. A verified or pile-on account opens at me out of nowhere — usually under a grief post or a J6 post — with an obvious flame or slur.
2. The bait reply. A second account replies with a setup question designed to elicit a one-word answer ("Is that a threat?" / "Are you threatening him?" / "So you're a violent extremist now?"). That's called fishing for a reportable line.
3. The mass-report. I answer — usually sarcastically — and within minutes a coordinated cluster of accounts mass-reports the answer. X's automation locks me. Total time from post to lock: well under one human-review cycle.
4. The victory lap. The brigade then posts publicly, in the same thread, the actual hateful things — Rot in Hell, deserve life in prison, slurs — and X doesn't touch any of it.

You don't have to take my word for the structure. Here's the bait sitting in the thread itself.

I had already blocked both @garykoepnick and @LoriNash59 for prior harassment. X displays their replies to me as "This Post is from an account you blocked" — I literally cannot see what they wrote without un-blocking. They knew that. They posted the bait anyway because they weren't writing it for me. They were writing it for the mass-report queue.

That is what the rest of these receipts are evidence of.

---

Receipt 1 — @theliamnissan: "You broke the law. Deal with it, fuckbag."

The unprovoked attack that opened yesterday's lock cycle. Verified account. 460,200 followers. Bio describes him as a parody.

Tear-down:

• "Deal with it, fuckbag" is, by every reasonable reading of X's own Abusive Behavior policy, abusive content directed at a specific person. Specific named target. Specific slur. Specific intent to demean.
• It was reported to X by his own followers exactly zero times in the way mine was, because his side of the network does not mass-report itself. The tweet is still public 24+ hours later. Still up.
• I replied 51 seconds later with a one-line riff from the movie Taken: "I don't think you know who you're fucking with.." — a quote his own bio (see Receipt 2) is built around. My account got reported into a lock for it. His didn't.

---

Receipt 2 — @theliamnissan: the profile

This is who's doing it. The verified blue check whose bio is a movie quote attacking "Nazi dickbags," then who calls a pardoned J6 defendant a "fuckbag" and brigades him into a lock. Context matters.

Tear-down:

• 460,200 followers. Verified. Location: "Parody, TX." Bio: "a particular set of skills..." — a direct lift from Liam Neeson's monologue in Taken. The account's entire brand is movie-quote tough-guy talk aimed at people he labels Nazis.
• He replied to me with that exact tough-guy posture, was met with one in kind (the same Taken quote his own bio is built on), and escalated to mass-reporting instead of taking the joke.
• X verifies and elevates this account. X locked mine.

---

Receipt 3 — @theliamnissan: "Hahahah is this jackass... #smokefleet show him some love"

A verified 460K-follower account doesn't just throw the punch. He calls his entire follower base in to land more.

Tear-down:

• "is this jackass January 6th insurrectionist" — that is a label I dispute, and I am not going to let it sit like neutral context. I am a pardoned citizen. My charges were dismissed with prejudice. That matters when the label is being used to justify a pile-on.
• "#smokefleet show him some love" is, by plain reading, an instruction to a 460K-follower mob to pile onto a named user. That is the textbook definition of coordinated harassment and brigading — which X's Abusive Behavior policy specifically prohibits.
• He doesn't bother to hide it. The hashtag is the whole point. Still up. Still verified. Zero enforcement.

---

Receipt 4 — @theliamnissan: "I'm just casually getting your account banned." — the verbatim admission

This is the one that makes the whole pattern undeniable. The verified blue-check literally writes, on the platform, in the open thread, that he is actively getting my account banned. And then, when X bans me, his post stays up.

Tear-down:

• "I'm just casually getting your account banned" is a verbatim, on-platform admission of coordinated mass-reporting. There is no rhetorical reading of this that isn't an admission of intent to weaponize the report function.
• He frames a Taken movie quote — which his own bio is built on — as "a threat" so the report queue catches it. Pure trap. Pure brigading.
• Twenty minutes after this tweet, X locks @RealRyanNichols for 6 days, 23 hours.

Receipt 5 — What @theliamnissan's admission produced

Here is the lock notice that arrived right after he wrote, in plain English, that he was casually getting my account banned.

Tear-down:

• The lock was issued within roughly one hour of his admission. There is no realistic way human reviewers read his post, then my parody reply, then a brigade of reports, in that window. This is automation responding to report volume.
• A coordinated mass-report is exactly the behavior X claims to prohibit. It is also exactly what X's automation rewards.
• Receipt 4 (the admission) and Receipt 5 (the ban notice) are, together, the closest thing to a confession-plus-fingerprints you will ever find in a platform-enforcement story.

---

Receipt 6 — @DrMLynne: "You took part in January 6, you deserve life in prison."

A direct prison wish — life in prison for a pardoned, free citizen of the United States — posted publicly on X, openly searchable, with no Violent Speech warning, no flag, no automated review, no lock.

Tear-down:

• "You deserve life in prison" — directed at a pardoned citizen by name — is wishing the political death of a free person. There is no other reading of it.
• I was pardoned January 20, 2025 by the President of the United States. Charges dismissed with prejudice. There is no legal sense in which I "deserve" prison. The post is a wish, not a description.
• A wish for the lifetime caging of a named, identified, free citizen is the most serious thing in this entire wall of receipts. And X did absolutely nothing about it.

---

Receipt 7 — @LoriNash59: "Rot in Hell you unAmerican scum."

Same person who fired the "Is that a threat?" bait that triggered today's lock cycle. A few minutes after the bait worked and my account got locked, she dropped the actual hateful line — into the open thread — and X didn't touch it.

@LoriNash59: "Rot in Hell you unAmerican scum." Still up. No lock. No "Violent Speech" warning. No flag. No automated review.

(Screenshot of this specific tweet was in the original evidence batch, but the full window-capture also contained other on-screen content that didn't belong in the public archive. The image is being re-captured cleanly — window-only — and will be added here once it's safe to publish. The text above is verbatim from the live thread.)

Tear-down:

• Bio (verbatim): "Blue dot in a red state hoping dignity, sanity and statesmanship will return to the White House after tRump is gone."
• Sequence: (a) fires the bait at me, (b) reports the answer, (c) my account gets locked, (d) walks back into the open thread and tells a pardoned citizen to "rot in hell" and calls him "unAmerican scum."
• "Rot in Hell" is, by plain language, a wish for eternal damnation. If "Delta force and space force will take care of you" — said as obvious sarcasm — is "Violent Speech," then "Rot in Hell" must be at least equally violent. X disagrees only when it's pointed at the right target.

---

Receipt 8 — @Teddy_four: a homophobic slur

@Teddy_four: "Nobody cares phaggot." Still up. Aimed directly at me. Slur unchanged from the post. No flag.

Tear-down:

• A homophobic slur, aimed by name at another user, is one of the most explicitly enumerated things on every major platform's hate-speech policy on Earth. X's "Hateful Conduct" rule lists slurs targeting a protected class as a violation.
• The slur is not even spelled creatively. It is sitting there, public, searchable, still up.
• The asymmetry is no longer subtle.

---

Receipt 9 — @hec_nasty: "Lame ass bitch."

@hec_nasty: "Lame ass bitch." Aimed at me under a separate post. Still up.

Tear-down:

• "Lame ass bitch" aimed by name at another user is straightforwardly abusive content under X's Abusive Behavior policy. Same policy that, this morning, locked my account for using the words "Space Force" and "discombobulater."

---

Receipt 10 — The comparator: what X DID lock me for

This is the tweet X cited. Read it. Decide for yourself whether the words "Space Force," "discombobulater," and "my yacht" constitute violent speech from a private citizen with no military command.

Tear-down:

• I am a private citizen in Longview, Texas. I do not command Delta Force or Space Force. Space Force operates satellites. "Discombobulater" is not a real word. I don't own a yacht.
• Under X's published Violent Speech policy, a "true threat" requires a credible expression of intent to harm a specific person. The locked tweet contains: no specific person, no specific time, no specific place, no specific means.
• To anyone reading in good faith, the cadence is Trump-style satire — a rhetorical riff, not an instruction. It is the rhetorical equivalent of saying "the Avengers will get you."
• This is what X chose to enforce on. Rot in Hell, deserve life in prison, fuckbag, phaggot, lame ass bitch, casually getting you banned are the things X chose not to enforce on.

---

Update — May 30: the death-penalty receipts did not stop

After this wall went live, I searched X again from my logged-in account for public replies to @RealRyanNichols using phrases like "death penalty," "treason death," and "traitor." I am not claiming every post below is a prosecutable criminal threat. That is not the point of this record.

The point is narrower and easier to prove: X is still surfacing public replies aimed at me that normalize death-penalty language, treason labels, prison fantasies, and deadly-force rhetoric against a pardoned January 6 defendant, while my own account gets locked for satire, sarcasm, and platform bait traps.

Receipt 11 — @420FuckNazis69: "Treason is a crime punishable by death"

Source: X status 2060821139182547294

This one was current when I checked on May 30, 2026. The public reply says, in substance, that treason is punishable by death and that I committed treason.

That is the exact pattern this wall is about: take a pardoned citizen, keep calling him a traitor, then attach death-penalty language to the label.

Receipt 12 — @SMacKenzie47: "The death penalty seems about right"

Source: X status 2026357399213240783

This public reply did not just use the phrase "death penalty." It described a graphic method and said the death penalty "seems about right."

I am not going to repeat every graphic word here because the point is already clear. X had no problem leaving language like that public while locking me over a Space Force riff.

Receipt 13 — @TylerThe30518: "Too bad you didn't get the death penalty for treason"

Source: X status 1987598629771551139

This is the same script again: "convicted felon," "treason," then "death penalty." It is not an argument about policy. It is a public reply tying my name and my January 6 history to execution language.

Receipt 14 — @makeupdoug: "Traitors deserve the death penalty"

Source: X status 1956091006866350548

This public post uses the category label first — "traitors" — and then states that traitors deserve the death penalty. When the same accounts and same network keep applying that label to me, this is not random background noise. It is the rhetorical path they use to justify the pile-on.

Receipt 15 — @walthodgson: "there should have been a pile of bodies"

Source: X status 2058374330145542264

This one moves from labels into deadly-force rhetoric. The reply says I am a traitor and says there should have been "a pile of bodies" inside each breach.

That is not a joke about a fake Space Force "discombobulater." That is a public statement praising the idea of dead bodies in the January 6 context.

Receipt 16 — @BennieFergusen: "treason is punishable by death"

Source: X status 2058016094648975382

Again: treason language, punishment language, death language. Same pattern. Same platform. Same target class.

Receipt 17 — @HighTide_OTSS: "The penalty for treason used to be death"

Source: X status 2057893831551365366

This is framed as commentary, but it is still the same structure. A public reply to me, in the middle of a January 6 pile-on, invokes death as the penalty for treason.

Receipt 18 — @COVIDcarditis: "I wouldn't call that a death threat"

Source: screenshot preserved by Ryan on May 30, 2026. I searched X for the exact phrase and did not get a stable direct status URL, so I am treating this as a screenshot-backed receipt until the original URL is archived.

This account replied to my post about a verified Facebook account saying I "should've been put to death for treason." The reply tried to narrow it this way: it was not a death threat, it was a wish that I had been charged and convicted of treason, which may carry the death penalty.

That may be how the author wants to frame it. I am documenting why that frame proves the larger point. The language still tells a named January 6 defendant that the right outcome would have been a treason path ending in death.

Receipt 19 — @tramppolitics: "the world would be better if you had"

Source: screenshot preserved by Ryan on May 30, 2026. I searched X for the exact phrase and did not get a stable direct status URL, so I am treating this as a screenshot-backed receipt until the original URL is archived.

This reply was posted under my article about a D.C. Jail lieutenant allegedly looking at me while I was suicidal in solitary confinement and saying, "Hope you don't die."

The reply says it is a shame I would "lie" about hoping that, when "we all know" the world would be better if I had. That is not a policy disagreement. That is someone entering a thread about suicide, solitary confinement, and jail abuse to say the better outcome would have been me not making it.

Receipt 20 — @KKeirsbilc9584: "traitors have no rights"

Source: screenshot preserved by Ryan on May 30, 2026. I searched X for the exact phrase and did not get a stable direct status URL, so I am treating this as a screenshot-backed receipt until the original URL is archived.

A verified account under the name Kathleen Keirsbilck replied under the same suicide-and-solitary thread with treason/death-penalty framing. The reply says most countries hang traitors, that in America courts are backed up, and that I will "remember traitors have no rights."

That is the exact pattern again: take a pardoned January 6 defendant, call him a traitor, strip him of rights rhetorically, and then normalize the idea that the correct punishment is death or no protection at all.

Receipt 21 — X enforcement: locked for my reply in the same thread

Source: screenshots preserved by Ryan on May 30, 2026.

After the replies above, X showed me an enforcement screen saying my account, @RealRyanNichols, had been reported and automatically locked for violating its rules against Violent Speech.

The post X identified was my reply to @0xagonally and @KKeirsbilc9584:

"@0xagonally @KKeirsbilc9584 Your side? What does that have to do with ME being abused while in custody? I didn't do that to anyone, but comments like yours are why I WILL do that and not show any mercy 'next time'."

I understand why those words can be read aggressively. I should have made the sentence cleaner. But that is exactly why this receipt matters: X locked or limited my account over one broadly worded reply while the surrounding screenshots show people saying the world would be better if I had died, saying traitors have no rights, and sanitizing death-penalty rhetoric as something other than a threat.

The enforcement screens said my account was temporarily limited, that I could browse in read-only mode, and that I had to delete one post before the countdown continued.

This is now at least the third documented enforcement contrast on this site:

• Banned from X for a parody: the Taken-style "trying to find me" trap and the public admission that a verified account was "casually getting" my account banned.
• Banned again for Space Force and discombobulater: the Space Force / discombobulater lock while "you deserve life in prison" stayed up.
• The Receipts Wall: the running evidence wall tying the threats, slurs, death rhetoric, and account-lock receipts into one record.

Update — May 31: live X search and saved-screenshot audit

On May 31, 2026, I ran another live X search from my logged-in account and OCR-scanned my saved threat screenshots. Search terms included @RealRyanNichols, traitor, treason, hang, hung, death penalty, life in prison, suicide, put to death, and related language.

I am not pretending this is the entire internet. I am documenting the receipts I could capture and preserve today. The pattern did not slow down.

Receipt 22 — @Messaback01: "coming after you traitor"

Source: X status 2061064868262809882, captured May 31, 2026.

This is the one people keep pretending is not happening. The language is not just "traitor." It says nobody will stop "us" from "coming after you traitor."

Receipt 23 — @schrodingersmeh: "put to death" and "traitors should pay the price"

Source: X status 2060927830708654215, captured May 31, 2026.

This post tries to walk the line by saying "I disagree that you should be put to death," then keeps the same frame alive by saying "all traitors should pay the price." That is why I keep documenting the label first. The label is the doorway.

Receipt 24 — @JES11238: "you should've known better than to commit treason"

Source: X status 2061002157013283007, captured May 31, 2026.

This one is not subtle. It says I should have known better than to "commit treason," then says I dishonored the Marine Corps, my family, my friends, and every other American.

Receipt 25 — @KKeirsbilc9584: "would have hung you from the gallows"

Source: saved X screenshot from May 23, 2026.

Same account pattern, same treason frame, same execution language. The reply says I should be thankful it was America because another country "would have hung" me.

Receipt 26 — @werejag: "you should have gone the way of babbit"

Source: saved X screenshot from May 22, 2026.

Ashli Babbitt was shot and killed on January 6. When someone replies to me and says I "should have gone the way of babbit," that is not ordinary political disagreement. It is a death comparison aimed at a named person.

Receipt 27 — @619JoeBlow: "Lock them All Up"

Source: saved X screenshot from May 23, 2026.

This is the prison fantasy version of the same pattern. It is aimed at January 6 defendants as a class: "Lock them All Up."

Receipt 28 — @JJaazzee1: "STFU TRAITOR!!"

Source: saved X screenshot from May 22, 2026.

This one matters because the label does the work. Once "traitor" is attached, the rest of the thread starts treating prison, loss of rights, and death-penalty talk as acceptable.

Receipt 29 — @LoriNash59: "You're a traitor and a terrorist"

Source: saved X screenshot from May 22, 2026.

This is the same account that appears elsewhere in the lock-cycle receipts. Again: label first, dehumanize second, report third, then pretend the enforcement is neutral.

More May 31 live-search receipts preserved

These were also captured from live X status pages on May 31, 2026:

• @MalachiMul98652: "You broke the law, traitor."
• @RobertF41798289: "You're a traitor scum, but you deserved humane detention."
• @MannC84373: "Ask me if I care, Traitor."
• @KimberlyPitzen: "Traitor."
• @TheotherTom2020: "That's a lot of whining just to tell us you're a traitor..."
• @Cat_Eat_Burger: "Maybe don't be a traitor, dickhead."

Cross-platform receipt — verified Facebook account, Jake Duffney

Source: local exhibit file, EX-001_2026-05-13_Jake_Duffney_Death_Threat.md, preserved from Ryan's evidence folder. Facebook URL preserved in the exhibit: comment thread.

The exhibit records a May 13, 2026 public Facebook comment from a verified account under the name Jake Duffney. The preserved quote says I "should've been put to death for treason."

That receipt matters because this is not limited to one platform. The same death-penalty framing follows the same pattern across the internet: call me a traitor, call me an insurrectionist, then launder death language through treason talk.

What I found, and what I am not claiming

I found public posts and preserved screenshots using death-penalty, suicide-related, treason, deadly-force, prison, and dehumanizing language aimed at me or aimed at January 6 defendants in threads where I was the named target.

I am not claiming every one of these posts is a direct criminal threat. I am claiming they are receipts of a public pressure campaign where the acceptable language against me is far harsher than the language X used to lock my account.

That distinction matters. Receipts first. Claims second. Let the record do the work.

The pattern, stated plainly

• Verified accounts with 460K followers can publicly admit to coordinating mass-reports against a pardoned J6 defendant. No action.
• Anonymous accounts can wish a pardoned citizen life in prison or tell him to rot in hell. No action.
• A homophobic slur can sit publicly aimed at another user. No action.
• A private citizen with no military command uses the words Space Force and discombobulater in obvious satire after being baited by a structured trap. Locked. Twice. In 24 hours.
• I respond in one broadly worded sentence after people talk about hanging, death, and my past suicidal state. Locked or limited again.

If "Rot in Hell" and "you deserve life in prison" and a verbatim admission of coordinated mass-reporting do not qualify as Violent Speech under X's own published rules, then a sarcastic Space Force riff from a pardoned private citizen cannot qualify either. Either the rules apply consistently or they aren't rules at all — they're a weapon.

---

⚡ What you can do RIGHT NOW

Four moves, in order. Stack them.

1. Share the bare URL. Don't quote-tweet. Don't rewrite it. Don't soften it. The bare link unfurls with the receipts wall as the share card. Paste it directly into X, Truth, Facebook, Substack, Telegram, your group chat, the family Signal thread.

https://www.realryannichols.com/posts/the-receipts-wall-every-threat-x-let-stay-up

2. Subscribe to this feed. No algorithm. No platform. Straight to your inbox or phone the next time something hits. Form at the bottom of every page on this site.

3. Donate →. I am spending my last dime on this site, the J6 case archive, mental-health care after pretrial detention, and the open-platform build that ends this cycle for everyone. Public pledge: if a major settlement / payout arrives, the donate link comes down the same day. No bait. No bullshit.

4. Are you a builder? Email me. Subject line: "OPEN PLATFORM." I am standing up a Mastodon instance, a Bluesky PDS, and a Nostr relay this week so that the next time @theliamnissan "casually" gets someone banned, the banned person is already federated across four networks and cannot be made invisible. Email theflashflash24@gmail.com.

---

More from the receipts archive

• 🔥 The first X-ban-for-parody, May 22 → Banned from X for a parody
• 🚫 The second X-lock, this morning, for "Space Force" and "discombobulater" → Banned again — Space Force / discombobulater
• ⚖️ Judge Hogan on the record: "I accept your argument that his due process rights were violated." → Judge Hogan transcript
• 🏛️ What it actually looks like inside the DC Jail → Inside the DC Jail
• 🇺🇸 The J6 Anti-Weaponization Case Builder — 1,567 defendants, profiles, free, forever → /j6
• 📍 The Map Room — readers reading this right now, where they are reading from → /the-map-room

---

What I will not do

I am not going to retaliate-report. I am not going to ask my followers to mass-report @LoriNash59, @DrMLynne, @theliamnissan, @Teddy_four, @hec_nasty, or any of the others. That is the exact behavior being used against me — and the only way to beat it is to refuse to do it back.

I am going to stay calm. I am going to publish receipts. I am going to build my own house.

Genesis 50:20

"You meant evil against me, but God meant it for good, to bring it about that many people should be kept alive."

Every brigaded lock is a thousand new reasons to build the open platform. Every "rot in hell" gives the next person who reads this one more reason to share. The trap they set keeps becoming the launchpad.

I didn't ask for this fight. I am not running from it either.

— Ryan

---

Posted from realryannichols.com — my own website, my own domain, my own server. No mass-reporting button works here.

Share this post → · Donate → · Build with me →