Kiriko

KDE bans user calling out racism, antisemitism and misogyny but not the perpetrator. During the AI policy discussion on invent.kde.org/plasma/plasma-workspace/-/…/187 someone called a KDE contributor out for their bigotry. KDE banned the person calling him out and removed all the comments. archive.ph/6YccJ#note_1648724 (no other archive available) invent.kde.org/sweetluna (blocked user) invent.kde.org/svin I guess it’s official. Fascism is allowed. Calling it out is not.

"Proposed KDE LLM guidelines" is now officially locked Some of the worst LLM takes I’ve seen in a while. I’ve never thought FLOSS would be taken over by proprietary torment nexuses so fast. The discussion will probably continue behind closed doors, so the public has no way of knowing who says what and corporations have their way easier. And someone got exposed for being a Nazi.

What would it take? A lovable, sovereign, AI-native KDE I was very excited about this year’s Akademy (KDE’s anual conference), until I saw this… Linux desktops won’t save us. A talk in three parts, building towards a vision for a sovereign desktop in 2026 (and a look back). Loved. In 2003, together with Eva Brucherseifer, Jan’s company relevantive ran the first large-scale usability study of the Linux desktop on behalf of decision-makers considering migration. KDE 3.1 on SuSE was tested by 60 office workers with no prior Linux experience; 87% enjoyed working with it, 80% estimated they could reach professional competence within a week. The Linux desktop wasn’t a usability disaster — but realising its potential required deliberate configuration, honest naming, and treating migration as a human-resources problem, not a technical one. The findings shaped a decade of OpenUsability work inside KDE. They are, awkwardly, almost entirely still applicable. We’ll look at what stuck, what didn’t, and why “lovable” — not merely “usable” — is the bar today, and why getting it right cuts the cost and risk of every migration discussion that follows. AI-native. A desktop that loves you back has to know you. Personal AI has crossed the threshold where the desktop itself can be compiled per user, per device, per moment, from a small portable model of the user — what we are sketching as Kadai: an encrypted, vendor-agnostic personal kernel from which Plasma assembles each Activity. Plasma is uniquely well-fit for this — Activities, Plasmoids, the existing scripting surface — but a handful of upstream changes (declarative reconciliation, per-widget capabilities, richer Activity metadata) would turn KDE into the first shell that treats AI as infrastructure rather than as a chat box bolted to the side. Sovereign. Once a user owns their model and their tools, the same question returns at institutional scale. EU institutions, member countries, and a long tail of organisations are openly asking what a credible, non-colonialising desktop stack looks like. No project carries this alone — a sovereign desktop is an ecosystem question. KDE is uniquely positioned as the shell, the integration layer, the experience; but filesharing belongs with Nextcloud, the browser with Firefox, the office suite with … The last third of the talk is about what KDE’s partnership surface could look like — outward, to industry and public administration, and sideways, to the allied open-source projects that already do the rest of the work better than anyone could redo it. Who owns that surface, where it lives, what KDE e.V. would need, what not to build. Sovereignty, from this angle, is just lovability and AI-ownership scaled up to the organisation: the user not owned by a vendor, the institution not owned by a foreign supplier — and the stack not owned by anyone, because the right partners hold the right pieces. This talk is an invitation — from peple with a long arc inside this community — to take a serious swing at the question the 2003 study posed and never quite resolved: what would it take for KDE to be the desktop people actively choose, not just the one some of us settle for? Attendees will leave with: a concrete proposal (KaDAi) to react to or tear apart, a clear set of asks the project could direct at Plasma maintainers, and the framing for a sovereignty conversation that KDE is uniquely positioned to lead.

Unfortunately it’s not a single instance. There was a thread on their forums I had notifications on for. It was about banning AI. It ended up locked. Someone posted some links to slop code in KDE, I thought it got locked because they made up their minds, turns out they jumped off the fence towards AI… discuss.kde.org/t/…/164

I haven’t been up to date with all of them though from what I remember seeing: COSMIC: system76 employees seem to be against AI and the company doesn’t force them to use it www.reddit.com/r/pop_os/comments/…/n1hu9ft/ one of the main COSMIC people’s linux alternative OS banned them completely www.phoronix.com/news/Redox-OS-March-2026 XFCE: the wayland version is completely vibecoded and done by one of the main XFCE people www.spurint.org/journal/2026/07/llms-and-xfwl4 GNOME: some applications and libraries have banned it completely (the image viewer, libadwaita, calendar and others) discourse.gnome.org/t/…/27327 vibecoded extensions are banned theverge.com/…/gnome-linux-ai-shell-extensions-ba… and vibecoded apps are not allowed on their circle thingy www.phoronix.com/news/GNOME-Circle-No-AI-Slop but there’s no project-wide ban as far as I can tell Mint/Cinnamon: no ban and one of the main mint developers maintains an applet for claude usage github.com/linuxmint/…/claude-usage%40mtwebster though I cant see any slop on the repos themselves lxqt: AI is explicitly allowed as long as it’s documented github.com/lxqt/lxqt/wiki/Contributing-code#usage… github.com/lxqt/lxqt/discussions/2889

Apart from the proof @ProdigalFrog@slrpnk.net posted, bee_fumo was also live-posting the whole thread on twitter x.com/bee_fumo/status/2102032995695645121

He was live-posting the whole thread x.com/bee_fumo/status/2102032995695645121

That whole thread is awful. Just awful. It looks like only 2-3 KDE devs pushback and the rest are thumbs-uping pro-AI points. Claims that LLMs are fine for the environment… Then someone got exposed for racism and misogyny among many other -isms and they claim that some of the participants in that discussion LIKE those posts… YIKES. It all makes sense why they are dying on the framework hill.

Noctalia used to have a handful of claude commits, they seem to have been force pushed out or similar. Hopefully out of change in mind.