Personal opinion: Nathan seems to be really side-stepping a lot of concerns brought of up in the comments there. And referring to people coming together collectively in an open-letter when virtually all other channels are closed as ‘brigading’ is… Not cool. Edit: he retracted the use of brigading.

  • A_norny_mousse@piefed.zip
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 day ago

    Earlier I already noticed OP glossing over nuance when commenting about this.

    Reading the blog linked here I really don’t see any issue, esp. not of the “drunk with power” kind which seems to be a go-to for certain people as soon as something icky comes up.
    Being “leader” of an OSS project is not fun. It’s like herding cats. And the money probably isn’t so hot either.
    Your skepticism rocks, but please attack actual rich assholes instead.

    AFAICS so far, KDE likes to discuss things even more than other OSS projects, including public brainstorming.

    I hope they come to a good policy against AI, which is problematic not only from a developer’s POV.
    So far KDE still seem to be in the brainstorming phase though.

    To round off, some key parts (which I fear will get misquoted/overblown) from this very article:

    • Everyone agreed it (AI slop) was a problem, and that we don’t want that crap.
    • There was less certainty about the best way to handle it socially.
    • Several wished for an official policy so we didn’t all have to figure it out on our own. I proposed a set of draft guidelines making it quite clear that slop merge requests are unwanted, and can be ignored or closed. It received a generally positive reception.
    • Another KDE developer requested that we workshop it somewhere more modern and capable.
    • I got busy and didn’t do so.
    • Several weeks later, various people on the internet discovered that a talk proposing “a lovable, sovereign, AI-native KDE” had been accepted at Akademy 2026 and created drama around it. [ Already then Nate replied that this was just one speaker of many and in no way representative of KDE as a whole ]
    • Akademy happened, and the talk was given to what I’m told was a fairly chilly reception. The next day, a workshop was held about the topic, also receiving a chilly reception.
    • Realizing this topic was not going away, later that day I re-opened a second draft of my LLM guidelines on invent.kde.org. KDE contributors began to discuss the draft proposal.
    • Two people unknown to any KDE contributors appeared and began fighting with one another about the broader topic of the morality of AI, not the proposed guidelines.
    • One of those people exposed the other person’s odious Twitter posts in an effort to discredit them.
    • Later, the identity of the doxxed exposed person was verified, and they were also banned for their conduct outside of KDE being so unacceptable that people inside KDE did not want to associate with them.
    • Someone else outside of KDE set up https://kdeforpeople.com/ in an attempt to pressure KDE into banning LLMs. A bunch of people signed onto it, almost none of whom are known KDE contributors (I see one person I know in there).
    • The topic was picked up on social media and the press with… varying levels of accuracy.
    • The draft proposal was removed and the whole topic hidden.

    It wasn’t my intention to leave anything important out here.

    Downvotes, here I come!

    • Eldritch@piefed.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      17 hours ago

      Yes OP has been daily Doom posting for the last month or so. I daily drive plasma. And have been keeping an eye on things. But I have not seen anything unreasonable or concerning. I find Brody Robertson has a decent insight into some of these things and explains himself relatively well on these topics.

      It’s undeniable that AI has been trained unethically. And certain instances are being deployed unethically. Similar could be said for certain vaccines. We didn’t ban use of them however. Unfortunately the cat is out of the bag when it comes to ethical training. AI is now a tool and it is widespread regardless of whether or not we like it. The best we can hope to do is to push for accountability going forward. Supporting everyone. And punishing those who act unethically.

      People need to make the connection that the problem with AI replacing people. Isn’t ai. It’s that wealthy capitalists are trying to cut people off from a means of supporting themselves. I.E the problem is capitalism. The problem is always capitalism. The problem has always been capitalism and the system that came before. If we provided proper social safety nets and social support for everyone in society. No one would care if AI replaced them at some menial soul-sucking job. If they could live and pursue their passions instead they would all be glad to.

    • ProdigalFrog@slrpnk.netOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      1 day ago

      The way Nate is framing the original intent of the proposal, that KDE was swamped with AI slop and they just needed a quick policy that would allow them to comfortably reject it, doesn’t seem quite accurate. If that was all they needed, it seems like it would’ve been quite easily to propose an ad-hoc policy of allowing maintainers to reject suspected AI slop PRs at will, which would solve the immediate problem while allowing them to gather more feedback on a ‘proper’ policy. Adding a provision to not require any AI disclosure doesn’t help with the stated goal of just wanting a way to easily reject slop.

      I’ve read the positions of some of the developers involved in the proposal thread on other platforms, and most have made it very clear that they are pro-AI (I do not include Nate among them, as he has stated he actually dislikes AI and doesn’t use it). Among that group, the concerns about AI ethics and their use are, ultimately, of secondary concern over the prospect of increased productivity and time savings. That inclination is what resulted in so little credence given to the people raising concerns against it in the proposal thread (it was clear that the concept of not accepting AI code, or even just limiting it to self-hosted models, was not on the table from the outset).

      Nate is clearly distressed from the negative reaction the proposal has caused, and I can sympathize with that. However, from what I’ve read of his responses on his linked blog, IMHO it is mostly damage control, and still isn’t addressing the main concerns people had about the original policy proposal. When people point out the copyright, environmental, and ethical issues, Nate will acknowledge those, but insists that the original proposal, by virtue of it allowing them to quickly reject obvious AI code, would’ve been an improvement (despite it also giving the provision that AI use didn’t have to be disclosed, essentially meaning that those skillful enough to make it not obvious will still be perpetuating the ethical, environmental, and copyright issues, but just in the dark without anyone knowing the severity).

      In the linked blog post, many of the comments are saying that KDE effectively closed down most avenues to provide feedback on the proposal, thus leaving them with essentially the only option of making the KDE For People open letter, as otherwise it appeared that any public dissent against a permissive AI policy was ultimately going to be dismissed as the Pro-AI group decided on a policy behind closed doors.

      Their justification for planning to make it a closed door decision was two people in the proposal thread, both of which easily could’ve been removed from the thread, or the thread closed to developers only, and their discussion could’ve continued without any difficulty. I personally don’t believe their justification, as it clearly seems like it was closed and ultimately made hidden to avoid the public relations fallout the main discussion was having for being so dismissal of the AI concerns brought up.

      I invite anyone curious to read the blog and the comments below, and come to their own conclusion.

      • A_norny_mousse@piefed.zip
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        3 hours ago

        edit

        I have since seen the proposal of a KDE AI policy - and no thanks to the “Nate Graham is bad” party in this thread - and decide to rewrite some of my comments.

        • I personally believe that being against AI goes beyond just code. It’s ethical, political, whatevrer you want to call it. AI sucks, quite literally the life out of people and the ground they’re living on.
        • Unfortunately most FOSS projects concentrate more on code quality etc. in their AI policies, not on these overarching issues.
        • KDE seems to be a little late to the party wrt AI policies written out
        • Their proposal is just that atm and personally I applaude the transparent decision making process
        • There are too many people who are understandably outraged about the whole issue, but go about opposing it in a bad way, distorting or obfuscating facts - as seen right here
        • In the extreme this becomes indistinguishable from trolling and it’s totally understandable that blog or repo owners shut the comment section down
    • esc@piefed.social
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 day ago

      KDE right now has a very reasonable position, but of course being utilitarian and reasonable wouldn’t be ever enough for purists that will be throwing shit on the project regardless of what policy will be accepted in the end (OP is already doing it, some other people on fedi as well).

      • PokerChips@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        5 hours ago

        By your account I guess Cheaters in college should have used the defense of professors that caught them as “purists” … Get the FO of here with that.