Open Slopware - Free/Open Source Software tainted by LLM developers/developed by genAI boosters, along with alternatives.

The intention of this list is to raise awareness of AI/LLM usage in popular open-source software. Provided below is an informed set of AI-free alternatives for users and developers to consider should their ethical boundaries be crossed or tolerance for risk be exceeded. This list is not a resource to be used for the harassment of other open-source developers. If you wish to advocate for the cessation of use and/or removal of AI-generated code from another project, we ask that it be done respectfully and constructively (and do not mention this list).

For more information on why we think this list matters, please see Why not LLMs?.

Want to add, update, or remove a project listed below? Check out our Contributing Doc.

See a project on here that you love, and wish wasn’t on here? Check out our No AI Request Template.

Ready to fork a project to introduce a No AI policy? Check out our How to Slop Free Fork Guide.

Any other questions? Please check out our FAQ, and if your question isn’t answered there, please feel free to start a Discussion.

  • pivot_root@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    4 months ago

    I don’t like AI being jammed into everything as much as the next person, but some of these are just ridiculous.

    1. Knocking Firefox for AI functionality, but not Chrome? Chrome downloads an entire 4 GB local model without even telling you yet still sends queries to Google’s hosted models.

    2. Recommending ls as a replacement for eza is a stupid and redundant suggestion. Nobody learns to download eza first; eza is installed as a replacement for ls because it provides more features than coreutils ls. The cherry on top is that if you use a distro with uutils, your ls is also on this list.

    3. Good luck to any purist with replacing curl with wget. libcurl is everywhere and in everything.

    4. “Linux Kernel”

    5. Both LLVM and gdb. I guess we’re going back to the days of printf debugging, boys.