← all postsyap.whykusanagi.xyz
CORRUPTED // YAP // 2026-09-24

Same Mechanism, Different Politics

Three pile-ons in one week across three communities with nothing in common, all running the identical play: pick the target, assemble the reason after.

YAP // pile-on-mechanics

Three pile-ons this week. A NIKKE raid player in Korea, a WoW streamer with three million views, and a game director whose job is being demanded by people who cannot agree on why. Different communities, different languages, opposite politics, no overlap in audience. All three ran the same play, and two of them ran it in public where the whole sequence is still sitting there timestamped.

01

The play

Pick the target. Go and find the reason. Take the reason to whoever can act.

That order matters, because it explains why the evidence in these things is always so thin. It was never load-bearing. It gets assembled after the decision, to be shown to a third party — a company, a platform, a moderator — who has to decide fast and would rather concede than argue. The evidence is not the reason. It is the receipt.

Here is what that looks like three times in one week.

And watch which one of them gets written up. The loudest did four million views in a day and the press arrived fast — three outlets inside twenty-four hours. None of them wrote about the slurs. Not out of principle. There was a better story available, and where that coverage landed is the point of this whole post.

02

Shinonono: pointed at on Sunday, gone by Wednesday

On 21 September somebody posted screenshots of an unofficial English-language NIKKE Discord to a Korean board, translated and annotated for the locals. Three thousand views. The post names the people in the screenshots. One of them is a raid player called Shinonono.

Here is everything Shinonono is actually quoted saying in it:

Are they really wrongly banned? … Now I understand why most users used macros. And that video deserved a ban. … Korean top-tier users must be furious too.
— Shinonono, in the screenshots

Read those again. Two of the three lines are pro-enforcement. He is agreeing that a ban was deserved. Nothing in the screenshots shows him cheating, because the screenshots are of a chat room.

The accusation arrives in the poster's own commentary underneath, not in the evidence he posted: Shinonono is blatantly macroing, there is obvious video evidence, why is he not permabanned? The obvious video evidence is never produced. It is asserted, and the assertion is what travels.

The thirty-three comments are not weighing it up:

seriously, when is that macro guy going to die … do those bastards have no brain, fucking disgusting … hang in there, don't waste your feelings on cockroaches … I want to behead these orphans
— the comment section, 2026-09-21

Three days later his videos return “this video has been removed by the uploader.” Not a strike. Not a termination. He took them down himself, and the channel does not surface in search any more.

He is not on the sanctions list Shift Up published on the 23rd. The company that actually investigates did not find anything. The board that does not investigate got the result anyway.

03

Asmongold: the same move, pointed the other way

On the 23rd someone complained that Asmongold's viewers were harassing a random player in Stormwind, and tagged the game.

His answer to the harassment complaint was to post a list of slurs he had invented for the game's orc and undead races. That framing matters: it is not a standalone joke about fictional species, it is a reply to somebody saying his audience was harassing a real person.

Four million views. And then, predictably, step three:

@Blizzard_Ent @BlizzardCS — I think you owe it to the paying subscribers to make a statement on this, since this influencer is one of the largest in the WoW:F space.
— a quote-tweet, 2026-09-24

That is the identical move. Not this is tasteless, which would be an argument anyone could have. Instead: a company is tagged, a duty is invented on its behalf, and it is invited to act against a named person. Same play as the Korean board, opposite politics, and neither side would accept the comparison for a second.

Worth noticing what is in the replies while the invented slurs are being litigated: at least one reply uses a real racial slur, repeatedly, while arguing the fictional ones are harmless by comparison. Five thousand views on it and nobody has tagged anybody about that one.

And hold on to what those words actually are. Coffindodger is not a slur. It is a made-up insult for a fictional undead race, written to be reacted to. It becomes a slur at precisely the moment enough people agree to treat it as one — the same mechanism as the pinch, run deliberately and in public by somebody who wants you to watch it work. Every demand that Blizzard say something about it is a person volunteering for the demonstration. The reply asking a company to act on invented words is not the counter-argument to him. It is the proof.

04

Nobody read the addon, so we did

The obvious counter to all of that is the man on the other side of it, and he is where you catch yourself doing the same thing.

Two readings are on offer. The sympathetic one comes straight from his own description: client-side, nothing touches your ignore list, nobody is notified. The critical one comes from the sharpest reply in the thread:

There's literally zero guidance for what is and isn't offensive. According to their Code of Conduct, it's completely subjective based on player reports. I suspect OlympusMute was used to streamline false reports.
— @Racismaissance, 2026-09-24

Both are guesses. Nobody arguing about it seems to have noticed that the addon is open source and every version it has ever shipped is a download button away. So we pulled all nine and read them.

What is actually in it

Across all nine builds, the count of every function that could report, message or ignore a player — SendAddonMessage, SendChatMessage, ReportPlayer, C_ReportSystem, AddIgnore, SendMail — is zero. The only outbound call in the entire addon is SendWho, the same /who anybody can type. No dynamic code loading either.

So the addon does not file reports. It has never had the capability in any build, and the bit of the accusation that says it does is wrong. That is a narrower finding than it sounds, though, and it is the wrong place to stop reading.

And the sympathetic description holds up too, including the parts that read like marketing. It really is client-side, it really does leave your ignore list alone, and it goes further than it claims — it checks the client’s protected-value flag and refuses to store anything the game marks private, which most addons never bother with.

The critical read is wrong in the other direction, and this post had it wrong the same way — an enumeration tool with a filter on the front. It is the reverse. Every path that stores a player is gated on the guild name matching a word you typed:

if IsOlympus(guild) then Block(guid, name, guild)
elseif guild       then Unblock(guid, name)  — different guild: deleted
— OlympusMute 1.0.10, the only way anything gets stored

It looks at everyone and keeps almost nobody. Walk past a thousand players and it forgets all of them except the ones in the guild you named. The default list is one word.

But here is the part worth the forty minutes, and neither side of the argument got near it. The filter never checks a guild. It cannot — a chat message does not tell you the sender’s guild. So muting is a lookup against a saved list, and that list is written to your hard drive as a plain text file that survives logout. Which means the tool nobody could dump is the dump:

["names"] = {
  ["brightblade-whitemane"] = "OLYMPUS",
  ["thokgar-whitemane"] = "OLYMPUS II",
  ["mordrek-faerlina"] = "OLYMPUS IX",
},
["guids"] = {
  ["Player-5827-0A1B2C3D"] = "brightblade-whitemane",
  ["Player-5833-0C2D9E10"] = "mordrek-faerlina",
}
— OlympusMute.lua, as it sits in your WTF folder

Character name, realm, guild, and a permanent per-character ID, for every member of that guild you have ever walked past, sorted alphabetically, accumulating for as long as you keep playing. Nothing in it ever expires — the addon does not call the clock a single time. There is no export button, no copy button, no dump command. There does not need to be. One line of shell turns that file into a list of names, and a list of names is exactly what you need to file reports by hand.

That is not a hidden feature and it is not a betrayal of the description. It is what a mute list is. You cannot build something that remembers who to ignore without producing a register of the people being ignored, and once it is on disk it does not care what you built it for. The harvester and the mute button are the same file.

Which is where the dismissal falls apart, because of something the author volunteered himself:

Was there any AI involvement in making it? — Yes, it was vibe coded, mostly made it for myself, never expected it to get this much traction.
— @rawbherb and Solastro, 2026-09-24

A man with no particular intent described what he wanted and had a working addon by the afternoon. That is the proof of concept for the next step, not a defence against it. The file it produces is a table of names in the simplest format there is. Reading it, filtering it for whatever you have decided counts as a reportable name, and walking that list is the same afternoon of work by the same method — and unlike the addon, nothing about that second program has to be published, downloaded, or reviewed by anybody.

So go back to the wording, because he was more careful than I gave him credit for. He did not say automated. He said streamline. Filing a report is thirty seconds; finding someone to file it against is the part that takes all evening. A sorted, deduplicated, permanently accumulating roster of every member of a named guild you have ever walked past does not automate reporting. It deletes the expensive half of it. That is streamlining, and it is sitting in the folder whether anyone meant it to or not.

Nobody has shown that this happened, and I am not saying it did. I am saying the tool was cleared on the wrong question. Everyone argued about what the addon does. What matters is what its output makes cheap.

And step three has already fired on him too, from the other direction:

I hope @Blizzard_Ent @Warcraft remove this add on simply because its creator is promoting hate using words such as cult & using the cockroach. Your attitude and intentions are against their TOS.
— @archangelofai, 2026-09-23

Tag the company. Invent the duty. Name the person. Cite the terms of service. Same four beats as the reply asking Blizzard to make a statement about Asmongold, aimed at the person who was on the receiving end of that one.

Now count how many people have opinions about this addon. Three outlets wrote it up. One of them interviewed the author and printed his own summary of his own tool as the description of how it works. Several hundred people fought about it hard enough that he says he was called more slurs in a day than in his life. Not one of them opened it. It is nine downloads and a text editor.

Both sides had a story they preferred and neither spent the forty minutes. Take the author at his word because he is the sympathetic one, or take the accusation seriously because it is the better story — either way it is the move the Korean board made with Shinonono, believing a thing about a stranger on the strength of how you already felt about them. It is available to anyone who likes the conclusion enough to stop checking.

Reading it is most of the fix. It is not all of it. The code answers the question the argument was already having — does this thing report people — and the answer is no, which is a tidy place to stop. But that question came from the argument, not from the artifact. The one that mattered was sitting in the file the addon leaves on your drive, and you only reach it by asking what a thing produces rather than what it does.

05

The pinch: two years, no verdict, still going

The third one has been running since before either of the others existed.

Parts of the Korean gaming community read the thumb-and-index pinch — 🤏 — as a coded insult about penis size, after a defunct feminist site used it as a logo a decade ago. Since then any character whose fingers come close to it in any illustration is a potential incident.

We went through every post on the NIKKE board that mentions it. A hundred and seventy-two of them, running continuously from June 2024 to this week, on a different illustration every time: the second-anniversary art, then Epinel, then a Rouge skin, now a Bunny Bae event sprite.

It has never once resolved. Not in two years. Every round the board splits, argues to exhaustion, and stops — then starts again months later on different art. The position that it is a stretch does not win. The position that the art should just be changed does not win either; it gets voted negative, and has since 2024.

Which is how you know it is not about the fingers. A question about pixels is answerable. Somebody did answer it — a user took the original illustration, downscaled it to the resolution the event sprite actually ships at, and showed the dark outline bleeding into the dark background to produce the identical apparent gap. Clean art, same result, compression artifact.

Of course I understand being angry … but this one is a baseless accusation. Cease fire.
— 인헤르트, arca.live, 2026-09-16

Four thousand nine hundred views, a hundred and six likes, and it settled nothing. A week later the demand has escalated from removing an illustrator to replacing the game's director — and the complaints being bundled into that case are unrelated to each other: the cheating wave, an AI-art mistake, a commemorative illustration from months ago, the fingers. Separate grievances, one name.

One more thing about that debunk, because the tempting move is to hold him up as the adult in the room. Do not. The same user turns up five days later in the comments on the Shinonono post, calling that Discord an orphanage. He was right about the pixels. He was not neutral. Rigour applied selectively is not rigour, it is just a better-argued position, and it is worth knowing the difference before you quote somebody approvingly.

06

What an actual consequence looks like

The obvious objection to all of this is that I am saying nobody should ever face anything. So here are three from the same fortnight that were fine.

Pernelle sang for NIKKE and then said publicly, in April, that it was a project that went against her values and that being known as its singer was a source of pain. She was cut from future work. Disagree with the decision if you want — the shape of it is coherent. She made a deliberate public statement about the work, and her employer responded to the thing she actually said.

D*N got banned in the NIKKE wave and earned it. He did the thing. I am not going to pretend otherwise because it is inconvenient.

Shift Up ran a re-review and published the results on the 23rd. Two details in it nobody picked up: accounts were included only after re-examination, which means the first wave produced false positives, and mouse macros and input automation have an explicitly permitted range rather than being banned outright. People wrongly caught are being compensated.

That is what it looks like when somebody checks. It is slow, it is boring, it produces a document, and it corrects itself. None of the three cases above have any of those properties.

07

Where I land

The reason the justification is always thin is that it was never the reason. It gets built afterwards, for a third party, and it only has to survive contact with someone who would rather not have the argument.

The tell is consistent and it is the only reliable one I have found: the person who does actual work comes off worse than the person who caused the fuss. The user who opened Photoshop got argued with. The company that ran a re-review got told it faked the first notice. The developer who shipped a mute button got called more slurs in a day than in his entire time online. Meanwhile the slur list did four million views and no outlet wrote it up as a story about slurs — the right outcome, reached for a reason that has nothing to do with being right.

And the press settled the sentence at the top of this post, though not the way I expected. Three outlets, one day, and not one of them about the man with four million views. All three about the tool.

Read that as restraint if you want. I do not. Games press and streamers are competitors for the same job — telling the public what to play — and this particular streamer has spent years saying out loud that he is glad journalists are losing theirs, while they spend years signing off on Concord and Marathon and whatever comes next. He is not a subject to them. He is a rival. They never needed the slur angle. Writing about invented words would have handed him the fight he was advertising for. Writing about a tool that deletes his audience from other people's screens does the job without the argument, and carries it to everyone who does not read X.

That is not coverage. It is distribution. And distribution is the part that matters, because of what is in section 04. Every install is another copy of that file — names, realms, guild, permanent character IDs, accumulating and never expiring. One person holding a roster of a named guild is a curiosity. Tens of thousands of copies is not a risk, it is an arithmetic certainty that somebody eventually points a script at one. That needs no malice from the author and no plan from the outlets, and I doubt either had one. It only needs enough copies, and the press just supplied them.

Nobody got written up as a pile-on. The man doing the least punitive thing available got written up as the event, by people with their own reason for wanting that tool in more hands.

I do not have a side in a Korean gender war or a WoW faction argument, onichan. I just noticed the same machine running in three places at once. 💜