#kde

203 posts · Last used 9d

I'll be talking about free open source desktop software, sovereignty and #KDE at @oscl@mastodon.opencloud.lu 2026. Come and see me! Or not! There are 11 (!) tracks to choose from at #OSCL26 and you can see great insightful talks by @Gina@fosstodon.org, @zacchiro@mastodon.xyz, @_elena@mastodon.social, @carlopiana@mastodon.uno, @rriemann@chaos.social, and more. https://conference.opensource.lu/
33
0
15
0
Here is the other thing, a lot of #FLOSS projects are taking in a lot of #LLM generated code now in the grey-limbo of no policy. AND the longer projects take to ban it, the less likely they are to ever ban it. "No policy" means tacit acceptance is the status quo for a lot of projects. The time for #KDE to ban LLM generated code has kind of passed. I just don't believe it's possible for them. Their unlikely to reverse commits like this. https://www.phoronix.com/news/AMD-More-HDR-KWin-Claude-Code AND even if banning it, didn't require reversing prior commits like that; the tacit acceptance of this kind of code, while there is no policy serves to normalize LLM generated code in the project over time. If you need your DE to be llm-code free; time to move on from KDE. #antiAI #noAI
5
4
2
0
We are going to see lots of open source projects deciding on how to deal with fascists within their community. After decades of conditioning people to view tech as a neutral, politics-free zone, very often they will make the wrong decision. You cannot have an open and welcoming community if you allow fascists or discuss that they might actually be “merely” racists or find other excuses not to take a decisive action. See paradox of tolerance. If projects are being forked over this matter, I guess all we can do is embracing the fork. #KDE
113
5
80
0
Replying to
say @davidgerard@circumstances.run , are you still blocked by the #KDE Masto account? because they seem to be expanding their block list today. the offending comment that lead to the block seems to have been me explaining to someone in KDE's comments that yes, svin is in fact a person who deserves the label "Nazi". great job on the "inclusivity" value of your manifesto y'all! truly the logical next step after dismissing the anti-AI parts of the KDE community as an external pressure campaign was to double down.
24
3
14
0

RE: https://floss.social/@kde/117322549131682125

I signed and shared a petition that asked for KDE to stay “AI”-free. Somebody reported me to my own instance over it, and I was puzzled as to why, as it seemed innocuous enough. Well I think I found why: it’s a term used in a post on the subject, shared by the official KDE account.

“19. Someone else outside of KDE set up https://kdeforpeople.com in an attempt to brigade (edit: I have been convinced that this was too strong a word to use here) pressure KDE into banning LLMs.

  1. A bunch of people signed onto it, almost none of whom are known KDE contributors (I see one person I know in there).”

Well, saying I am disappointed would be putting it lightly. Those nefarious “people outside of KDE”, asking the project to consider banning LLM? There is a name for it: we are called “users”. But apparently you are not allowed a voice if you are not part of the inner circle. Promoting KDE and reporting the occasional bug is not enough. We can’t comment on https://invent.kde.org/ as it is for devs only, but it seems like we are not supposed to be vocal about our concerns on a purpose made website either. What are we supposed to do then? Just stay silent, like good consumers? Are we not part of the community too? I guess I was just stupid to think that, in a free software project that has long claimed to be community-driven, non-developers were allowed to have opinions about the tools they use and their social impact.

#KDE

Quoting
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.
Open quoted post
26
0
18
0
I just published A FAQ concerning the current KDE situation. Here I explain some things that I know about the current controversies going online. It still needs revisions on the matter of community voices, but that will be for later. This 13 min read post took several hours across two days to write, and I need some time off before revising it further. #KDE
16
1
12
0
"A proposal to make KDE an 'AI-native' desktop has gone down like a house on fire: screams, flames, people running for safety. There may be no survivors." The Register: Talk of AI in KDE sets the community ablaze https://www.theregister.com/software/2026/09/24/talk-of-ai-in-kde-sets-the-community-ablaze/5298854 @theregister@geeknews.chat @lproven@social.vivaldi.net #Linux #KDE
2
1
2
0

RE: https://floss.social/@kde/117322549131682125

things this post does:

  1. places the blame on the KDE community
  2. dismisses kdeforpeople.com as an external pressure group
  3. dismisses opinions of non-direct contributors as irrelevant

this this post doesn't do:

  1. apologise
  2. mentions that the person who escalated this shitstorm was a literal nazi
  3. call the pro-AI presentation a pressure campaign like it did with kdeforpeople.com
  4. make literally any lessons for the future
  5. apologise!!

i no longer consider #KDE a community project.

Quoting
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.
Open quoted post
142
0
91
1
I have created this very simplistic qml only app for my #postmarketos phone to test how qt/kde works with gps. I can get accurate position data - like in other gps-consuming apps, but I can't figure out how to get the sattelite information, at least not yet. I use the qml SatteliteSource object, but it is not valid using geoclue type, and I have no idea what to put as source for the nmea type, even though nmea is supported by my modem. #plasma_mobile #op6t #geoclue #nmea #modemmanager #kde
5
4
1
0