conv.

All stories
TechActive today · day 4

KDE's AI policy attempt derailed by outside backlash, maintainer says

A KDE developer's effort to restrict LLM usage in the project sparked controversy and was shut down by critics outside the community.

What to know

  • KDE maintainer Nate Graham drafted more restrictive LLM usage guidelines to combat low-quality AI-generated code submissions, but the effort was shut down by critics outside the project who opposed any pro-AI policy.
  • Graham acknowledges both legitimate concerns about harmful LLM misuse and the value of responsible expert use, defending his attempt as a compromise that would have tightened—not loosened—AI restrictions.
  • The public backlash created a damaging conflict Graham says derailed internal consensus-building, forcing him to apologize while appealing for more constructive future policy discussions.

The dispute Whether Graham's guidelines would have tightened or loosened AI restrictions, and whether outside intervention was justified interference or necessary opposition to a manipulative process. · positions read across 8 posts and comments

some voices

The policy effort was legitimate governance derailed by external bad-faith actors.

  • “Nate Graham's first-hand, blow-by-blow account on what went down… some of the details my clarify some of the points.”

    kde@floss.social · Mastodon ↗
many voices

The policy attempt was a deceptive effort to legitimize AI use disguised as consensus-building.

  • “the attempt to ram through a pro-slop KDE policy just got closed yet again”

    davidgerard@circumstances.run · Mastodon ↗

“If I or someone else tries again to propose a set of usage guidelines that restrict inexpert usage of LLMs, with the goal that KDE receives fewer of the AI slop merge requests that are burning people out, please don't make things worse.”

Nate Graham · Pointiest Stick blog ↗

Nate Graham KDE maintainerOutside AI critics Community observers

KDE's AI policy attempt derailed by outside backlash, maintainer says
invent.kde.org

How it unfolded 4 developments, newest first · click a bar or a number to jump posts

Peak 1 piece in one hour at Sep 20, 3 AM; 10 pieces over 4 days (1 article · 9 posts) Sep 20, 3 AM — 1 piece · 1 post — Mastodon 1Sep 20, 4 AM — quietSep 20, 5 AM — quietSep 20, 6 AM — 1 piece · 1 post — Mastodon 1Sep 20, 7 AM — quietSep 20, 8 AM — quietSep 20, 9 AM — quietSep 20, 10 AM — quietSep 20, 11 AM — quietSep 20, 12 PM — quietSep 20, 1 PM — quietSep 20, 2 PM — quietSep 20, 3 PM — quietSep 20, 4 PM — quietSep 20, 5 PM — quietSep 20, 6 PM — quietSep 20, 7 PM — quietSep 20, 8 PM — quietSep 20, 9 PM — quietSep 20, 10 PM — quietSep 20, 11 PM — quietSep 21, 12 AM — quietSep 21, 1 AM — quietSep 21, 2 AM — quietSep 21, 3 AM — quietSep 21, 4 AM — quietSep 21, 5 AM — quietSep 21, 6 AM — quietSep 21, 7 AM — quietSep 21, 8 AM — quietSep 21, 9 AM — quietSep 21, 10 AM — quietSep 21, 11 AM — quietSep 21, 12 PM — quietSep 21, 1 PM — quietSep 21, 2 PM — quietSep 21, 3 PM — quietSep 21, 4 PM — 1 piece · 1 post — Mastodon 1Sep 21, 5 PM — quietSep 21, 6 PM — quietSep 21, 7 PM — quietSep 21, 8 PM — quietSep 21, 9 PM — quietSep 21, 10 PM — quietSep 21, 11 PM — quietSep 22, 12 AM — quietSep 22, 1 AM — quietSep 22, 2 AM — quietSep 22, 3 AM — quietSep 22, 4 AM — quietSep 22, 5 AM — quietSep 22, 6 AM — quietSep 22, 7 AM — quietSep 22, 8 AM — quietSep 22, 9 AM — quietSep 22, 10 AM — quietSep 22, 11 AM — quietSep 22, 12 PM — quietSep 22, 1 PM — quietSep 22, 2 PM — quietSep 22, 3 PM — 1 piece · 1 post — Mastodon 1Sep 22, 4 PM — quietSep 22, 5 PM — quietSep 22, 6 PM — quietSep 22, 7 PM — quietSep 22, 8 PM — quietSep 22, 9 PM — quietSep 22, 10 PM — quietSep 22, 11 PM — quietYesterday, 12 AM — 1 piece · 1 post — Mastodon 1Yesterday, 1 AM — quietYesterday, 2 AM — quietYesterday, 3 AM — quietYesterday, 4 AM — quietYesterday, 5 AM — quietYesterday, 6 AM — quietYesterday, 7 AM — quietYesterday, 8 AM — quietYesterday, 9 AM — quietYesterday, 10 AM — quietYesterday, 11 AM — quietYesterday, 12 PM — quietYesterday, 1 PM — quietYesterday, 2 PM — 1 piece · 1 article — Mastodon 1Yesterday, 3 PM — 1 piece · 1 post — Hacker News 1Yesterday, 4 PM — 1 piece · 1 post — Mastodon 1Yesterday, 5 PM — quietYesterday, 6 PM — 1 piece · 1 post — Mastodon 1Yesterday, 7 PM — quietYesterday, 8 PM — 1 piece · 1 post — Mastodon 1Yesterday, 9 PM — quietYesterday, 10 PM — quietYesterday, 11 PM — quiet 1234
Sep 21Sep 22yesterdaynow · 12:58 AM ET
  1. 4

    KDE's official account shares Graham's account

    The official KDE Mastodon account amplifies Graham's post, urging readers to carefully review the full context before forming conclusions.

    • kde@floss.social

      Nate Graham's first-hand, blow-by-blow account on what went down: https:// pointieststick.com/2026/09/23/ kde-and-ai-and-you-and-me/ Not to do the click-baitey thing, but some of the details my clarify some of the points. Please read through the whole thing carefully to better understand the situation and why what was done was done.

      kde@floss.socialMastodon7h ago370▲view on Mastodon ↗
    2 more of the top 3 · 3 posts in this stretch
    • mos_8502@studio8502.ca

      How are we expected to handle a technology that is: Very powerful Genuinely useful for various things Dangerous, de-skilling, and/or addictive in the wrong hands Full of really bad externalities Broadly available worldwide at effectively zero cost It’s like 100 billion toaster-sized nuclear reactors dropped from the sky one day. The very least you…

      mos_8502@studio8502.caMastodon3h agoview on Mastodon ↗
    • colindean@mastodon.social

      https:// pointieststick.com/2026/09/23/ kde-and-ai-and-you-and-me/

      colindean@mastodon.socialMastodon5h agoview on Mastodon ↗
    all of them →
  2. 3

    Graham clarifies intent and apologizes for the conflict

    Nate Graham publishes a detailed account explaining he was attempting to craft more restrictive LLM guidelines and apologizes for the resulting public controversy. He acknowledges legitimate concerns about LLM misuse while defending responsible AI use by experts.

    “I accidentally triggered an online shitstorm in the process of trying to craft a set of more restrictive LLM usage guidelines for KDE.”
    — Nate Graham
    • Sylvhem@eldritch.cafe

      If you use KDE and don’t like so-called “artificial intelligence”, you may want to sign that text, calling for an “AI” ban in KDE Plasma. https:// kdeforpeople.com/ # KDE

      Sylvhem@eldritch.cafeMastodon1d ago40▲view on Mastodon ↗
    1 more of the top 2 · 2 posts in this stretch
    • billyjoebowers@mastodon.online

      RE: https:// mstdn.plus/@markgl/11731815067 3291200 I would love for @KDE to take a stand and block AI code. Plasma is my DE of choice.

      billyjoebowers@mastodon.onlineMastodon23h agoview on Mastodon ↗
    all of them →
  3. 1 day quiet
  4. 2

    Outside critics shut down the policy attempt

    The policy discussion was closed after critics outside KDE discovered and mobilized against what they characterized as a 'pro-slop' policy effort.

    “the attempt to ram through a pro-slop KDE policy just got closed yet again…”
    — davidgerard@circumstances.run
    • davidgerard@circumstances.run

      lol, the attempt to ram through a pro-slop KDE policy just got closed yet again because people found out about it https:// invent.kde.org/plasma/plasma-w orkspace/-/work_items/187#note_1648917

      davidgerard@circumstances.runMastodon2d ago233▲view on Mastodon ↗
  5. 1 day quiet
  6. 1

    KDE policy discussion opens on LLM usage

    A work item appears on KDE's project management system discussing guidelines around large language model usage, sparking debate about whether the community is being manipulated.

    1. first by Mastodon, 9h ago

    • mawhrin@circumstances.run

      (you can look at kde right now and watch how the culture of politeness and consensus is being literally used to fabricate a consensus. sadly, i don't think there's a simple good solution to handle this type of hackery.)

      mawhrin@circumstances.runMastodon3d agoview on Mastodon ↗
    1 more of the top 2 · 2 posts in this stretch
    • thomholwerda@exquisite.social

      🤨 https:// invent.kde.org/plasma/plasma-w orkspace/-/work_items/187

      thomholwerda@exquisite.socialMastodon3d agoview on Mastodon ↗
    all of them →

What people are saying 0 voices from 0 sites · best of 8 · verbatim