Esc
SafetyCase Closed

Bluesky user urges violence against deepfake porn creators

Is this a scandal?

No longer — the story has resolved. Noise 33/100, holding steady, across 1 source.

SCAND-259299as of Methodology
Cite this incident"Bluesky user urges violence against deepfake porn creators." SCAND.Ai incident SCAND-259299, noise 33/100 as of October 26, 2026. https://scand.ai/scandal/bluesky-user-urges-violence-deepfake-porn-creators
FORECASTForecast, not fact

Platforms will likely remove the post for violent incitement while facing criticism for appearing to protect abusers, because inconsistent enforcement erodes trust among victim advocates.

33

Noise 33/100 — louder than 95% of tracked AI controversies.

AI-assisted analysis · How we work

Why it matters

Highlights tension between protecting victims of non-consensual AI imagery and platform enforcement against violent rhetoric targeting perpetrators.

Key points

  1. Bluesky user kinkel19561 posted Dutch-language incitement to violence against deepfake creators on September 25, 2026.
  2. The post explicitly advocated severe physical mutilation including eye-gouging and ear-biting as punishment for AI pornographers.
  3. Content praised women taking extralegal action against non-consensual intimate imagery creators as boundary enforcement.
  4. The statement creates moderation dilemmas by combining legitimate anti-abuse sentiment with prohibited violent incitement.
  5. Incident reflects growing public frustration with inadequate legal remedies for AI-generated sexual abuse material.

The story

A Bluesky user identified as kinkel19561 posted a message in Dutch on September 25, 2026, urging physical violence against creators of non-consensual deepfake pornography. The post explicitly advocated gouging eyes and biting ears off offenders while praising women who enforce their own boundaries. The statement has drawn attention to the escalating conflict between anti-deepfake advocates and platform content moderation policies regarding vigilante justice. While the post condemns illegal AI-generated sexual abuse material, it simultaneously violates standard terms of service prohibiting incitement to violence. Content moderation teams now face the challenge of addressing harmful speech that emerges as a direct response to technological abuse. This incident underscores the difficulty platforms encounter when policing rhetoric that frames violence as defensive justice for victims of AI exploitation.

Who's involved

Critic
kinkel19561

Advocates physical violence against deepfake porn creators as justified retribution and boundary enforcement

Neutral
Bluesky Trust & Safety

Must enforce terms of service prohibiting violent incitement regardless of target's alleged misconduct

How the conversation shifted

the split has narrowed

Polarity (0–100) from the noise pipeline, sampled over time.

Join the Discussion

Discuss this story

Community comments coming in a future update

Be the first to share your perspective. Subscribe to comment.

Noise Level

Murmur33?Noise Score (0–100): how loud a controversy is. Composite of reach, engagement, star power, cross-platform spread, polarity, duration, and industry impact — with 7-day decay.
Decay: 100%
Reach
6
Engagement
70
Star Power
10
Duration
32
Cross-Platform
20
Polarity
50
Industry Impact
50

The timeline

  1. Violent anti-deepfake post published on Bluesky

    User kinkel19561 posted Dutch-language message urging physical mutilation of deepfake pornography creators

The full record

Sources & methodology

Every claim above traces to these primary items. How we score →

What's being under-reported

No defender-side coverage yet

The critic side is sourced here; no defending voice has been captured yet.

  • Coverage: 1 social post, 0 news-outlet items.
  • Voices: 1 critic, 0 defenders.

The forecast

Platforms will likely remove the post for violent incitement while facing criticism for appearing to protect abusers, because inconsistent enforcement erodes trust among victim advocates.

Forecast, not fact — an editorial estimate we score when this resolves.

You're up to date

That's the complete picture as of — nothing more to know right now. We'll update this page the moment it changes.