Discord Handle: tylor/kum (Tylor/Ikum)

Page 5 and page 7 of the same warrant, side by side. Two usernames, one post. Full write-up →
One post. One warrant. Two usernames.
Page 5 of Affidavit for Search Warrant 3217131 describes the confession in prose and attributes it to a username written tylor/kum — rendered elsewhere as Tylor/Ikum. Page 7 of the same document reproduces the screenshot, and the screenshot header says zealous_monkey_55095.
Nothing in the warrant reconciles them. No footnote, no "also known as", no explanation.
The record on this handle
| Field | What the record says |
|---|---|
| Handle | tylor/kum, also written Tylor/Ikum and tylor.kum |
| Where it appears | Page 5 prose of Affidavit for Search Warrant 3217131 |
| What it is attributed to | The same confession post shown on page 7 under a different name |
| Reconciled anywhere? | No. Not in the warrant, not in charging documents, not in any public filing |
| Standing | Unexplained. It is in a sworn court document and it does not match the exhibit |
Why this is not a triviality
A username is an identifier. In a case built on one screenshot, the identifier attached to that screenshot is not a detail — it is the whole chain of custody in a single string.
There are ordinary explanations. A person can hold two accounts. A display name can differ from a handle. An affiant can transcribe from memory, or from a second document, and get it wrong. Any of those is more likely than anything sinister.
But which ordinary explanation applies has never been stated, and it is the sort of thing a native platform export answers in one line. The state has said it does not intend to offer the forensic extractions, which is where that line would live.
The renderings, gathered
The same string reaches the public in at least three shapes, which is itself a sign that nobody outside the case has seen the underlying data:
- tylor/kum — page 5 prose as commonly transcribed
- Tylor/Ikum — the rendering used in analysis reproduced below
- tylor.kum — the Discord-style rendering, with a dot, used in later write-ups
Compare The Same Exchange, Three Renderings, where the identical problem shows up in the message text rather than the username.
The relationship to the Steam names
The Steam profile attributed to the same person runs as craftin247, later milk. That name shares nothing with either Discord rendering. Three identifiers, no overlap, and no document that ties them together — which is exactly why the Steam roster had to be built from a public comment wall.
Every Image That Carries This Handle
Each image below is an archived capture in which this handle, or the document that names it, is readable. Every one links to its own full write-up page.






What Would Settle It
- The native Discord export showing the account that authored the post.
- A statement from the affiant explaining where the page 5 username came from.
- Discord's subpoena return naming the account that posted it.
- Any court filing that reconciles page 5 with page 7 of its own warrant.
The Fix
None of the records above is available to the public, and nothing in the current process compels their release. The Charlie Kirk disclosure laws are the mechanism that does.
- Law 1 — FBI and DOJ Disclosure. The federal file on this circle, including whatever the twenty-plus interviews produced, is held and not published.
- Law 2 — US Intelligence Disclosure. If any account in this circle was operated from outside the United States, US intelligence already knows or can find out. Law 2 forces that answer into the open — and a clean answer clears everyone here by name.
- Law 4 — Trusted Investigations. The strongest of the four, because it removes the Department of Justice as gatekeeper. It lets trusted investigators compel records from a private company — Discord, Valve — and take testimony from people who were actually in that circle under threat of perjury.
Read the four laws → · The explainer video →
The Location Field Is Typed In. The IP Address Is Not.
On Discord, on Steam, and on every platform in this section, the country shown on a profile is a text box the user filled in. Anyone can type Utah, or Egypt, or nothing at all, and change it again in seconds. Whether it is shown publicly is a setting. It is not evidence of where a person was sitting when they typed a message.
What is not typed in is the IP address. Every session, every login, every message send is written to the platform's own logs with the address it arrived from, alongside device fingerprints and session timing. Discord holds that record for the servers named in the Utah State Bureau of Investigation's warrant — Craftopia, Gamin and The Corruption — and for the account that posted the confession. Valve holds the equivalent record for every Steam account in the same circle.
That is the question this section keeps returning to: is it known where the people in these servers actually were? The FBI reportedly examined twenty or more people in Robinson's Discord circle and charged none of them, and nothing in the public record states where any of them were. To be explicit, because it matters: being in another country is not wrongdoing, no one in those servers has been accused by any authority of anything, and nothing on this site suggests any of them did anything improper. The point is narrower — that a location nobody has verified should not be treated as if it were verified, in either direction.
The answer exists. It is in Discord's subpoena return and in the login-IP history for September 10–12 — records that investigators can obtain through lawful process and the public cannot. What we are asking for is that the record for the account that posted the confession be established through that process and, so far as the law allows, made public. Until it is, every claim of foreign involvement in these chats — and every denial — rests on a field somebody typed.
We are not asking anyone to identify, locate, contact or expose any private individual, and readers should not attempt it. We name no one and we accuse no one. This is a request for a record, not an allegation against a person.
The Steam Side
- craftin247 → milk — the Steam identity for the same person, sharing nothing with either Discord rendering.
- Every Other Username Was Redacted — the caption on this same warrant, and why the Steam comment wall became the best public list of names.
- The Steam Names Roster
Interesting In This Area
- The competing attribution is zealous_monkey_55095.
- Search Warrant 3217131 carries both, four pages apart.
- A third identity is reported for the same person in the leak archive.
- Discord Friends, Servers and Handles holds the complete roster.
Interesting In Other Areas
- Forensic phone extraction is the one process that resolves a username dispute.
- The custody timeline is the other unresolved problem on the same post.
- How the confession was produced is where this discrepancy is usually raised.
- FBI investigation — twenty-plus people in this circle, none charged.
The Handles, On One Card

Every Handle and Account in This Circle
Each name below has its own page — the full record on it, every archived image it is readable on, and the link across to its counterpart on the other platform.
Discord handles
zealous_monkey_55095 · tylor/kum (this page) · bedbug inspector · Lancelotl · Flexolotl · fentanylsandwich1312 · generic8076 · Ankha_Kitty · Craftopia, Gamin, The Corruption
Steam accounts
craftin247 → milk · Ankha · cento · Thank You · luvr · Alive but Gay · miss your son is clicker trained · Xx_chubby_ch43_xX · Lucy · peace walker · Cute Lamb Needs Attention · Milsnss · silly goose
The two full indexes: Discord Friends, Servers and Handles · The Steam Names Roster
Most or all of the people named above are very probably ordinary gamers who did nothing wrong. They commented on a public gaming profile or listed a handle in a bio. The list is published because the search warrant redacted every other username, and because an investigation that can obtain login records could clear each account by name.
This website's author is @HolonCitizen on X and YouTube/@HolonCitizen. Follow me there.