Flathub has replaced its blanket ban on AI-generated applications with a disclosure requirement. Reviewers can still reject submissions, and manifests remain off-limits for AI-generated content.

  • Destide ( sirico@feddit.uk ) 
    link
    fedilink
    English
    arrow-up
    4
    ·
    6 hours ago

    By and large flathubs metadata has allowed for pretty transparent overviews. Stick the same filtering that safe and unsafe containers have and everyone retains a clear choice.

  • Wilmo ( wilmo@lemmy.ml ) 
    link
    fedilink
    English
    arrow-up
    34
    ·
    10 hours ago

    I think they should just create a policy where unmaintained software gets removed? Or flagged where it’s easy to filter out.

    Most AI slop just gets abandoned, but a real developer who wants to maintain FOSS software long term with some AI assistance is quite a different thing.

    • Linkerbaan ( linkerbaan@lemmy.ml ) 
      link
      fedilink
      English
      arrow-up
      2
      ·
      3 hours ago

      An unforeseen consequence from AI Slop is that normal people can now create quite handy software for niche use cases, but the barrier to entry is so low that those people often abandon it quickly too. Rather than security risks, abandonedware is starting to become a bigger problem.

      • Sina ( Sina@beehaw.org ) 
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 hours ago

        I don’t know about other normal people, but I’m certainly actively maintaining my own vibecoded apps as long as it’s affordable to do so. By that I mean they give me the niche functionality I want & new features are not added anymore, but if a pillow or pyqt update breaks my app, I may figure out how to fix it even on my own.

  • Probably the right decision given there’s no way to truly tell what level of AI generation or effort within the project itself with AI has taken place.

    I understand the willingness to ban low effort low quality one shot projects, but given most software nowadays incorporating some level of LLMs, I can’t ever see a blanket ban working out anywhere.

    • starsoaked_lily ( starsoaked_lily@lemmy.ml ) 
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 hours ago

      that’s like saying that because we can’t all always 100% tell if someone is cheating at an online game we should forget about banning cheaters - you can prohibit a behavior you aren’t always able to sus out and use a combination of detection heuristics and making that behavior unwelcome (i will say i believe the correct policy is to label projects which discernibly use llms rather than banning them)

  • eremophila ( eremophila@lemmy.zip ) 
    link
    fedilink
    arrow-up
    14
    ·
    16 hours ago

    This suggests that it has to be disclosed to the reviewers, which is a good thing, but how will end users be made aware?

    I only use 6 flatpaks (due them not being available in the arch official repo’s) and I get them via a gui package manager. I’m assuming I am going to have to modify how I do this for any future installs, and check my existing ones, but then what about future releases/updates?

    A ‘no ai’ swtich/toggle would be swell.

      • eremophila ( eremophila@lemmy.zip ) 
        link
        fedilink
        arrow-up
        20
        ·
        15 hours ago

        Yes, I’m also aware that is redundant to this conversation. There is no reason for decent people to just give up on decency just because one layer (even the top layer) of something is f*cked up.

        If people gave up that easily, we would all be working in coal mines 14 hours a day, living in trash societies, with slave labour, and trash governments… oh

        Hopefully someone forks the kernel, and there is an increase in anti ai distro’s, de’s etc.