alternatives update - you don't have to have a perfect 1:1 alternative

### Description of Changes

This PR adds LaSuite Docs as tainted, and adds alternatives to the category with Calligra and CryptPad

Reviewed-on: https://codeberg.org/ethical-foss/open-slopware/pulls/1101
Reviewed-by: Ethical FOSS admin <ethical-foss-admin@noreply.codeberg.org>

.forgejo/issue_template/collaborate-with-me.yaml

@@ -1,7 +1,7 @@
 name: Call for Collaborators for a New AI-free Project
 about: Put out a call for collaborators on a new or recently forked project that has an explicit No AI policy. (must have a code of conduct)
-title: '[Call for Collaborators]: project name here'
-ref: 'main'
+title: "[Call for Collaborators]: project name here"
+ref: "main"
 labels:
   - call-for-collaborators
 body:
@@ -9,7 +9,7 @@ body:
     attributes:
       value: |
         Thanks for helping to make the world a bit more AI free 💙
-        The idea here is to request help with forking or rewriting a currently tainted project.
+        The idea here is to request help with any slop-free project, including forking or rewriting a currently tainted project.
 
   - type: input
     id: project
@@ -28,7 +28,7 @@ body:
   - type: input
     id: language
     attributes:
-      label: Programming Lanaguage
+      label: Programming Language
       description: |
         What programming language will this be primarily written in?
 
@@ -43,9 +43,9 @@ body:
     id: terms
     attributes:
       label: Code of Conduct and Rules for Collaboration
-      description: By submitting this issue, you agree to follow our [Code of Conduct](https://codeberg.org/small-hack/open-slopware/src/branch/main/CODE_OF_CONDUCT.md)
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://codeberg.org/ethical-foss/open-slopware/src/branch/main/CODE_OF_CONDUCT.md)
       options:
-        - label: I agree to follow this project's Code of Conduct
+        - label: I agree to follow this project's [Code of Conduct](https://codeberg.org/ethical-foss/open-slopware/src/branch/main/CODE_OF_CONDUCT.md)
           required: true
         - label: The project I want to collaborate on has a No AI policy banning any and all AI usage
           required: true

.forgejo/issue_template/config.yaml

@@ -3,8 +3,11 @@ blank_issues_enabled: false
 
 contact_links:
   - name: Our Contributing Doc
-    url: https://codeberg.org/small-hack/open-slopware/src/branch/main/CONTRIBUTING.md
+    url: https://codeberg.org/ethical-foss/open-slopware/src/branch/main/CONTRIBUTING.md
     about: Read this to learn how you can contribute to this project ✨
   - name: How to Create a Pull Request
     url: https://docs.codeberg.org/collaborating/pull-requests-and-git-flow/
     about: Learn more about how to create a pull request on codeberg 🩵
+  - name: How to have "tainted" status removed
+    url: https://codeberg.org/ethical-foss/open-slopware/src/branch/main/CONTRIBUTING.md#removal-of-tainted-status
+    about: If you want to know how to get your project (or a project you love) removed from the list, please check out this link.

.forgejo/issue_template/discussion.yaml

@@ -15,16 +15,16 @@ body:
       label: Discussion Topic
       description: |
         Please let us know what you'd like to discuss.
-        Remember that if you already have concrete evidence, you should just open a PR. Pleae don't create an Issue.
+        Remember that if you already have concrete evidence, you should just open a PR. Please don't create an Issue.
         This is also not a place to ask advice on using your own LLMs.
   - type: checkboxes
     id: terms
     attributes:
       label: Code of Conduct
-      description: By submitting this issue, you agree to follow our [Code of Conduct](https://codeberg.org/small-hack/open-slopware/src/branch/main/CODE_OF_CONDUCT.md)
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://codeberg.org/ethical-foss/open-slopware/src/branch/main/CODE_OF_CONDUCT.md)
       options:
-        - label: I agree to follow this project's Code of Conduct
+        - label: I agree to follow this project's [Code of Conduct](https://codeberg.org/ethical-foss/open-slopware/src/branch/main/CODE_OF_CONDUCT.md)
           required: true
-        - label: I have also read the [CONTRIBUTION.MD](https://codeberg.org/small-hack/open-slopware/src/branch/main/CONTRIBUTING.md)
+        - label: I have also read the [Contributing Guidelines](https://codeberg.org/ethical-foss/open-slopware/src/branch/main/CONTRIBUTING.md)
           required: true
           visible: [form]

.forgejo/issue_template/request-for-more-kind-eyes.yaml

@@ -8,21 +8,14 @@ body:
   - type: markdown
     attributes:
       value: |
-        Thanks for helping to make the world a bit more AI frree 💙
-
-  - type: input
-    id: project
-    attributes:
-      label: What project is this for?
-      description: |
-        What external project are you reaching out to?
+        Thanks for helping to make the world a bit more AI free 💙 This issue type is not intended for harassment. Do not use this issue type to be rude to anyone in any repo.
 
   - type: input
     id: link
     attributes:
       label: Link
       description: |
-        A link to your Pull Request, Issue, Discussion, forum post, mailing list, etc where you've requested clarification on an AI policy.
+        A link to your Pull Request, Issue, Discussion, forum post, mailing list, etc where you've requested clarification on an AI policy. You must provide a link to where you're currently discussing an AI policy.
 
   - type: textarea
     id: additional-info
@@ -35,7 +28,9 @@ body:
     id: terms
     attributes:
       label: Code of Conduct
-      description: By submitting this issue, you agree to follow our [Code of Conduct](https://codeberg.org/small-hack/open-slopware/src/branch/main/CODE_OF_CONDUCT.md)
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://codeberg.org/ethical-foss/open-slopware/src/branch/main/CODE_OF_CONDUCT.md)
       options:
-        - label: I agree to follow this project's Code of Conduct
+        - label: I have read the full description of this issue type [here](https://codeberg.org/ethical-foss/open-slopware/src/branch/main/CONTRIBUTING.md#more-kind-eyes)
+          required: true
+        - label: I agree to follow this project's [Code of Conduct](https://codeberg.org/ethical-foss/open-slopware/src/branch/main/CODE_OF_CONDUCT.md)
           required: true

.forgejo/pull_request_template.yaml

@@ -0,0 +1,27 @@
+name: pull-request
+about: Submit a PR
+ref: 'main'
+body:
+  - type: input
+    id: description
+    attributes:
+       visible: [content]
+       label: Description of Changes
+       description: Include a description of what you're changing and why. Remember, anything here will also show up in the commit when we squash and merge this PR.
+       placeholder: This PR (Updates/Adds/Removes/Improves) (Name of Section / Project) As (Tainted/An Alternative)
+
+  - type: checkboxes
+    id: terms
+    visible: [form]
+    attributes:
+      label: Docs have been read
+      description: By submitting this PR, you agree to the following
+      options:
+        - label: I agree to follow this project's [Code of Conduct](https://codeberg.org/ethical-foss/open-slopware/src/branch/main/CODE_OF_CONDUCT.md)
+          required: true
+        - label: I have also read the [Contributing Guidelines](https://codeberg.org/ethical-foss/open-slopware/src/branch/main/CONTRIBUTING.md)
+          required: true
+        - label: I have also read the [Style Guide](https://codeberg.org/ethical-foss/open-slopware/src/branch/main/STYLE.md)
+          required: true
+        - label: If adding tatinted software, I have provided either the last untainted version/commit OR an alternative for all new entries in this PR. See about exceptions in the Contributing/Style guides.
+          required: true

.gitignore

@@ -0,0 +1 @@
+DONT_REFERENCE_ME.md

CODE_OF_CONDUCT.md

@@ -3,13 +3,17 @@
 - No racism.
 - No xenophobia.
 - No colorism/featurism.
+- No casteism.
 - No transphobia.
 - No homophobia/queerphobia.
 - No sexism.
-- No albeism.
+- No ableism.
+- No islamophobia, antisemitism, or hatred to anyone based on their religion or lack thereof.
 - No classism.
 - No fascism.
 
+When it comes to bigotry, if you're found to have been broken one of the "No Bigotry" rules, you may not participate here. Your software is also disqualified from being listed as an alternative or suggested for the "More Kind Eyes" or "Call for Collaborators" Issue types.
+
 ## On handling bigotry or unsavory content for the purposes of the open-slopware list
 
 It is still worth bringing up if a core repo maintainer has a history of bigotry such as racism, transphobia, etc, if it's in the context of adding an alternative software or something to that nature, but still just be objective, e.g. "We should not add a link to x because it is maintained by a transphobic person, see evidence here" and just leave it at that. We'll take that feedback and reject a pull request or ask someone to modify it if it's relevant for community safety (like ensuring people avoid software maintained by discriminatory people for instance).
@@ -30,11 +34,17 @@ That will display like this:
   homophobic content goes here.
 </details>
 
-Failure to do so will first result in a one time warning and future offenses will be considered a strike.
+Failure to do so will first result in a one time warning and future offenses will be considered a strike. We ask that you do not use the acronym "NSFW" and instead use specific tags such as "nudity" or "discussion of sex" as to be inclusive to all workers.
+
+# No CSAM
+
+We do not allow any form of CSAM, including drawn CSAM: lolicon, shotacon, or "cub" content. Do not submit alternatives that feature sexualized children anywhere in the source code. This includes drawn children. If you need to talk about a someone being accused of something related to CSAM in the context of alternatives in this repo, please use a specific Content Warning as described above.
 
 # On handling rude comments in this repo specifically
 
-If you see someone behaving in appropriately, do not feed their behavior. Tag @vleermuis-admin instead. They will handle it.
+If you see someone behaving in appropriately, do not feed their behavior. Tag @ethical-foss-admin instead. They will handle it.
+
+In some cases, we may delete comments, issues, or PRs if they're encouraging an inappropriate atmosphere e.g. a popular maintainer has come in with an accusatory tone and is actively advertising their followers to come and spam the repo.
 
 ## Strike system
 
@@ -49,8 +59,14 @@ We're going to do a 2 strike rule here with an optional warning. You are out on
 > [WARNING]
 > If you are caught being excessively rude here, especially if you're displaying a form of severe bigotry or bringing an inappropriate tone, we reserve the right to ban you from the repo with no strikes and if necessary, we will report you to codeberg.org.
 
+We do not allow people to debate strikes or bans either for themselves or on behalf of others.
+
 # Be kind or be gone
 
+- Do **NOT** use this repo as a witch hunting device in any direction. You may not reach out on repos, forums, social media, reddit, messaging apps, etc, especially not in a rude way, to maintainers of other repos to harass them and threaten them, especially not with this list. Doing so will result in a ban.
+
+- Do **NOT** mention this list *at all* when reaching out to a project to discuss AI in any way. It only results in putting the maintainers of that project on the defensive, and then the maintainers of *this* repo need to deal with the fallout of that. If you need help with asking for a No AI Policy, consider checking out our [No AI Request Template doc](https://codeberg.org/ethical-foss/open-slopware/src/branch/main/NO_AI_REQUEST_TEMPLATE.md#tips-for-success). You are also free to copy and paste anything from the [Why not LLMs](./why_not_llms.md) file.
+
 - We don't want drive by sarcastic comments.
 
 - No references to bodily fluids (vomit, urine, feces), this includes emojis. It's gross and unproductive.
@@ -63,12 +79,32 @@ We're going to do a 2 strike rule here with an optional warning. You are out on
 
 - This repo is not a substitute for social media. The maintainers do not have the mental health bandwidth to manage such a community.
 
-- Do **NOT** use this repo as a witch hunting device in any direction. You may not reach out on social media, reddit, messaging apps, etc, especially not in a rude way, to maintainers of other repos to harass them and threaten them with this list. Doing so will result in a ban.
-
 - Please do not reach out to the maintainers or collaborators of this repo anywhere but this repo specifically (unless they have given explicit permission to do so). We do not operate our personal email or fediverse accounts as extensions of this repo and will not take feedback there. We need a proper work life balance. Please respect that.
 
+- No complaining about purity rules, "walking on egg shells", etc. If you can't behave professionally here, then please just kindly exit.
+
 This repo is specifically meant for identifying LLM usage in other projects, and coordinating on alternatives. You can also come here to ask others to please help you in chatting with another repo maintainer to sway them away from AI usage. But you need to do all of it *with kindness*. We have no interest in a rage feedback atmosphere here and won't tolerate it. Please consider your words before you hit send.
 
+## Gender Neutral Language
+
+When referring to the people who work on this repo, please use gender neutral language unless you are referring to a specific person who you know the pronouns of. You should prefer to use "they/them/themself/themselves" if you do not know the pronouns of the person you're talking to/about. You can learn more about gender neutral language in the following resources:
+
+- [What are personal pronouns and why do they matter?](https://pronouns.org/what-and-why)
+- [Gender-Neutral Pronouns 101: Everything You've Always Wanted to Know](https://www.them.us/story/gender-neutral-pronouns-101-they-them-xe-xem)
+- [Dictionary of gender neutral language](https://en.pronouns.page/dictionary)
+
+Some example nouns you can use if you don't know the gender of someone:
+- maintainer
+- collaborator
+- author
+- user
+- colleague
+- friend
+- acquaintance
+
+> [!tip]
+> Many people put their pronouns in their profile. If you're unsure, you can check there, and if a person has pronouns listed, use those. If there's no pronouns listed, still default to neutral language as mentioned above.
+
 ## Accessibility
 
 ### Alt Text

CONTRIBUTING.md

@@ -1,8 +1,28 @@
+# Guide to Contributing to this Repo
+
 > [!warning]
-> Before you interact with this repo, please read the [**Code of Conduct**](./CODE_OF_CONDUCT.md)! This is a repo for *nice people only*!
+> Before you interact with this repo, please read the [**Code of Conduct**](./CODE_OF_CONDUCT.md)! This is a repo for *nice people only*! We would also appreciate it if you did not mention this repo on social media or in chats in order to shame a project or community. Do *not* make posts like, "`<project>` should be added to the open-slopware list", especially if you are tagging a maintainer or using a project's hashtag.
+
+* [Contributing Pull Requests](#contributing-pull-requests)
+  * [For Adding or Updating Tainted Software](#for-adding-or-updating-tainted-software)
+    * [Other tips for keeping the repo tidy](#other-tips-for-keeping-the-repo-tidy)
+    * [Criteria](#criteria)
+      * [Alternatives](#alternatives)
+    * [Style guide](#style-guide)
+    * [Removal of "Tainted" Status](#removal-of-tainted-status)
+    * [Adding Alternatives to Tainted Software](#adding-alternatives-to-tainted-software)
+      * [Rules for self submission](#rules-for-self-submission)
+      * [Unqualified Alternatives](#unqualified-alternatives)
+* [Contributing Issues](#contributing-issues)
+  * [Discussion](#discussion)
+  * [More Kind Eyes](#more-kind-eyes)
+  * [Call for Collaborators](#call-for-collaborators)
+* [Contributing to the Why Not LLMs File](#contributing-to-the-why-not-llms-file)
 
 # Contributing Pull Requests
 
+## For Adding or Updating Tainted Software
+
 To contribute to this list, file a pull request adding it to the appropriate category, along with any known alternatives. The pull request must include links to evidence (see [Criteria](#criteria)).
 
 Title the pull request one of the following:
@@ -11,14 +31,17 @@ Title the pull request one of the following:
 - Add `<software-name>` as an Alternative for `<software-name>`
 - Add `<software-name>` as an Alternative for `<category>`
 - Update `<software-name>`
-- Remove `<software-name>`
 
-> [!important]
-> Please do your best to *research alternatives* to the slopware before submitting a PR. It's important to elevate projects that aren't drinking the slop <3
+Please don't link directly to codeberg.org repos, issues, pull requests or commits, as it will alert the other repo that they're being talked about in this list, which could create a negative atmosphere. If you need to link to them, please use a codeblock like this:
 
-**Please make sure to only submit a PR for 1 section at a time, otherwise it is more difficult to coordinate between multiple Issues and PRs.**
+```
+https://codeberg.org/org/project
+```
 
-Other tips for keeping the repo tidy and making sure we don't duplicate efforts:
+> [!note]
+> Please make sure to only submit a PR for *one* section at a time, otherwise it is more difficult to coordinate between multiple Issues and PRs. We have a limit of only 5 *open* PRs per person. Please do not submit more than 5 PRs at a time. When your previous PRs are closed or merged, you are, of course, welcome to submit more, but please do not flood the repo. (There is an exception to this rule if one or more of your open PRs are awaiting upstream feedback.)
+
+### Other tips for keeping the repo tidy
 
 - Search for the software name in the Issues *and* Pull Requests of this repo. (Great minds think alike ❤️)
   - If the software is already reported in an open Issue, but not as a PR, open your PR linking to the open issue with the following description, so the related issue gets automatically closed if the PR gets merged:
@@ -26,60 +49,176 @@ Other tips for keeping the repo tidy and making sure we don't duplicate efforts:
     - Closes #123
     ```
 - If the software is already reported in an open issue and as an open PR leave a comment in the PR with the new or updated evidence(s).
+- When submitting a PR, make sure you're comfortable with the description of the PR being what gets committed. We use the PR description when squashing all commits before merging. We default to sqaushing and merging, so that if the repo has only one commit per PR.
 
-> [!note]
+> [!tip]
 > Don't know how to create a PR? You can learn more about that in the [Codeberg Pull Requests and Git Flow docs](https://docs.codeberg.org/collaborating/pull-requests-and-git-flow/) 🩵
 
-## Criteria
+### Criteria
 
 The criteria for being included in this repository are any of following tags. You can click each one to jump to the definition and acceptable evidence:
 
-- [![AI Functionality](./badges/ai-functionality-yellow.svg)](https://codeberg.org/small-hack/open-slopware#ai-functionality)
-- [![Permissive AI policy](./badges/permissive-ai-policy-orange.svg)](https://codeberg.org/small-hack/open-slopware#permissive-ai-policy)
-- [![AI Code Reviews](./badges/ai-code-reviews-purple.svg)](https://codeberg.org/small-hack/open-slopware#ai-code-reviews)
-- [![AI sponsored](./badges/ai-sponsored-blue.svg)](https://codeberg.org/small-hack/open-slopware#sponsored-by-ai)
-- [![Gen AI 'Art'](./badges/gen-ai-art-dark-yellow.svg)](https://codeberg.org/small-hack/open-slopware#gen-ai-art)
-- [![AI Databroker Usage](./badges/ai-databroker-usage-pink.svg)](https://codeberg.org/small-hack/open-slopware#ai-databroker-usage)
-- [![AI In Issue Tracker](./badges/ai-in-issue-tracker-teel.svg)](https://codeberg.org/small-hack/open-slopware#ai-in-issue-tracker)
-- [![Permits LLM Ingestion](./badges/permits-llm-ingestion.svg)](https://codeberg.org/small-hack/open-slopware#permits-llm-ingestion)
+- [![Vibecoded](./badges/vibecoded.svg)](https://codeberg.org/ethical-foss/open-slopware#vibecoded) (only to be used in extreme cases)
+- [![AI Functionality](./badges/ai-functionality.svg)](https://codeberg.org/ethical-foss/open-slopware#ai-functionality)
+- [![Permissive AI policy](./badges/permissive-ai-policy-orange.svg)](https://codeberg.org/ethical-foss/open-slopware#permissive-ai-policy)
+- [![AI Code Reviews](./badges/ai-code-reviews-purple.svg)](https://codeberg.org/ethical-foss/open-slopware#ai-code-reviews)
+- [![AI sponsored](./badges/ai-sponsored-blue.svg)](https://codeberg.org/ethical-foss/open-slopware#sponsored-by-ai)
+- [![Gen AI 'Art'](./badges/gen-ai-art-dark-yellow.svg)](https://codeberg.org/ethical-foss/open-slopware#gen-ai-art)
+- [![AI Databroker Usage](./badges/ai-databroker-usage-pink.svg)](https://codeberg.org/ethical-foss/open-slopware#ai-databroker-usage)
+- [![AI In Issue Tracker](./badges/ai-in-issue-tracker-teel.svg)](https://codeberg.org/ethical-foss/open-slopware#ai-in-issue-tracker)
+- [![Condones LLM Ingestion](./badges/condones-llm-ingestion.svg)](https://codeberg.org/ethical-foss/open-slopware#condones-llm-ingestion)
+
+Please don't submit social media posts as evidence unless it is a post *by a maintainer of the tainted project* talking about using AI to develop the tainted project. Even then, we'd prefer links to a project's LLM commits in a git forge, AI/contributing policies, or blog posts.
+
+#### Alternatives
 
 Alternatives should not contain any slop as defined by our tagging system above.
 
+Please do your best to *research alternatives* to the slopware before submitting a PR. All new contributions should have *either* an alternative OR a last untainted version/commit, so that people can fork the project. (You can still provide both, but only one is required.) It's important to elevate projects that aren't drinking the slop, or to let people know how best to fork, so we don't all lose hope <3.
+
+Alternatives don't have to be perfect 1:1, as long as you provide a note letting people know the differences. Sometimes the solution to avoiding tainted software is a combination of other tools, and that's OK.
+
+**Exceptions to needing an alternative**
+
+- You've provided a last untainted commit and/or version.
+
+- The tainted project is [![Vibecoded](./badges/vibecoded.svg)](https://codeberg.org/ethical-foss/open-slopware#vibecoded) with no clear alternative yet (this is fairly rare because AI code is often a sum of other stolen code), you don't need to provide an alternative (or last untainted commit).
+
+- There is *already* an "alternative note" section that provides at least one alternative for that section (e.g [local password managers](https://codeberg.org/ethical-foss/open-slopware#local-password-managers))
+
 ### Style guide
 
 When submitting new software to this list, please check out the [style guide](./STYLE.md) to ensure you are conforming to our community agreed upon standards.
 
-## Removal
+### Removal of "Tainted" Status
 
-Any project here may be removed as long as the following become true, *even if prior LLM-authored code remains*:
+Any project here may have the "Tainted" status removed as long as the following become true, *even if prior LLM-authored code remains*:
 
 1. The project establishes a "No genAI" policy, where the core developers commit to no longer using LLMs for developing that project in particular and no longer accepting obvious LLM-authored contributions, and state the policy prominently in their repo.
 2. Any genAI functionality of the project itself is removed in its entirety. "Kill switches" are insufficient.
 3. Any LLM friendly files/folders are either poisoned or removed entirely.
 
-When submitting a project for removal, please include a link to the evidence that they have created a "No genAI" policy. You can also submit PRs to update if a project stops using something like [![AI Code Reviews](./badges/ai-code-reviews-purple.svg)](https://codeberg.org/small-hack/open-slopware#ai-code-reviews), but keeps a [![Permissive AI policy](./badges/permissive-ai-policy-orange.svg)](https://codeberg.org/small-hack/open-slopware#permissive-ai-policy). Updates are always welcome.
+Title the pull request like this:
+> Remove `<software-name>`
+
+When submitting a project for removal, please include a link to the evidence that they have created a "No genAI" policy. You can also submit PRs to update if a project stops using something like [![AI Code Reviews](./badges/ai-code-reviews-purple.svg)](https://codeberg.org/ethical-foss/open-slopware#ai-code-reviews), but keeps a [![Permissive AI policy](./badges/permissive-ai-policy-orange.svg)](https://codeberg.org/ethical-foss/open-slopware#permissive-ai-policy). Updates are always welcome.
 
 Do you see a project on this list that you wish was not on it? Please consider reaching out in a kind way to suggest they implement a No AI Policy. You can check out our [No AI Request Template](./NO_AI_REQUEST_TEMPLATE.md) for inspiration 🙏
 
-# Issues
+> [!note]
+> Age of evidence is not grounds for removal. Example: If agent instructions were added several years ago, but have never been removed, this evidence is still valid and the only way to have the project's tainted status removed is for them to remove those instructions and to put out a No AI policy. We do not make exceptions to this rule.
+
+### Adding Alternatives to Tainted Software
+
+Feel free to submit any software as an alternative provided it is FOSS, has no AI in the code base, and is not associated with hate or bigotry (see [examples of bigotry](https://codeberg.org/ethical-foss/open-slopware/src/branch/main/CODE_OF_CONDUCT.md#no-bigotry)).
+
+Alternatives do not need to be perfect 1:1 replacements for tainted software. Sometimes, the alternative may even be a combination of multiple pieces of software. If something isn't a one to one replacement, please add a note explaining what the differences are.
+
+Projects that have an explicit "No AI" policy can be awarded the [![Anti-AI Policy](./badges/anti-ai-policy.svg)](https://codeberg.org/ethical-foss/open-slopware#anti-ai-policy) badge. See the [style guide](./STYLE.md) for more info.
+
+#### Rules for self submission
+
+You can absolutely self-submit your own projects. You just need to make sure you adhere to the following:
+
+- no previous strikes or bans in the repo
+- project is completely FOSS
+- project has a "Code of Conduct"
+- project has a "No AI Policy"
+
+#### Unqualified Alternatives
+
+- Any project associated with bigotry is not allowed.
+
+- At this time, we're not accepting alternatives that are centralized and/or lacking the appropriate documentation to be self-hosted by non-experts. For example, we will not endorse the messaging app "Signal", or social media platforms based on AT-protocol. In the event that such projects do become tainted they would not be easy to fork, operate, or support - which places users and operators at a disadvantage. If a project does improve their documentation such that self-hosting becomes more accessible, we will of course re-evaluate. Feel free to open a PR at that time.
+
+- We do not allow adult content at this time. (Please also do not submit alternatives with screenshots of adult content)
+
+# Contributing Issues
 
 Issues are meant primarily for discussing if something should be added or questions regarding clarification. An issue that says "Add x software" will be treated as a call to community action and labeled with `ready-for-pr`, provided it meets the above criteria. This is not a problem, but does not necessarily mean the core maintainers of this repo will create that PR for you. However it does mean you or someone else in the community is clear to go ahead and submit a PR for that software. This is maintained in the community's free time, so please understand that there will sometimes be a delay when a PR is created for you.
 
-Please make sure to only submit an Issue for 1 piece of software or section at a time, otherwise it is more difficult to coordinate between multiple Issues and PRs.
+Please make sure to only submit an Issue for 1 piece of software or section at a time, otherwise it is more difficult to coordinate between multiple Issues and Pull Requests.
+
+We use the following issue types and tags to keep conversation focused and actionable:
+
+- [![discussion](./badges/discussion.svg)](#discussion)
+- [![more kind eyes please](./badges/more-kind-eyes.svg)](#more-kind-eyes)
+
+## Discussion
+
+![discussion](./badges/discussion.svg)
+
+This is a general issue type and tag to discuss things related to the repo. Before opening this issue type, please read the [FAQ](./FAQ.md).
 
 This is not a place to discuss what you think an "ethical" LLM/AI is. We will close any Issues opened asking for advice on AI/LLM usage.
 
 This is also not a place to open an issue to the effect of "think of the centrists".
 
-## Helping with kind eyes
+If someone has a question in a Discussion type issue, and it requires a hard stance on behalf of the repo, please do not comment with a definitive answer unless you are a maintainer. If you do comment, please explicitly state that you are not an official maintainer, and tag @ethical-foss-admin if one has not already responded. There are still situations in which the maintainers will ask for community feedback, and in those, anyone is free to comment. We have these rules to reduce confusion and prevent conflict if there is a mismatch between community members and maintainers. If you feel strongly and want to push back, we are OK with that, but you must do so kindly and in accordance with our [Code of Conduct](./CODE_OF_CONDUCT.md).
 
-Maybe you don't need/want to open an Issue or Pull Request to this repo, but you still want to help. Here's what you can do. Take a look through the:
+## More Kind Eyes
 
-- **Issues** labeled with [`more-kind-eyes-please`](https://codeberg.org/small-hack/open-slopware/issues?q=&type=all&sort=relevance&labels=1318107&state=open&milestone=0&project=0&assignee=0&poster=0) or [`awaiting-upstream-feedback`](https://codeberg.org/small-hack/open-slopware/issues?q=&type=all&state=open&labels=1280479&milestone=0&assignee=0&poster=0)
-- **Pull Requests** labeled with [`more-kind-eyes-please`](https://codeberg.org/small-hack/open-slopware/pulls?q=&type=all&sort=relevance&labels=1318107&state=open&milestone=0&project=0&assignee=0&poster=0) or [`awaiting-upstream-feedback`](https://codeberg.org/small-hack/open-slopware/pulls?q=&type=all&sort=relevance&labels=1280479&state=open&milestone=0&project=0&assignee=0&poster=0)
+![more kind eyes please](./badges/more-kind-eyes.svg)
 
-In either case, one thing you can do is react positively to a given upstream issue, pull request, or discussion thread. If you're already a contributor to that project, you may also leave a comment. You *must* do so kindly though! We do not approve of anyone reaching out in a rude manner to any other projects. If you have no connection to project, the best thing you can do is an emoji react or upvote on the opening discussion topic or to a comment where AI is called out as bad. It's unwise to pop into a discussion for a project you do not use and have no interest in using and only adds noise to the conversation, which could overwhelm the maintainers. Please be cautious and courteous. If we find out you were threatening or expressed any form of bigotry, you will receive a ban from this repo.
+Maybe you don't need/want to open an Issue or Pull Request to this repo, but you still want to help. Consider chiming in, kindly, on a ![more kind eyes please](./badges/more-kind-eyes.svg) Issue. This issue type is for when someone has found, or created, a link to an AI discussion topic. AI discussion topic links can be:
 
-# Social media
+- Bug/Issue in a repo's Issue Tracker
+- Discussion on forge sites that support that feature e.g. GitHub Discussions
+- PR on an AI Policy where feedback is welcome
+- Forum post specifically dedicated to the project and read by the maintainers of the project
+- Social media account run *by the project* and not a solo maintainer. We do **not** want to call watchers of this repo to approach solo maintainers (there is too much room for that to potentially result in harassment), but if a project/company has a specific social media thread asking for opinions on AI usage in their code base or as a feature of their project/product, feel free to link that.
 
-We would appreciate it if you did not mention this repo on social media or in chats in order to shame a project or community. Do not make posts like, "`<project>` should be added to the open-slopware list", especially if you are tagging a maintainer or using a project's hashtag.
+>[!warning]
+> Do not recommend any software run by AI companies or by orgs/people who have a history of bigotry.
+
+Anyone can then react (kindly) to a linked upstream issue, pull request, or discussion thread. If you're already a contributor to that project, you may also leave a comment. You *must* do so kindly though! We do not approve of anyone reaching out in a rude manner to any other projects. If you have no connection to project, the best thing you can do is an emoji react or upvote on the opening discussion topic or to a comment where AI is called out as bad. Please be cautious and courteous. If we find out you were threatening or expressed any form of bigotry, you will receive a ban from this repo.
+
+Please don't link directly to codeberg.org repos, issues, pull requests or commits, as it will alert the other repo that they're being talked about in this list, which could create a negative atmosphere. If you need to link to them, please use a codeblock like this:
+
+```
+https://codeberg.org/org/project
+```
+
+>[!important]
+> Reminder that if you post a link to software that is maintained by people who openly embrace bigotry, we will close that issue. If you're a community member and see something we missed, feel free to kindly inform us and we will take action as soon as we're available (typically within 8 hours, but sometimes within 24 hours depending on availability).
+
+If you want to help in that way, search for:
+
+- [**Issues**](https://codeberg.org/ethical-foss/open-slopware/issues?q=&type=all&sort=relevance&labels=1318107&state=open&milestone=0&project=0&assignee=0&poster=0)
+- [**Pull Requests**](https://codeberg.org/ethical-foss/open-slopware/pulls?q=&type=all&sort=relevance&labels=1318107&state=open&milestone=0&project=0&assignee=0&poster=0)
+
+You can also open your own [![more kind eyes please](./badges/more-kind-eyes.svg) Issue](https://codeberg.org/ethical-foss/open-slopware/issues/new?template=.forgejo%2fissue_template%2frequest-for-more-kind-eyes.yaml).
+
+## Call for Collaborators
+
+This issue type is for advertising your "No AI allowed" project. It follows the same rules as self submission:
+
+- no previous strikes or bans in the repo
+- project is completely FOSS
+- project has a "Code of Conduct"
+- project has a "No AI Policy"
+
+Provided you meet the requirements, you're free to ask for additional collaborators or contributors to your repo :)
+
+# Contributing to the Why Not LLMs file
+
+This is a much more free form section without a specific rigid style guide at this time. Here are some general guidelines:
+
+- Do not link to people's social media posts e.g. the fediverse, bsky, X, etc even if they are against AI. Using blog posts is OK, but we'd prefer if the language there was not filled with profanity. We try to keep this repo professional.
+
+- When adding a link to back up your point, please use the name of the source and title of the article as the link name
+
+- Do not use paywalled links unless you are using an archive link that removes the paywall
+
+- Prefer archive links wherever possible
+
+  - Please don't use `archive.ph` or `archive.today`. See #54 for details. Using the wayback machine is always a good first course of action, but websites may ban it's IPs and in some rare cases, it may not be accessible to people globally. When in doubt, just chat with us in your PR to figure out the best course of action.
+
+- Use a content warning if anything may be triggering. Content warnings must be specific to the subject matter. Do not use the term "NSFW". Here is an example of how to write a content warning:
+
+   ```html
+   <details>
+     <summary>Content warning: Genocide</summary>
+     Content discussing genocide goes here.
+   </details>
+   ```

FAQ.md

@@ -0,0 +1,75 @@
+# Frequently Asked Questions
+
+There's no great place to put these in our current files, but these sorts of questions come up enough, that we wanted to put them down somewhere to easily link responses.
+
+## Can I self-advertise my project (that doesn't use AI)?
+
+> Yes, provided it meets our [Rules for Self Submission](https://codeberg.org/ethical-foss/open-slopware/src/branch/main/CONTRIBUTING.md#rules-for-self-submission), you can add your project as an alternative to any tainted software in which it is a good fit, and you can also open a [Call for Collaborators Issue](https://codeberg.org/ethical-foss/open-slopware/issues/new?template=.forgejo%2fissue_template%2fcollaborate-with-me.yaml).
+
+## I use AI in my project and do not plan on stopping. Should I self-submit?
+
+> You don't have to, but it's helpful, because you know best what the alternatives are, and when your last untainted commit was, which is helpful for those who wish to fork your project. We hope you'll consider dropping AI one day, for all the reasons we've listed in our [Why Not LLMs?](./why_not_llms.md) section, but if you don't plan on doing that ever, please just be cordial in this repo. No one is here to attack you, and if they do, please tag @ethical-foss-admin and we'll handle the situation.
+
+## Do closed source or proprietary products belong on this list?
+
+> No, this repo is only for open source projects.
+
+## Can we split the "Permissive AI Policy" tag further?
+
+> No, we don't want to have this conversation continually, as it is subjective what "severity" something falls under. The decision to add these tags took us a long time, and unless you have another *specific* tag that cannot be covered under any other tag, we're currently not open to discussion about this. This repo is already quite a lot to manage. We need to keep tags specific.
+
+## What if the AI code is human reviewed?
+
+> Slop that is human reviewed is still slop. We are against AI for more than just code quality reasons. Please see our [Why Not LLMs?](./why_not_llms.md) section.
+
+## Why are you targeting/attacking/harassing my favorite project?
+
+> We do not "target", "harass", or "attack" any projects. We, in fact, have a [very strict policy on not doing that](https://codeberg.org/ethical-foss/open-slopware/src/branch/main/CODE_OF_CONDUCT.md#be-kind-or-be-gone). This repo is one based on ethics and is intended as a call to action. If a project meets the definition of one of our tags, it will see itself added to this repo. It can take steps to stop doing whatever it is in that definition and we'll remove it. (See also the [guide for removal](https://codeberg.org/ethical-foss/open-slopware/src/branch/main/CONTRIBUTING.md#removal-of-tainted-status).)
+
+## If a repo had slop before, isn't it permanently tainted? Aren't all forks of slop therefore also slop?
+
+> No. See also: [guide for removal](https://codeberg.org/ethical-foss/open-slopware/src/branch/main/CONTRIBUTING.md#removal-of-tainted-status).
+>
+> Eventually, the slop will likely either be removed, replaced, or deprecated.
+>
+> We're also against AI for more than just code quality reasons. There's plenty of ethical reasons to be against continuing to use AI:
+>
+> - [environmental impact](https://codeberg.org/ethical-foss/open-slopware/src/branch/main/why_not_llms.md#environmental-impact)
+> - [ties to the war industrial complex](https://codeberg.org/ethical-foss/open-slopware/src/branch/main/why_not_llms.md#ties-to-the-war-industrial-complex)
+> - [effect on hardware prices hurting newcomers to the industry](https://codeberg.org/ethical-foss/open-slopware/src/branch/main/why_not_llms.md#effect-on-hardware-prices) (especially those already disenfranchised)
+>
+> The commitment to stop using AI stops those above ethical issues. It's like going vegetarian. You're still a vegetarian if you previously consumed meat, but now you don't. You've still reduced suffering and helped the environment. A commitment to doing better is better than never stopping a harmful action.
+
+## Is a project tainted if it has dependencies that are tainted?
+
+> This one is complicated, but in short: No, unless the dependencies are literally AI libraries.
+> If the dependency is, for example, the ChatGPT SDK or something similar, then yes, the project is tainted.
+> If the project is just built with something like Python, which is also tainted, we do not automatically consider it tainted, as the language is a general purpose language and there are *very* few languages not already tainted or slated to be tainted right now. We take a harm reduction philosophy and we believe that, especially in the case of established projects, demanding that they switch the core language of their project is not a simple undertaking.
+
+## Can you advise us on the ethical usage of AI?
+
+> No, but you may find the work of [DAIR](https://dair-institute.org/) interesting. Also, see our [Why not LLMs?](./why_not_llms.md) section.
+
+## What about "Open Source AI" tooling/usage?
+
+> Yes, simply being open source does not resolve the issues listed in our [Why Not LLMs?](./why_not_llms.md) section and thus such projects that utilize "open source AI" would still be included on this list as tainted.
+
+## Why is removal harder than landing on the list in the first place?
+
+> Because the project betrayed our trust. Now they have to try harder to rebuild that by committing to doing better in an accountable, public, concrete, and enforceable way. If the project is committed to doing better by rejecting AI in the future, putting out a No AI policy or updating their contributing docs, shouldn't be that difficult.
+
+## Why can't I include a social media post?
+
+> We do not want to have a social media type atmosphere here and quoting social media posts, no matter what side people are on, gets messy. The maintainers here do not have the mental health to engage in social media drama that inevitably arises from AI bros, nor do we want to inflict that on anyone who is unaware of this list and hasn't consented to that attention. This does not mean you should reach out to your favorite anti-AI influencer for permission to include them in this list. We don't want you to do that.
+
+### But what if it's a social media post against AI?
+
+> We would then need to research those social media users and see if we endorse them or not and we don't want to do that either.
+
+## I don't like your definition of slop or vibecoded. Can you change it?
+
+> No. Those [definitions](https://codeberg.org/ethical-foss/open-slopware#definitions) stay and are not up for debate.
+
+## How do we handle slop-free software with no tainted equivalent?
+
+> This is probably not the best list for the time being. This list focuses on boycotts and listing alternatives. If you want to list untainted software on it's own, we ask that you checkout our [sibling repos](https://codeberg.org/ethical-foss/open-slopware/src/branch/main#sibling-repos) section of our README that goes over a couple of other repos that highlight exclusively slop-free software :) As a note: we've had really positive interactions with all the repos listed under "sibling repos", so please don't hesitate to open PRs for their repos as well. Please follow the same code of conduct as you would here though, so above all: be kind!

GOVERNANCE.md

@@ -0,0 +1,46 @@
+# Who does What
+
+This repo wouldn't exist without the hundred or so people who contribute to it. We value everyone's contributions, but for certain tasks, we have a structure on who can do what.
+
+So it is clear: This is not anyone's full time job. Everyone is an unpaid volunteer working in their free time, including the owners.
+
+## Owners
+
+This is mainly @ethical-foss-admin which is an account that is run by multiple people who initially forked this repo. They have the ability to make new rules or tags and updates to the code of conduct. They have full approval and merge rights. If they've approved any PR, Team Human Made can pop in and merge that PR at their leisure. If you're asking for a new rule, tag, or major change to the repo in some way, you need to tag this account. This is also the account you should tag should you need moderation help in any capacity, as they have the authority to ban people from the repo, as well as lock a conversation if it gets too heated or has the potential to drive a rude atmosphere.
+
+If future owners appear, the tag to get them involved would be @ethical-foss/owners.
+
+## Team Human Made
+
+This is a special team of collaborators that have been vetted over time via their kind attitudes and continued contributions to the repo. When they show up in the repo, they will have a "member" tag on all their posts to distinguish them. They have the ability to speak on behalf of the repo when it comes to already established rules, and are frequently tagged on matters of discussion. They can also approve PRs, and it carries weight, but does not count towards the official approval required to allow a merge (something that may change in the near future). They can also merge anything that was already approved by the Owners.
+
+If they ask you to update something, or make a suggestion to improve something, please engage kindly.
+
+The entire team can be tagged with @ethical-foss/team-human-made. Please prefer tagging Team Human Made instead of a specific member, as to not weigh down one particular collaborator as, again, they all work on this in their free time.
+
+### How to Become a Member of Team Human Made
+
+When positions on Team Human Made are available, we'll create an Issue asking for people to apply and/or nominating specific people. You should not feel pressure to accept a position if you do not want it. We are still happy to have you as a contributor.
+
+We vet collaborators over a period of a couple of months of continued contributions. Provided you:
+
+- are kind and take feedback well
+- have participated in either PRs or Issues semi-regularly
+- have no Code of Conduct strikes (warnings can be OK depending on the warning, how you reacted, and how long it has been since your warning)
+  - do not have a visible history of behavior that would violate our Code of Conduct (even outside of this repo)
+
+There is no time requirement for how much you need to do in the repo once you're made a collaborator. Everyone should operate to the best of their ability. If you need time off for personal life, don't sweat it.
+
+## Contributors
+
+These are people who contribute to the repo. They have no special access. Anyone can be a contributor. They cannot approve or merge PRs, and they are not allowed to speak on behalf of the repo. If they would like to give an opinion on a discussion, they're free to do so, but if answering a question, they should state that they're not official maintainers, then tag in @ethical-foss/owners and/or @ethical-foss/team-human-made for an official response.
+
+# Vacations
+
+This repo gets put into "vacation mode" periodically through out the year. We do this because we need time away from the repo, and during that time, we can't guarentee any moderation, so for safety, no commenting on the repo can be allowed during that time.
+
+During vacation mode, we will disable Issues and Pull Requests and will not actively work on the repo in any way. Even though the Issues and Pull Requests are temporarily hidden, they are not deleted. The repo will still be public. There will be a notice at the top of README explaining that we're in vacation mode and when we will be back. When the vacation is over, the Issues and Pull Requests will be re-enabled, and all previous Issues/Pull Requests will be visible again.
+
+Vacations typically last anywhere from 3 days to 2 weeks depending on the owner's schedule, and are announced in advance.
+
+The owners reserve the right to put the repo into vacation mode if they are unwell and unable to tend to the repo.

HOW_TO_SLOP_FREE_FORK.md

@@ -0,0 +1,217 @@
+# How to create a slop free fork
+
+So you found out something you love is tainted with slop and now you want to do something about it?
+
+First off, congrats and thank you! That's a huge step and we're excited for the community you build! 💙
+
+## How to fork a repo from a last untainted commit/version
+
+Should you see a project you'd really like to fork on this list, here's how you would go about that.
+
+> [!warning]
+> Before you fork, make sure to check the licensing! It's important that you understand the license of whatever you fork, and never remove the old LICENSE. Safe to fork licenses include, but are not limited to: MIT, GPL, AGPL, Apache 2.0, CCv4, BSD. You can learn more about licensing in [Codeberg's documentation on licensing](https://docs.codeberg.org/getting-started/licensing/).
+
+Let's take tldr-pages as an example, as that was something the community recently hard forked into ethical-foss. Here's how it was done.
+
+1. Setup a new home for your fork. We recommend using [codeberg.org](https://codeberg.org)! Codeberg has [great docs on setting up your first repo](https://docs.codeberg.org/getting-started/first-repository/). We recommend not adding a `.gitignore`, `LICENSE`, or `README` to start with, because your clone will likely already have those and so you want to make sure you don't run into any git merge conflicts :) Do make sure to note that your repo is a fork of the repo you're forking at first though, just to make sure no one gets confused.
+
+2. Since we're using tldr as an example, we'll assume the project you want to fork is already in this repo. Go to the table where the software you want to fork is (for instance the [Cheat Sheets and Documentation section](https://codeberg.org/ethical-foss/open-slopware#cheat-sheets-and-documentation)), which looked like this:
+
+| Name | Last Untainted Version or Commit ID | Tags and Evidence | Alternative(s) |
+| --- |:---:| --- | --- |
+| [tldr-pages](https://github.com/tldr-pages/tldr) | [`v2.3`](https://github.com/tldr-pages/tldr/releases/tag/v2.3) | [![Permissive AI policy](./badges/permissive-ai-policy-orange.svg)](#permissive-ai-policy) ([1](https://github.com/tldr-pages/tldr/blob/main/AGENTS.md), [2](https://github.com/tldr-pages/tldr/commit/b042736266e10cb026b678ba1d0fed362d5f579d)) | [![Request for Help](./badges/request-for-help.svg)](#request-for-help) |
+
+3. Go to the source repo and find the clone URL. In this case, you would go to [tldr-pages](https://github.com/tldr-pages/tldr). Since it's on GitHub, you should see a green button that says "<> Code". Click the green button, then click "HTTPS" and you should be able to copy that URL.
+
+   <img src="./img/how_to/clone_tldr.png" alt="a screenshot of the https://github.com/tldr-pages/tldr page where someone has clicked the code button. The green code button is circled in orange with an orange arrow pointing to it. The HTTPS tab and the web URL to clone also have an orange square around them with an orange arrow pointing to the url">
+
+   > [!tip]
+   > In the above case, the tldr repo was linked in the first column of the table, but in cases where it's not you can just click the lasted untainted version link and chop off everything after the name of the project, so https://github.com/tldr-pages/tldr/releases/tag/v2.3 becomes https://github.com/tldr-pages/tldr
+
+4. Open up a terminal and find a directory where you'd like to keep this project. Then clone the repo there. Here is an example where we keep things in the projects directory within your home directory:
+
+   ```bash
+   # creates a directory called projects in your ~, which is your home directory
+   mkdir -p ~/Projects
+
+   # change your current directory into the new projects directory
+   cd ~/Projects
+
+   # clones the repo in your projects directory
+   git clone https://github.com/tldr-pages/tldr.git
+
+   # changes directory to your recently cloned project (in this example, it's the tldr repo)
+   cd tldr
+   ```
+
+5. Grab the new location of your new repo :) If you're using codeberg, you want to grab the SSH url for cloning, which you can find just below the repo stats. We've highlighted it and also we show you the button you can click to copy it easily here:
+
+   <img src="./img/how_to/copy_new_repo_url_codeberg.png" alt="Screenshot of the top of the page for https://codeberg.org/ethical-foss/ethical-foss where we've highlighted the clone url and drawn orange arrows pointing to the word SSH, the URL, and the copy button. They exist just below the repo states, but before the repo's code search bar and repo files">
+
+6. Change the upstream origin of your repo to be your new fork's SSH URL. There are two ways to do this. The first way is to use the `git` command:
+
+   ```bash
+   git remote set-url origin ssh://git@codeberg.org/ethical-foss/ethical-foss.git
+   ```
+
+   Another way is to edit the `.git/config` file Use your editor of choice to open the following file:
+
+   ```bash
+   # We're using neovim here, but you can use any editor you're comfortable with.
+   # If you're new, nano is always a safe bet as it has tips at the bottom of the screen.
+   neovim .git/config
+   ```
+
+   The file will look like this:
+
+   ```config
+   [core]
+       repositoryformatversion = 0
+       filemode = true
+       bare = false
+       logallrefupdates = true
+   [remote "origin"]
+       url = https://github.com/tldr-pages/tldr.git
+       fetch = +refs/heads/*:refs/remotes/origin/*
+   [branch "main"]
+       remote = origin
+       merge = refs/heads/main
+   ```
+
+   You want to change your the value of "url" to your new SSH URL. In this case, it would look like this, since the new repo is ethical-foss:
+
+   ```config
+   [core]
+       repositoryformatversion = 0
+       filemode = true
+       bare = false
+       logallrefupdates = true
+   [remote "origin"]
+       url = ssh://git@codeberg.org/ethical-foss/ethical-foss.git
+       fetch = +refs/heads/*:refs/remotes/origin/*
+   [branch "main"]
+       remote = origin
+       merge = refs/heads/main
+   ```
+
+7. Here comes the part where you check out the last known untainted commit or version. In this case, the last version of `v2.3`. You can do a hard reset of your fork to that exact version. This drops all the commits after that. To do that, run the following:
+
+   ```bash
+   # hard reset your branch to the old commit or version
+   git reset --hard v2.3
+
+   # force push up your now untainted repo
+   git push --force
+   ```
+
+8. The initial steps are now done and your new forked repo's history starts at the exact last known good version. Advanced git users can now cherry pick LLM commits out of the repo, but we recommend not doing that unless you're very confident with git. Instead, we think it's best that you create new commits to remove the AI and LLM generated code, because then this also keeps a cleaner history. In your "No AI Policy" or in your README, you can self disclose that the repo contains old commits from an LLM, but that you're working on replacing them or that you will not replace old commits, but all new commits will be done by humans. Either is fine. When it comes to AI Functionality, you'll also want to disclose that immediately and perhaps create an issue that says "Remove AI Functionality" to show users that you intend to remove that. You could also ask for help that that time.
+
+  > [!note]
+  > Are you an advanced git user? Do you want to add more docs here on how to remove old LLM commits from the forked repo? Feel free to submit a PR and we'll test your instructions to make sure they're safe before merging it :)
+
+## Tips for a healthy community
+
+To start off, we recommend you do two things:
+
+- Create a "Code of Conduct"
+- Create a "No AI Policy"
+
+### Code of Conduct
+
+This may seem like it's not related to the whole "No AI" thing we're all about, but it's incredibly important to creating safe and healthy communities. There will be people who try to cross lines and it's important that from outset, you both create rules for what is not allowed, and a process for enforcing those rules. We recommend the following be added to a `CODE_OF_CONDUCT.md` at the root level of your repo, immediately (this is straight from our own code of conduct):
+
+<details>
+
+  <summary><code>CODE_OF_CONDUCT.md</code> example</summary>
+
+  ```md
+  # Code of Conduct
+
+  ## No Bigotry
+
+  - No racism.
+  - No xenophobia.
+  - No colorism/featurism.
+  - No casteism.
+  - No transphobia.
+  - No homophobia/queerphobia.
+  - No sexism.
+  - No albeism.
+  - No islamophobia, antisemitism, or hatred to anyone based on their religion or lack thereof. 
+  - No classism.
+  - No fascism.
+
+  ## Strike system
+
+  We're going to do a 2 strike rule here with an optional warning. You are out on your second strike. We are not doing three strikes.
+
+  1. **warning**: You made a sarcastic or aggressive comment attacking another user here or elsewhere, regardless of which side you are on. You will get a reminder that you need to be kind here and if you need a comment by another user addressed, you must tag an admin. This warning and any warnings after it are *optional* and may be skipped if you are doing something that falls into the [No Bigotry](#no-bigotry) rules, or if you are clearly operating in bad faith.
+
+  2. **Strike one**: You made a comment that was off-base, slightly rude, but was not egregious enough to be banned, yet.
+
+  3. **Strike two**: After 1 strike, you behaved the same way again.
+
+  > [WARNING]
+  > If you are caught being excessively rude here, especially if you're displaying a form of severe bigotry or bringing an inappropriate tone, we reserve the right to ban you from the repo with no strikes and if necessary, we will report you to codeberg.org.
+
+  # Be kind or be gone
+
+  - We don't want drive by sarcastic comments.
+
+  - No references to bodily fluids (vomit, urine, feces), this includes emojis. It's gross and unproductive.
+
+  - We don't want people talking about how they never liked a particular piece of software because they didn't like the features.
+
+  - We don't want anyone personally attacking anyone from this repo or other repos.
+
+  - We will delete off-topic comments that have rude vibes or are encouraging a generally rage-feedback atmosphere.
+
+  - This repo is not a substitute for social media. The maintainers do not have the mental health bandwidth to manage such a community.
+
+  - Please do not reach out to the maintainers or collaborators of this repo anywhere but this repo specifically (unless they have given explicit permission to do so). We do not operate our personal email or fediverse accounts as extensions of this repo and will not take feedback there. We need a proper work life balance. Please respect that.
+
+  - No complaining about purity rules, "walking on egg shells", etc. If you can't behave professionally here, then please just kindly exit. 
+
+  ## Accessibility
+
+  ### Alt Text
+
+  Please provide alt text descriptions for any images you post. This is so that users that are blind or low vision know what is being posted as their screenreaders can read it aloud. This is also useful for people who speak other languages so that they can translate any text from the screenshot and understand context. If you don't provide alt text after being asked to, we will count that as a warning, and if you still fail to do so, it will be a strike. We make exceptions if you yourself have a disability preventing you from doing so. Please kindly ask that someone else provide alt text for you, and when they do, please update your image's alt text. (*You do not need to disclose your disability.* It is fine to ask others to provide alt text for you for ANY reason.)
+  ```
+
+</details>
+
+If you do not outline exactly what is and is not allowed, you will get a lot of people saying "I didn't know I couldn't do that" and it will make enforcing your boundaries difficult. People will always disagree with some decisions you and your community make, and they will want to "take it offline", so it's important that you do not allow that, or your personal social media and messaging will become bad for your mental health. If you'd like to set up a social media account/server or a chat server, we recommend keeping it separate from your personal accounts, so that you have an easy way to disconnect at the end of the day or on your weekends.
+
+### No AI Policy
+
+This one is obvious in this repo, but in other repos, it's always important to set clear expectations. Failure to do so may cause people to test the boundaries and also land you on this list. We don't say that to be threatening, but our community takes a complete hard line stance on ALL AI/LLM usage.
+
+Some examples of "No AI Polices" that you can take take a look at for inspiration are:
+
+- [wafrn's Contributring Doc](https://codeberg.org/wafrn/wafrn/src/branch/main/CONTRIBUTING.md)
+
+- [Loupe's Use of Generative AI Policy](https://discourse.gnome.org/t/loupe-no-longer-allows-generative-ai-contributions/27327)
+
+But in general you want to outline the following:
+
+- No AI or LLM usage is allowed in this repo for contributions in Issues, Pull Requests, or Discussions. This includes bug finding, optimizations, security passes.
+  - You are not permitted to ingest this repo with AI or LLMs of any kind
+  - Any AI generated PRs will be rejected.
+- We do not accept funding from AI companies.
+
+Do your best to not leave any wiggle room for anyone testing the waters on using AI in any way, this includes "self hosted LLMs".
+
+## Advertising your new fork
+
+We're so happy to hear you created a new slop free fork! You'll probably want some community help though. Here's what you can do to summon the open source community:
+
+1. Make sure your repo has all the appropriate and relevant topics, so for example, if you've forked the tldr-pages repo, tag the repo with `tldr`, and `cheatsheets`. Topics are managed the main page of your repository, directly under your repo's description.
+
+
+### Adding new collaborators
+
+Codeberg also has great docs on [how to add new collaborators](https://docs.codeberg.org/collaborating/invite-collaborators/)!
+
+> [!warning]
+> Ensure you trust anyone you give access to your repo. Don't add people as collaborators whom you've never interacted with before!

NO_AI_REQUEST_TEMPLATE.md

@@ -61,6 +61,21 @@ This has resulted in pricing historically marginalized individuals, who are more
 
 A lot of AI companies also work directly with nation states for use in their  War Departments, which in turn leads to further AI usage during war and invasions. This is coupled with [NYT: Palantir, Anthropic and small start-ups are generating rewards from their investments in defense tech](https://www.nytimes.com/2026/03/18/technology/silicon-valley-war-defense-tech.html).
 
+As another example [NPR: OpenAI announced Pentagon deal after Trump banned Anthropic](https://www.npr.org/2026/02/27/nx-s1-5729118/trump-anthropic-pentagon-openai-ai-weapons-ban) which was due to the USA Department of War [launching an AI acceleration strategy](https://web.archive.org/web/20260113071131/https://www.war.gov/News/Releases/Release/Article/4376420/war-department-launches-ai-acceleration-strategy-to-secure-american-military-ai/).
+
+Due to the nature of LLMs being only kind of as good as the data they are trained on, this can lead to additional civilian deaths and housing/infrastructure damage either intentionally or not. Examples:
+
+<details>
+  <summary>Content Warning: War details, death</summary>
+
+  - [Gaza: UN experts deplore use of purported AI to commit ‘domicide’ in Gaza, call for reparative approach to rebuilding](https://www.ohchr.org/en/press-releases/2024/04/gaza-un-experts-deplore-use-purported-ai-commit-domicide-gaza-call)
+  - [Lavender & Where’s Daddy: How Israel Used AI to Form Kill Lists & Bomb Palestinians in Their Homes](https://www.democracynow.org/2024/4/5/israel_ai)
+  - [Microsoft says it provided AI to Israeli military for war](https://apnews.com/article/microsoft-israel-military-gaza-hamas-artificial-intelligence-20b2adb438b39ee9cb6eb2f52c1ae44a)
+  - [Google has dropped its promise not to use AI for weapons](https://theconversation.com/google-has-dropped-its-promise-not-to-use-ai-for-weapons-its-part-of-a-troubling-trend-249169)
+  - ["We want to use it for everything": How Project Maven became central to America’s AI-powered warfare](https://web.archive.org/web/20260312035736/https://www.independent.co.uk/news/world/americas/project-maven-ai-us-airstrike-iraq-anthropic-b2929138.html)
+
+</details>
+
 ## What You Can Do
 
 I'd like to kindly suggest implementing a strict "No AI" policy. This can also help with what seems to be larger and larger influxes of low quality drive-by PRs by AI agents.
@@ -79,8 +94,103 @@ Thank you and kind regards :pray:
 
 ## Appeal to Code Quality Template
 
-Feel free to submit a PR to fill this one in.
+```markdown
+Hello,
 
+I'd like to talk about your AI policy. Below are some reasons why using AI can result in poorer code quality:
+
+## Poor Code Quality
+
+Vibe coding / agentic workflows result in poorer code quality, and relaxed oversight practices. These effects may be compounded by the common practice of using additional LLM-based tooling to provide code-reviews.
+
+* [How I Dropped Our Production Database and Now Pay 10% More for AWS](http://archive.today/2026.03.06-144058/https://alexeyondata.substack.com/p/how-i-dropped-our-production-database)
+* [Claude Tested Everything Except the One Thing That Mattered (AI agent refuses to follow explicit instructions to test `createPost()` in increasingly erratic ways)](http://archive.today/2026.03.09-201135/https://christophermeiklejohn.com/ai/claude/2026/03/08/claude-tested-everything-except-the-one-thing-that-mattered.html)
+* [Amazon calls engineers for a “deep dive” internal meeting to discuss “GenAI”-related outages](https://ghostarchive.org/archive/3TfgF)
+* GitClear has released reports in [2024](https://www.gitclear.com/coding_on_copilot_data_shows_ais_downward_pressure_on_code_quality) and [2025](https://www.gitclear.com/ai_assistant_code_quality_2025_research) indicating a worsening of key code quality metrics correlating with increased LLM adoption.
+
+### Deskilling
+
+There is increasing evidence to show that LLMs negatively impact developers' coding abilities:
+
+* [Brains show less activity when completing tasks with LLMs](https://arxiv.org/abs/2506.08872) compared to completing tasks with search or completing tasks without digital help.
+* [Developers who use early-2025 LLMs](https://metr.org/blog/2025-07-10-early-2025-ai-experienced-os-dev-study/) reported higher subjective performance, but were measured to have lower objective performance. This gap between subjective and objective performance was considered notable.
+* In an [Anthropic study](https://www.anthropic.com/research/AI-assistance-coding-skills), learners using LLMs demonstrated lower learning rates on average compared to learners not using LLMs.
+* [A recent study uses the term "cognitive surrender"](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=6097646) to describe the way humans tend to offload key critical thinking skills onto LLMs, even when the output is wrong.
+* A paper entitled ["AI Assistance Reduces Persistence and Hurts Independent Performance"](https://arxiv.org/abs/2604.04721) from April 2026 by academics from MIT, Oxford, UCLA, and Carnegie Mellon showed alarming evidence that performing a variety of tasks with the help of AI for only 10 minutes causes "inpaired unassisted performance and reduced persistence". The researchers noted that "although AI assistance improves performance in the short-term, people perform significantly worse without AI and are more likely to give up"; they also pointed out that "these findings are particularly concerning because persistence is foundational to skill acquisition and is one of the strongest predictors of long-term learning".
+
+### Infosec risks
+
+LLM usage results in massive security holes.
+
+* [Meta Security Researcher's AI Agent Accidentally Deleted Her Emails](http://archive.today/2026.02.26-153034/https://www.pcmag.com/news/meta-security-researchers-openclaw-ai-agent-accidentally-deleted-her-emails)
+* [Moltbook's "vibe-coded" breach is the future of security failures](https://thehill.com/opinion/cybersecurity/5744310-ai-powered-security-risks/)
+* [In a study evaluating over 500k code samples, LLM-generated code was found to contain more high-risk security vulnerabilities than human-generated code](https://arxiv.org/abs/2508.21634)
+* [LLMs make up package names, making them vulnerable to incorporating malicious code in "slopsquatting" attacks](https://www.theregister.com/2025/04/12/ai_code_suggestions_sabotage_supply_chain/) ([Arxiv study](https://arxiv.org/abs/2406.10279))
+
+## What You Can Do
+
+I'd like to kindly suggest implementing a strict "No AI" policy. This can also help with what seems to be larger and larger influxes of low quality drive-by PRs by AI agents.
+
+You can find other projects that have taken steps to say no to AI here:
+https://noai.starlightnet.work/list.html
+
+For a specific policy, I can recommend the following policies for inspiration:
+
+- [wafrn's Contributring Doc](https://codeberg.org/wafrn/wafrn/src/branch/main/CONTRIBUTING.md)
+
+- [Loupe's Use of Generative AI Policy](https://discourse.gnome.org/t/loupe-no-longer-allows-generative-ai-contributions/27327)
+
+Thank you and kind regards :pray:
+```
 ## Appeal to Fear of Legal Ramfification Template
+```markdown
+Hello,
 
-Feel free to submit a PR to fill this one in.
+I'd like to talk about your AI policy. Below are some reasons why using AI can result in legal trouble in the future:
+
+## Legal Ramifications
+
+LLMs are often trained on, and thus prone to regurgitate (either completely, or in-part), chunks of code that are licensed under terms which have specific legal requirements that a contributor using LLMs may not understand or even be aware of when making a contribution. Regardless of this ignorance, it falls to the repo's owner to comply with the terms of any and all licensed code integrated into their project.
+
+### License Problems
+
+Legal, copyright, and ethics problems arise, especially with copyleft licenses such as the GNU (A/L)GPL. With the "help" of AI the copyleft code may be "license-washed" very easily.
+
+Here are some ongoing problems with AI "license-washing" in the FOSS world:
+
+* `chardet` - used an LLM to rewrite the codebase from the LGPL license to Expat/MIT (and later 0-BSD) license, violating the (L)GPL.
+  * relicensed release: <https://github.com/chardet/chardet/releases/tag/7.0.0>
+  * original author's concerns: <https://github.com/chardet/chardet/issues/327>
+  * "consumer's" concerns: <https://github.com/chardet/chardet/issues/331>
+
+Additionally, there have been legal cases regarding the usage of AI:
+
+* [GitHub Copilot litigation](https://githubcopilotlitigation.com/)
+* [IEEE article explaining concerns about AI generated code ownership](https://spectrum.ieee.org/ai-code-generation-ownership)
+* [Tracker of broader lawsuits against AI companies](https://chatgptiseatingtheworld.com/2025/11/02/tracker-of-tort-lawsuits-v-ai-companies/)
+
+### Stolen Training Data
+
+AI companies use data from across the web to train their models, most often without the website owners' and users' consent. Big tech companies like Google and Meta are scraping data from the users of major FOSS projects, such as Mastodon, WordPress, and other ActivityPub-powered and self-hosted software.
+
+* In 2023, [the Washington Post published a list of sources in Google's C4 data set](https://archive.ph/eehKq). A multitude of fediverse instances and personal sites were included. The fediverse is known for its userbase being major proponents of privacy and opt-in consent, making this especially jarring for those who have chosen to use decentralized social media for control over their data.
+* In 2025, [a similar leak of Meta's sources was published](https://archive.ph/NZlf3). Meta's list demonstrates how their integration of ActivityPub into their Threads software has enhanced their ability to scrape content without authorization. Threads is widely blocked in some parts of the fediverse, but their scraping of server CDNs has allowed them to get around that. Notably, both the CDN domains of the managed hosting services masto.host and fedi.monster are included in the list; large servers like mastodon.art, which is hosted by the former and has many artists who've left sites like DeviantArt and others due to their AI scraping of user content, had [media unknowingly scraped](https://mastodon.art/@Curator/115022115346692178).
+* In March 2026, [a research paper](https://arxiv.org/html/2603.20957v2) showed that simply fine-tuning LLMs resulted in outputs containing up to 90% of entire (copyrighted) books, contradicting LLM companies' previous statements in court that their models do not store copies of training data. After fine-tuning exclusively on a single author, the researchers were able to cause the LLM to output works from over 30 completely unrelated authors across different genres. None of the models were explicitly trained on these books by the researchers, which indicates that LLMs always carry with them a considerable amount of copyrighted materials from training.
+
+Usage of AI in your project is usage of tooling that blatantly disregards licensing and violates the Code of Conduct in your project (if present), making said tools antithetical to FOSS' purpose.
+
+## What You Can Do
+
+I'd like to kindly suggest implementing a strict "No AI" policy. This can also help with staying your code legally clean as code by AI agents often ignore licensing requirements.
+
+You can find other projects that have taken steps to say no to AI here:
+https://noai.starlightnet.work/list.html
+
+For a specific policy, I can recommend the following policies for inspiration:
+
+- [wafrn's Contributring Doc](https://codeberg.org/wafrn/wafrn/src/branch/main/CONTRIBUTING.md)
+
+- [Loupe's Use of Generative AI Policy](https://discourse.gnome.org/t/loupe-no-longer-allows-generative-ai-contributions/27327)
+
+Thank you and kind regards :pray:
+```

STYLE.md

@@ -14,30 +14,51 @@ Be sure to put things in the correct category and always update the above TOC (t
 
 Make sure to format your table like below (note that it is alphabetized by software name):
 
-| Name | Last Untainted Version or Commit ID | Tags and Evidence | Alternative(s) |
+| Name | Last Untainted <br />Version/Commit ID | Evidence | Alternative(s) |
 |---|:---:|---|---|
-| [formallyCoolSoftware](https://linktocoolsoftware.com) | [`ab12345`](linktolastgoodcommitid.com/commit/ab12345) | [![Permissive AI policy](./badges/permissive-ai-policy-orange.svg)](#permissive-ai-policy) ([1](http://linktocoolsoftware.com/branch/main/AGENTS.md))<br/> ![AI Sponsored](./badges/ai-sponsored-blue.svg) ([1](http://linktocoolsoftware.com/branch/main/README.md))| [coolSlopFreeProject] |
-| [formallyOKSoftware](https://linktofinesoftware.com) | [`v2.0.0`](linktolastgoodversion.com/v2.0.0) | [![Permissive AI policy](./badges/permissive-ai-policy-orange.svg)](#permissive-ai-policy) ([1](http://linktocoolsoftware.com/branch/main/AGENTS.md))<br/> ![AI Sponsored](./badges/ai-sponsored-blue.svg) ([1](http://linktocoolsoftware.com/branch/main/README.md))| [alrightSlopFreeProject] |
+| [formallyCoolSoftware](https://linktocoolsoftware.tld) | [`v1.0.0`](linktolastgoodcommitid.tld/releases/v1.0.0)<br/>[`ab12345`](linktolastgoodcommitid.tld/commit/ab12345) | [![AI Functionality](./badges/ai-functionality.svg)](https://codeberg.org/ethical-foss/open-slopware#ai-functionality) ([1](https://docs.linktocoolsoftware.tld/ai-assistant))<br/>[![Vibecoded](./badges/vibecoded.svg)](#vibecoded) ([1](https://link-to-software-blog.tld/how-i-vibecoded-the-app)) <br/> [![Permissive AI policy](./badges/permissive-ai-policy-orange.svg)](#permissive-ai-policy) ([1](https://linktocoolsoftware.tld/branch/main/AGENTS.md))<br/> [![AI Code Reviews](./badges/ai-code-reviews-purple.svg)](https://codeberg.org/ethical-foss/open-slopware#ai-code-reviews) ([1](https://linktocoolsoftware.tld/branch/main/AGENTS.md))<br/> [![Gen AI 'Art'](./badges/gen-ai-art-dark-yellow.svg)](https://codeberg.org/ethical-foss/open-slopware#gen-ai-art) ([1](https://linktocoolsoftware.tld/ai_logo.jpg))<br/> [![AI Databroker Usage](./badges/ai-databroker-usage-pink.svg)](https://codeberg.org/ethical-foss/open-slopware#ai-databroker-usage) ([1](https://linktocoolsoftware.tld/privacypolicy)) <br/> ![AI Sponsored](./badges/ai-sponsored-blue.svg) ([1](https://linktocoolsoftware.tld/branch/main/README.md)) <br/> [![AI In Issue Tracker](./badges/ai-in-issue-tracker-teel.svg)](https://codeberg.org/ethical-foss/open-slopware#ai-in-issue-tracker) ([1](http://linktocoolsoftware.tld/issues/123))<br/> [![Condones LLM Ingestion](./badges/condones-llm-ingestion.svg)](https://codeberg.org/ethical-foss/open-slopware#condones-llm-ingestion) ([1](https://linktocoolsoftware.tld/branch/main/ai_policy.md)) | [coolSlopFreeProject] |
+| [formallyOKSoftware](https://linktofinesoftware.tld) | [`v2.0.0`](linktolastgoodversion.tld/v2.0.0) | [![Permissive AI policy](./badges/permissive-ai-policy-orange.svg)](#permissive-ai-policy) ([1](https://linktocoolsoftware.tld/branch/main/AGENTS.md))<br/> ![AI Sponsored](./badges/ai-sponsored-blue.svg) ([1](https://linktocoolsoftware.tld/branch/main/README.md))| [alrightSlopFreeProject] <br/> [amazingSlopFreeProject] [![Anti-AI Policy](./badges/anti-ai-policy.svg)](#anti-ai-policy) ([1](https://link-to-anti-ai-evidence.tld)) |
+
+**Name column**: should be the name of software linked to their git repo (or other software forge if they don't use git).
+
+**Last Untainted Version/Commit**: should be the last commit before AI started being used in the repo. You can provide both the version and a commit hash, but if you can only provide one, please prefer using the version. (Reminder: This is meant for forking only, as running old software comes with security risks.) If the project is [![Vibecoded](./badges/vibecoded.svg)](https://codeberg.org/ethical-foss/open-slopware##vibecoded), you can just use the word "None" for the Last Untainted Version/Commit. You must provide something (even "None" if Vibecoded) *either* for this column, or for the alternatives column - unless there is already an "Alternatives" note.
 
 **Evidence column**: should contain one or more of the following tags (followed by *up to 3* numbered evidence links in parentheses):
 
-- [![AI Functionality](./badges/ai-functionality-yellow.svg)](https://codeberg.org/small-hack/open-slopware#ai-functionality)
-- [![Permissive AI policy](./badges/permissive-ai-policy-orange.svg)](https://codeberg.org/small-hack/open-slopware#permissive-ai-policy)
-- [![AI Code Reviews](./badges/ai-code-reviews-purple.svg)](https://codeberg.org/small-hack/open-slopware#ai-code-reviews)
-- [![AI sponsored](./badges/ai-sponsored-blue.svg)](https://codeberg.org/small-hack/open-slopware#sponsored-by-ai)
-- [![Gen AI 'Art'](./badges/gen-ai-art-dark-yellow.svg)](https://codeberg.org/small-hack/open-slopware#gen-ai-art)
-- [![AI Databroker Usage](./badges/ai-databroker-usage-pink.svg)](https://codeberg.org/small-hack/open-slopware#ai-databroker-usage)
-- [![AI In Issue Tracker](./badges/ai-in-issue-tracker-teel.svg)](https://codeberg.org/small-hack/open-slopware#ai-in-issue-tracker)
-- [![Permits LLM Ingestion](./badges/permits-llm-ingestion.svg)](https://codeberg.org/small-hack/open-slopware#permits-llm-ingestion)
+- [![AI Functionality](./badges/ai-functionality.svg)](https://codeberg.org/ethical-foss/open-slopware#ai-functionality)
+- [![Vibecoded](./badges/vibecoded.svg)](https://codeberg.org/ethical-foss/open-slopware##vibecoded) (keep in mind this is more severe than permissive AI policy)
+- [![Permissive AI policy](./badges/permissive-ai-policy-orange.svg)](https://codeberg.org/ethical-foss/open-slopware#permissive-ai-policy)
+- [![AI Code Reviews](./badges/ai-code-reviews-purple.svg)](https://codeberg.org/ethical-foss/open-slopware#ai-code-reviews)
+- [![Gen AI 'Art'](./badges/gen-ai-art-dark-yellow.svg)](https://codeberg.org/ethical-foss/open-slopware#gen-ai-art)
+- [![AI Databroker Usage](./badges/ai-databroker-usage-pink.svg)](https://codeberg.org/ethical-foss/open-slopware#ai-databroker-usage)
+- [![AI sponsored](./badges/ai-sponsored-blue.svg)](https://codeberg.org/ethical-foss/open-slopware#sponsored-by-ai)
+- [![AI In Issue Tracker](./badges/ai-in-issue-tracker-teel.svg)](https://codeberg.org/ethical-foss/open-slopware#ai-in-issue-tracker)
+- [![Condones LLM Ingestion](./badges/condones-llm-ingestion.svg)](https://codeberg.org/ethical-foss/open-slopware#condones-llm-ingestion)
 
-**Don't know what the alternative or last known good version is?** Use this badge in its place:
+> [!note]
+> The above order is the official order you should add your tags in.
 
-- [![Request for Help](./badges/request-for-help.svg)](https://codeberg.org/small-hack/open-slopware#request-for-help)
+**Alternatives Column**: should be a link to the source of a different project that is similar to the one that is tainted, but does not yet have any AI in it. This column can be omitted if there are many alternatives for one entry. See: [When to use an Alternatives Note Versus Table Column](#when-to-use-an-alternatives-note-versus-table-column).
+
+> [!warning]
+> You must provide *either* a last untainted commit/version *or* an alternative. You can provide both, but if you don't provide one or the other, you will be politely asked to do so. There is an exception if the tainted project is [![Vibecoded](./badges/vibecoded.svg)](https://codeberg.org/ethical-foss/open-slopware##vibecoded) with no clear alternatives OR there is already an "Alternatives" note.
+
+**Don't know what the alternative or last known untainted version/commit is?** Use this badge in its place:
+
+- [![Request for Help](./badges/request-for-help.svg)](https://codeberg.org/ethical-foss/open-slopware#request-for-help)
+
+**Does an alternative you're recommending have an explicit and clear "No AI" policy?** Use this special badge to make sure they stand out!
+
+- [![Anti-AI Policy](./badges/anti-ai-policy.svg)](https://codeberg.org/ethical-foss/open-slopware#anti-ai-policy)
 
 Here are all the badges for easy copying and pasting:
 
 ```markdown
-[![AI Functionality](./badges/ai-functionality-yellow.svg)](#ai-functionality)
+[![AI Functionality](./badges/ai-functionality.svg)](#ai-functionality)
+```
+
+```markdown
+[![Vibecoded](./badges/vibecoded.svg)](#vibecoded)
 ```
 
 ```markdown
@@ -65,13 +86,17 @@ Here are all the badges for easy copying and pasting:
 ```
 
 ```markdown
-[![Permits LLM Ingestion](./badges/permits-llm-ingestion.svg)](#permits-llm-ingestion)
+[![Condones LLM Ingestion](./badges/condones-llm-ingestion.svg)](#condones-llm-ingestion)
 ```
 
 ```markdown
 [![Request for Help](./badges/request-for-help.svg)](#request-for-help)
 ```
 
+```markdown
+[![Anti-AI Policy](./badges/anti-ai-policy.svg)](#anti-ai-policy)
+```
+
 > [!important]
 >
 > If a project has multiple tags, please be sure to add a break (`<br />`) in between each one, so that the column extends vertically rather than horizontally. This keeps the table visually consistent and easier to read at a glance.
@@ -80,15 +105,18 @@ Please do not submit GitHub screenshots of "A user you have blocked has previous
 
 Screenshots are allowed but must be a last resort for something that cannot be linked. We'd prefer archive links in all other instances.
 
-The above "Alternative(s)" column is for software that has a 1:1 parity or is a very similar alternative specific to the piece of software at hand. If the category or section is filled with the same alternative list (for instance, how it is in the [terminal emulators](https://codeberg.org/small-hack/open-slopware#terminal-emulators) section), you can remove the "Alternatives" column. Instead, you can add a note below the table with all the alternatives, like this:
+## When to use an Alternatives Note Versus Table Column
+
+The above "Alternative(s)" column is for software that has a 1:1 parity or is a very similar alternative specific to the piece of software at hand. If the category or section is filled with the same alternative list (for instance, how it is in the [terminal emulators](https://codeberg.org/ethical-foss/open-slopware#terminal-emulators) section), you can remove the "Alternatives" column. Instead, you can add a note below the table with all the alternatives, like this:
 
 > [!NOTE]
 > ### Category Alternatives
-> If there are a lot of alternatives for a section, include the alternatives in a note like this.
-> * [alternativeSoftware]: This can be a short description and [link to anti-AI policies](somelink.link).
-> * [coolSlopFreeProject]: This can be a short description and [link to anti-AI policies](somelink.link).
+> If there are a lot of alternatives for a section, include the alternatives in a note like this. These should also be alphabetized.
+> * [alternativeSoftware]: [![Anti-AI Policy](./badges/anti-ai-policy.svg)](#anti-ai-policy) ([1](https://link-to-anti-ai-evidence.tld)) This can be a short description.
+> * [coolSlopFreeProject]: This can be a short description.
 
-<!-- here is where you would put your links to alternative software, to keep the markdown doc clean -->
-[alternativeSoftware]: https://verygoodnotslopware.com "alternative software"
-[coolSlopFreeProject]: https://verygoodnotslopware2.com "another alternative software"
-[alrightSlopFreeProject]: https://veryoknotslopware3.com "another extra alternative software"
+<!-- here is where you would put your links to alternative software, to keep the markdown doc clean and should also be alphabetized -->
+[amazingSlopFreeProject]: https://verygoodnotslopware.tld "an amazing example of a no-ai project"
+[alrightSlopFreeProject]: https://veryoknotslopware3.tld "another extra alternative software"
+[alternativeSoftware]: https://verygoodnotslopware.tld "alternative software"
+[coolSlopFreeProject]: https://verygoodnotslopware2.tld "another alternative software"

badges/ai-databroker-usage-pink.svg

@@ -5,15 +5,15 @@
     <stop offset="1" stop-opacity=".1"/>
   </linearGradient>
   <clipPath id="r">
-    <rect width="115" height="20" rx="3" fill="#fff"/>
+    <rect width="115" height="20" rx="3" fill="#000"/>
   </clipPath>
   <g clip-path="url(#r)">
-    <rect width="0" height="20" fill="#BF1F8F"/>
-    <rect x="0" width="115" height="20" fill="#BF1F8F"/>
+    <rect width="0" height="20" fill="#e5e4e2"/>
+    <rect x="0" width="115" height="20" fill="#e5e4e2"/>
     <rect width="115" height="20" fill="url(#s)"/>
   </g>
-  <g fill="#fff" text-anchor="middle" font-family="Verdana,Geneva,DejaVu Sans,sans-serif" text-rendering="geometricPrecision" font-size="110">
+  <g fill="#000" text-anchor="middle" font-family="Verdana,Geneva,DejaVu Sans,sans-serif" text-rendering="geometricPrecision" font-size="110">
     <text aria-hidden="true" x="567" y="150" fill="#010101" fill-opacity=".3" transform="scale(.1)" textLength="1055">AI Databroker Usage</text>
-    <text x="567" y="140" transform="scale(.1)" fill="#fff" textLength="1055">AI Databroker Usage</text>
+    <text x="567" y="140" transform="scale(.1)" fill="#000" textLength="1055">AI Databroker Usage</text>
   </g>
 </svg>

badges/ai-functionality-yellow.svg

@@ -1,19 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="90" height="20" role="img" aria-label="AI Functionality">
-  <title>AI Functionality</title>
-  <linearGradient id="s" x2="0" y2="90%">
-    <stop offset="0" stop-color="#bbb" stop-opacity=".1"/>
-    <stop offset="1" stop-opacity=".1"/>
-  </linearGradient>
-  <clipPath id="r">
-    <rect width="90" height="20" rx="3" fill="#000"/>
-  </clipPath>
-  <g clip-path="url(#r)">
-    <rect width="0" height="20" fill="#DED700"/>
-    <rect x="0" width="90" height="20" fill="#DED700"/>
-    <rect width="90" height="20" fill="url(#s)"/>
-  </g>
-  <g fill="#000" text-anchor="middle" font-family="Verdana,Geneva,DejaVu Sans,sans-serif" text-rendering="geometricPrecision" font-size="110">
-    <text aria-hidden="true" x="465" y="150" fill="#010101" fill-opacity=".3" transform="scale(.1)" textLength="800">AI Functionality</text>
-    <text x="465" y="140" transform="scale(.1)" fill="#000" textLength="800">AI Functionality</text>
-  </g>
-</svg>

badges/ai-functionality.svg

@@ -0,0 +1,16 @@
+<svg width="90" height="20" aria-label="AI Functionality" role="img" version="1.1" xmlns="http://www.w3.org/2000/svg">
+ <linearGradient id="s" x2="0" y2="90%">
+  <stop stop-color="#bbb" stop-opacity=".1" offset="0"/>
+  <stop stop-opacity=".1" offset="1"/>
+ </linearGradient>
+ <clipPath id="r">
+  <rect width="90" height="20" rx="3"/>
+ </clipPath>
+ <g clip-path="url(#r)">
+  <rect width="0" height="20" fill="#DED700"/>
+  <rect width="90" height="20" fill="#DED700"/>
+  <rect width="90" height="20" fill="url(#s)"/>
+ </g>
+ <text transform="matrix(.1 0 0 .1 0 -.42775)" x="465" y="150" fill="#000000" fill-opacity=".3" font-family="Verdana, Geneva, 'DejaVu Sans', sans-serif" font-size="110px" text-anchor="middle" text-rendering="geometricPrecision" aria-hidden="true" textLength="800">AI Functionality</text>
+ <text transform="scale(.1)" x="465" y="140" fill="#000000" font-family="Verdana, Geneva, 'DejaVu Sans', sans-serif" font-size="110px" text-anchor="middle" text-rendering="geometricPrecision" textLength="800">AI Functionality</text>
+</svg>

badges/anti-ai-policy.svg

@@ -0,0 +1,19 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="95" height="15" role="img" aria-label="🌟 Anti-AI Policy">
+  <title>🌟 Anti-AI Policy</title>
+  <linearGradient id="s" x2="0" y2="100%">
+    <stop offset="0" stop-color="#bbb" stop-opacity=".1"/>
+    <stop offset="1" stop-opacity=".1"/>
+  </linearGradient>
+  <clipPath id="r">
+    <rect width="95" height="15" rx="3" fill="#000"/>
+  </clipPath>
+  <g clip-path="url(#r)">
+    <rect width="0" height="15" fill="#40A100"/>
+    <rect x="0" width="95" height="15" fill="#40A100"/>
+    <rect width="95" height="15" fill="url(#s)"/>
+  </g>
+  <g fill="#FFF" text-anchor="middle" font-family="Verdana,Geneva,DejaVu Sans,sans-serif" text-rendering="geometricPrecision" font-size="100">
+    <text aria-hidden="true" x="480" y="110" fill="#010101" fill-opacity=".3" transform="scale(.1)" textLength="860">🌟 Anti-AI Policy</text>
+    <text x="480" y="110" transform="scale(.1)" fill="#FFF" textLength="860">🌟 Anti-AI Policy</text>
+  </g>
+</svg>

badges/condones-llm-ingestion.svg

@@ -1,5 +1,5 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="123" height="20" role="img" aria-label="Permits LLM Ingestion">
-  <title>Permits LLM Ingestion</title>
+<svg xmlns="http://www.w3.org/2000/svg" width="123" height="20" role="img" aria-label="Condones LLM Ingestion">
+  <title>Condones LLM Ingestion</title>
   <linearGradient id="s" x2="0" y2="100%">
     <stop offset="0" stop-color="#bbb" stop-opacity=".1"/>
     <stop offset="1" stop-opacity=".1"/>
@@ -13,7 +13,7 @@
     <rect width="123" height="20" fill="url(#s)"/>
   </g>
   <g fill="#fff" text-anchor="middle" font-family="Verdana,Geneva,DejaVu Sans,sans-serif" text-rendering="geometricPrecision" font-size="110">
-    <text aria-hidden="true" x="617" y="150" fill="#010101" fill-opacity=".3" transform="scale(.1)" textLength="1130">Permits LLM Ingestion</text>
-    <text x="617" y="140" transform="scale(.1)" fill="#fff" textLength="1130">Permits LLM Ingestion</text>
+    <text aria-hidden="true" x="617" y="150" fill="#010101" fill-opacity=".3" transform="scale(.1)" textLength="1130">Condones LLM Ingestion</text>
+    <text x="617" y="140" transform="scale(.1)" fill="#fff" textLength="1130">Condones LLM Ingestion</text>
   </g>
 </svg>

badges/discussion.svg

@@ -0,0 +1,19 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="67" height="20" role="img" aria-label="discussion">
+  <title>discussion</title>
+  <linearGradient id="s" x2="0" y2="100%">
+    <stop offset="0" stop-color="#bbb" stop-opacity=".1"/>
+    <stop offset="1" stop-opacity=".1"/>
+  </linearGradient>
+  <clipPath id="r">
+    <rect width="67" height="20" rx="3" fill="#fff"/>
+  </clipPath>
+  <g clip-path="url(#r)">
+    <rect width="0" height="20" fill="#5319e7ff"/>
+    <rect x="0" width="67" height="20" fill="#5319e7ff"/>
+    <rect width="67" height="20" fill="url(#s)"/>
+  </g>
+  <g fill="#fff" text-anchor="middle" font-family="Verdana,Geneva,DejaVu Sans,sans-serif" text-rendering="geometricPrecision" font-size="110">
+    <text aria-hidden="true" x="335" y="150" fill="#010101" fill-opacity=".3" transform="scale(.1)" textLength="570">discussion</text>
+    <text x="335" y="140" transform="scale(.1)" fill="#fff" textLength="570">discussion</text>
+  </g>
+</svg>

badges/more-kind-eyes.svg

@@ -0,0 +1,18 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="115" height="20" role="img" aria-label="More Kind Eyes Please">
+  <title>More Kind Eyes Please</title>
+  <linearGradient id="s" x2="0" y2="100%">
+    <stop offset="0" stop-color="#313131" stop-opacity=".1"/>
+    <stop offset="1" stop-opacity=".1"/>
+  </linearGradient>
+  <clipPath id="r">
+    <rect width="115" height="20" rx="3" fill="#000000"/>
+  </clipPath>
+  <g clip-path="url(#r)">
+    <rect width="0" height="20" fill="#fbca04ff"/>
+    <rect x="0" width="115" height="20" fill="#fbca04ff"/>
+    <rect width="115" height="20" fill="url(#s)"/>
+  </g>
+  <g fill="#000000" text-anchor="middle" font-family="Verdana,Geneva,DejaVu Sans,sans-serif" text-rendering="geometricPrecision" font-size="110">
+    <text x="567" y="140" transform="scale(.1)" fill="#000000" textLength="1055">More Kind Eyes Please</text>
+  </g>
+</svg>

badges/ready-for-pr.svg

@@ -0,0 +1,19 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="92" height="20" role="img" aria-label="Ready for PR">
+  <title>Ready for PR</title>
+  <linearGradient id="s" x2="0" y2="100%">
+    <stop offset="0" stop-color="#bbb" stop-opacity=".1"/>
+    <stop offset="1" stop-opacity=".1"/>
+  </linearGradient>
+  <clipPath id="r">
+    <rect width="92" height="20" rx="3" fill="#fff"/>
+  </clipPath>
+  <g clip-path="url(#r)">
+    <rect width="0" height="20" fill="#40A100"/>
+    <rect x="0" width="92" height="20" fill="#40A100"/>
+    <rect width="92" height="20" fill="url(#s)"/>
+  </g>
+  <g fill="#fff" text-anchor="middle" font-family="Verdana,Geneva,DejaVu Sans,sans-serif" text-rendering="geometricPrecision" font-size="110">
+    <text aria-hidden="true" x="450" y="150" fill="#010101" fill-opacity=".3" transform="scale(.1)" textLength="830">Ready for PR</text>
+    <text x="450" y="140" transform="scale(.1)" fill="#fff" textLength="830">Ready for PR</text>
+  </g>
+</svg>

badges/request-for-help.svg

@@ -8,8 +8,8 @@
     <rect width="95" height="20" rx="3" fill="#fff"/>
   </clipPath>
   <g clip-path="url(#r)">
-    <rect width="0" height="20" fill="#40A100"/>
-    <rect x="0" width="95" height="20" fill="#40A100"/>
+    <rect width="0" height="20" fill="#BF1F8F"/>
+    <rect x="0" width="95" height="20" fill="#BF1F8F"/>
     <rect width="95" height="20" fill="url(#s)"/>
   </g>
   <g fill="#fff" text-anchor="middle" font-family="Verdana,Geneva,DejaVu Sans,sans-serif" text-rendering="geometricPrecision" font-size="110">

why_not_llms.md

@@ -0,0 +1,177 @@
+# Why not LLMs?
+
+* [Legal Ramifications](#legal-ramifications)
+  * [Legal Cases And Law Problems](#legal-cases-and-law-problems)
+  * [License Problems](#license-problems)
+* [Stolen Training Data](#stolen-training-data)
+* [Environmental Impact](#environmental-impact)
+* [Labor](#labor)
+* [Poor Code Quality](#poor-code-quality)
+  * [Deskilling](#deskilling)
+  * [Infosec risks](#infosec-risks)
+* [Health and Safety](#health-and-safety)
+  * [Ties to the War Industrial Complex](#ties-to-the-war-industrial-complex)
+  * [Effects on Policing](#effects-on-policing)
+  * [Maintainer Fatigue](#maintainer-fatigue)
+* [Effect on Hardware Prices](#effect-on-hardware-prices)
+
+## Legal Ramifications
+
+LLMs are often trained on, and thus prone to regurgitate (either completely, or in-part), chunks of code that are licensed under terms which have specific legal requirements that a contributor using LLMs may not understand or even be aware of when making a contribution. Regardless of this ignorance, it falls to the repo's owner to comply with the terms of any and all licensed code integrated into their project.
+
+### Legal Cases And Law Problems
+
+* [GitHub Copilot litigation](https://githubcopilotlitigation.com/)
+* [IEEE article explaining concerns about AI generated code ownership](https://spectrum.ieee.org/ai-code-generation-ownership)
+* [Tracker of broader lawsuits against AI companies](https://chatgptiseatingtheworld.com/2025/11/02/tracker-of-tort-lawsuits-v-ai-companies/)
+
+### License Problems
+
+Legal, copyright, and ethics problems arise, especially with copyleft licenses such as the GNU (A/L)GPL. With the "help" of AI the copyleft code may be "license-washed" very easily.
+
+There are ongoing problems with AI "license-washing" in the FOSS world:
+
+* `chardet` - used an LLM to rewrite the codebase from the LGPL license to Expat/MIT (and later 0-BSD) license, violating the (L)GPL.
+  * relicensed release: <https://github.com/chardet/chardet/releases/tag/7.0.0>
+  * original author's concerns: <https://github.com/chardet/chardet/issues/327>
+  * "consumer's" concerns: <https://github.com/chardet/chardet/issues/331>
+
+## Stolen Training Data
+
+AI companies use data from across the web to train their models, most often without the website owners' and users' consent. Big tech companies like Google and Meta are scraping data from the users of major FOSS projects, such as Mastodon, WordPress, and other ActivityPub-powered and self-hosted software.
+
+* In 2023, [the Washington Post published a list of sources in Google's C4 data set](https://archive.ph/eehKq). A multitude of fediverse instances and personal sites were included. The fediverse is known for its userbase being major proponents of privacy and opt-in consent, making this especially jarring for those who have chosen to use decentralized social media for control over their data.
+* In 2025, [a similar leak of Meta's sources was published](https://archive.ph/NZlf3). Meta's list demonstrates how their integration of ActivityPub into their Threads software has enhanced their ability to scrape content without authorization. Threads is widely blocked in some parts of the fediverse, but their scraping of server CDNs has allowed them to get around that. Notably, both the CDN domains of the managed hosting services masto.host and fedi.monster are included in the list; large servers like mastodon.art, which is hosted by the former and has many artists who've left sites like DeviantArt and others due to their AI scraping of user content, had [media unknowingly scraped](https://mastodon.art/@Curator/115022115346692178).
+* In March 2026, [a research paper](https://arxiv.org/html/2603.20957v2) showed that simply fine-tuning LLMs resulted in outputs containing up to 90% of entire (copyrighted) books, contradicting LLM companies' previous statements in court that their models do not store copies of training data. After fine-tuning exclusively on a single author, the researchers were able to cause the LLM to output works from over 30 completely unrelated authors across different genres. None of the models were explicitly trained on these books by the researchers, which indicates that LLMs always carry with them a considerable amount of copyrighted materials from training.
+
+FOSS projects listed in this repo are using tooling that blatantly disregard licensing and violate of Codes of Conduct, making said tools antithetical to FOSS' purpose.
+
+## Environmental Impact
+
+To start learning a bit more, you can checkout the wikipedia page on [Environmental impact of artificial intelligence](https://en.wikipedia.org/wiki/Environmental_impact_of_artificial_intelligence#Individual_level). We're very open to people contributing other explanations, links, and resources to learn more about this. Here's what we've gathered so far:
+
+- [MIT News: Generative AI's Environmental Impact](https://news.mit.edu/2025/explained-generative-ai-environmental-impact-0117)
+- [MIT Technology Review: We did the math on AI's energy footprint. Here's the story you haven't heard.](https://www.technologyreview.com/2025/05/20/1116327/ai-energy-usage-climate-footprint-big-tech/)
+- [Grantham Institute: What Direct Risks Does AI Pose to the Climate and Environment](https://www.lse.ac.uk/granthaminstitute/explainers/what-direct-risks-does-ai-pose-to-the-climate-and-environment/)
+- [UCLA: AI is Destroying Our Planet](https://newsroom.ucla.edu/stories/opinion-ai-is-destroying-our-planet-we-must-act)
+- [The Guardian: Officials hugely underestimated impact of AI datacentres on UK carbon emissions](https://web.archive.org/web/20260425032459/https://www.theguardian.com/technology/2026/apr/24/officials-hugely-underestimated-impact-of-ai-datacentres-on-uk-carbon-emissions)
+- [KU Leuven Centre for IT & IP Law: The environmental costs of AI: a shake-up of the EU's twin transition](https://www.law.kuleuven.be/citip/blog/the-environmental-costs-of-ai-a-shake-up-of-the-eus-twin-transition/)
+- [Politico: Europe must choose between AI and climate goals, data center lobby says](https://www.politico.eu/article/europe-choose-ai-climate-goals-data-center-chief-warns/)
+- [Australian Parliament: Impacts of AI on the environment](https://www.aph.gov.au/Parliamentary_Business/Committees/Senate/Adopting_Artificial_Intelligence_AI/AdoptingAI/Report/Chapter_6_-_Impacts_of_AI_on_the_environment)
+
+## Labor
+
+AI usage and normalization contributes to labor violations in many ways that are obvious and some you may not be aware of.
+
+On one hand, many things that you think are "AI" are actually humans in another country pretending to be an AI chatbot for you for either extremely low wages or in some cases, no wages e.g. prison labor. This is particularly common for "friend"/"sex" bots, but it is also extremely common in the image/video identification. You can find a bit more info at the following links:
+
+- [Long hours and low wages: the human labour powering AI’s development](https://theconversation.com/long-hours-and-low-wages-the-human-labour-powering-ais-development-217038)
+- [OpenAI Used Kenyan Workers on Less Than $2 Per Hour to Make ChatGPT Less Toxic](https://time.com/6247678/openai-chatgpt-kenya-workers/)
+- ['AI Is African Intelligence': The Workers Who Train AI Are Fighting Back](https://www.404media.co/ai-is-african-intelligence-the-workers-who-train-ai-are-fighting-back/)
+- [These Prisoners Are Training AI: In high-wage Finland, where clickworkers are rare, one company has discovered a novel labor force—prisoners.](https://web.archive.org/web/20260108224812/https://www.wired.com/story/prisoners-training-ai-finland/)
+- [Amazon grocery stores previously reported to use AI actually used people in India](https://www.businessinsider.com/amazons-just-walk-out-actually-1-000-people-in-india-2024-4?op=1)
+
+## Poor Code Quality
+
+Vibe coding / agentic workflows result in poorer code quality, and relaxed oversight practices. These effects may be compounded by the common practice of using additional LLM-based tooling to provide code-reviews.
+
+* [How I Dropped Our Production Database and Now Pay 10% More for AWS](http://archive.today/2026.03.06-144058/https://alexeyondata.substack.com/p/how-i-dropped-our-production-database)
+* [Claude Tested Everything Except the One Thing That Mattered (AI agent refuses to follow explicit instructions to test `createPost()` in increasingly erratic ways)](http://archive.today/2026.03.09-201135/https://christophermeiklejohn.com/ai/claude/2026/03/08/claude-tested-everything-except-the-one-thing-that-mattered.html)
+* [Amazon calls engineers for a “deep dive” internal meeting to discuss “GenAI”-related outages](https://ghostarchive.org/archive/3TfgF)
+* GitClear has released reports in [2024](https://www.gitclear.com/coding_on_copilot_data_shows_ais_downward_pressure_on_code_quality) and [2025](https://www.gitclear.com/ai_assistant_code_quality_2025_research) indicating a worsening of key code quality metrics correlating with increased LLM adoption.
+
+### Deskilling
+
+There is increasing evidence to show that LLMs negatively impact developers' coding abilities:
+
+* [Brains show less activity when completing tasks with LLMs](https://arxiv.org/abs/2506.08872) compared to completing tasks with search or completing tasks without digital help.
+* [Developers who use early-2025 LLMs](https://metr.org/blog/2025-07-10-early-2025-ai-experienced-os-dev-study/) reported higher subjective performance, but were measured to have lower objective performance. This gap between subjective and objective performance was considered notable.
+* In an [Anthropic study](https://www.anthropic.com/research/AI-assistance-coding-skills), learners using LLMs demonstrated lower learning rates on average compared to learners not using LLMs.
+* [A recent study uses the term "cognitive surrender"](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=6097646) to describe the way humans tend to offload key critical thinking skills onto LLMs, even when the output is wrong.
+* A paper entitled ["AI Assistance Reduces Persistence and Hurts Independent Performance"](https://arxiv.org/abs/2604.04721) from April 2026 by academics from MIT, Oxford, UCLA, and Carnegie Mellon showed alarming evidence that performing a variety of tasks with the help of AI for only 10 minutes causes "inpaired unassisted performance and reduced persistence". The researchers noted that "although AI assistance improves performance in the short-term, people perform significantly worse without AI and are more likely to give up"; they also pointed out that "these findings are particularly concerning because persistence is foundational to skill acquisition and is one of the strongest predictors of long-term learning".
+
+### Infosec risks
+
+LLM usage results in massive security holes.
+
+* [Meta Security Researcher's AI Agent Accidentally Deleted Her Emails](http://archive.today/2026.02.26-153034/https://www.pcmag.com/news/meta-security-researchers-openclaw-ai-agent-accidentally-deleted-her-emails)
+* [Moltbook's "vibe-coded" breach is the future of security failures](https://thehill.com/opinion/cybersecurity/5744310-ai-powered-security-risks/)
+* [In a study evaluating over 500k code samples, LLM-generated code was found to contain more high-risk security vulnerabilities than human-generated code](https://arxiv.org/abs/2508.21634)
+* [LLMs make up package names, making them vulnerable to incorporating malicious code in "slopsquatting" attacks](https://www.theregister.com/2025/04/12/ai_code_suggestions_sabotage_supply_chain/) ([Arxiv study](https://arxiv.org/abs/2406.10279))
+
+## Health and Safety
+
+There's been a number of high profile incidents that have resulted in endangerment or death. Here's some examples:
+
+* [AI Toy Exposed 50,000 Logs of Its Chats With Kids to Anyone With a Gmail Account](https://archive.ph/dX5xd)
+
+* <details>
+      <summary>Content Warning: Suicide</summary>
+
+  * [Wikipedia: Deaths linked to chatbots](https://en.wikipedia.org/wiki/Deaths_linked_to_chatbots)
+  * [AI chatbot pushed a teen to kill himself, a lawsuit against its creator alleges](https://apnews.com/article/chatbot-ai-lawsuit-suicide-teen-artificial-intelligence-9d48adc572100822fdbc3c90d1456bd0)
+
+  </details>
+
+[LLM use has also been linked to new-onset psychosis](https://pmc.ncbi.nlm.nih.gov/articles/PMC12863933/).
+
+### Ties to the War Industrial Complex
+
+A lot of AI companies also work directly with nation states for use in their Departments of War (sometimes called Defense) which in turn leads to further AI usage during war and invasions. This is coupled with [NYT: Palantir, Anthropic and small start-ups are generating rewards from their investments in defense tech](https://www.nytimes.com/2026/03/18/technology/silicon-valley-war-defense-tech.html).
+
+As another example [NPR: OpenAI announced Pentagon deal after Trump banned Anthropic](https://www.npr.org/2026/02/27/nx-s1-5729118/trump-anthropic-pentagon-openai-ai-weapons-ban) which was due to the USA Department of War [launching an AI acceleration strategy](https://web.archive.org/web/20260113071131/https://www.war.gov/News/Releases/Release/Article/4376420/war-department-launches-ai-acceleration-strategy-to-secure-american-military-ai/).
+
+Due to the nature of LLMs being only kind of as good as the data they are trained on, this can lead to additional civilian deaths and housing/infrastructure damage either intentionally or not. Examples:
+
+<details>
+  <summary>Content Warning: War details, death</summary>
+
+  - [Gaza: UN experts deplore use of purported AI to commit ‘domicide’ in Gaza, call for reparative approach to rebuilding](https://www.ohchr.org/en/press-releases/2024/04/gaza-un-experts-deplore-use-purported-ai-commit-domicide-gaza-call)
+  - [Lavender & Where’s Daddy: How Israel Used AI to Form Kill Lists & Bomb Palestinians in Their Homes](https://www.democracynow.org/2024/4/5/israel_ai)
+  - [Microsoft says it provided AI to Israeli military for war](https://apnews.com/article/microsoft-israel-military-gaza-hamas-artificial-intelligence-20b2adb438b39ee9cb6eb2f52c1ae44a)
+  - [Google has dropped its promise not to use AI for weapons](https://theconversation.com/google-has-dropped-its-promise-not-to-use-ai-for-weapons-its-part-of-a-troubling-trend-249169)
+  - ["We want to use it for everything": How Project Maven became central to America’s AI-powered warfare](https://web.archive.org/web/20260312035736/https://www.independent.co.uk/news/world/americas/project-maven-ai-us-airstrike-iraq-anthropic-b2929138.html)
+
+</details>
+
+All of this to remind you that if you use AI, you're helping to support these companies and the additional activities they participate in, outside of generative code or images.
+
+### Effects on Policing
+
+Police have quickly embraced AI, which has already directly led to people being jailed for things they've never done. As examples:
+
+- [This Grandmother was jailed for 6 months after an AI error linked her to a crime in a state she had never even visited](https://www.the-independent.com/news/world/americas/crime/tennessee-grandmother-ai-arrest-error-north-dakota-b2938261.html)
+- [How Wrongful Arrests Based on AI Derailed 3 Men's Lives](https://web.archive.org/web/20260111202754/https://www.wired.com/story/wrongful-arrests-ai-derailed-3-mens-lives/)
+
+This is, in part, due to companies such as Amazon [Aggressively pushing police to use AI](https://web.archive.org/web/20260116082026/https://www.forbes.com/sites/thomasbrewster/2025/10/01/inside-amazons-aggressive-push-to-get-cops-using-ai-surveillance/) which they do through both facial recognition and offering compute for predictive policing. With regards to facial recognition, here's an example of how it too can lead to false arrests: [Face Recognition on Flawed Data](https://www.flawedfacedata.com/#art-or-science).
+
+There have been warnings about AI in policing, particularly around racial bias, such as:
+
+- [Bennan Center of Justice: The Dangers of Unregulated AI in Policing](https://www.brennancenter.org/our-work/research-reports/dangers-unregulated-ai-policing)
+- [OxJournal: Predictive Policing or Predictive Prejudice? A Study of the Legal, Historical and Ethical Implications of AI in Policing](https://www.oxjournal.org/predictive-policing-or-predictive-prejudice/)
+- [The Guardian: Police AI Chief admits crime fighting tech will have bias...](https://web.archive.org/web/20260224070735/https://www.theguardian.com/technology/2026/feb/24/police-ai-chief-admits-crime-fighting-tech-will-have-bias-but-vows-to-tackle-it)
+- [A third of all Black children were flagged by a child services agency](https://loganstapleton.com/wp-content/uploads/2022/04/Extended_Analysis__How_Child_Welfare_Workers_Reduced_Racial_Disparities_in_Algorithmic_Decisions.pdf)
+
+### Maintainer Fatigue
+
+Having to deal with the onslaught of many LLM written pull requests and issues, causes real maintainer burnout that stagnates projects as maintainers become overwhelmed with half baked, poorly written, insecure code. Here's some examples:
+
+* [Overrun with AI slop, cURL scraps bug bounties to ensure “intact mental health”](https://arstechnica.com/security/2026/01/overrun-with-ai-slop-curl-scraps-bug-bounties-to-ensure-intact-mental-health/)
+* [Godot maintainers struggle with 'draining and demoralizing' AI slop submissions](https://www.theregister.com/2026/02/18/godot_maintainers_struggle_with_draining/)
+* [An AI Agent Published a Hit Piece on Me (matplotlib)](http://archive.today/2026.02.19-045842/https://theshamblog.com/an-ai-agent-published-a-hit-piece-on-me/)
+
+## Effect on Hardware Prices
+
+The demand for construction and outfitting of new data-centers to host AI/LLM compute capacity has overwhelmed global supply and production of multiple hardware components. Memory, Storage, and GPUs have seen massive increases in price for both consumer and enterprise models upward of 400% in some cases.
+
+The lack of supply has led large system-builders to purchase production capacity from OEMs well in-advance of delivery leading some manufacturers to end consumer-oriented product lines in favor of enterprise capacity.
+
+The down-stream effects for consumers is that near all electronic devices which contain memory and storage will see their prices rise and availability decline. Those who already own existing electronics and computer hardware components may also find themselves unable to have their devices repaired or replaced under warranty.
+
+- [The RAM shortage is coming for everything you care about](https://www.theverge.com/tech/880812/ramageddon-ram-shortage-memory-crisis-price-2026-phones-laptops)
+
+- [Western Digital is already sold out of hard drives for all of 2026 — chief says some long-term agreements for 2027 and 2028 already in place](https://www.tomshardware.com/pc-components/hdds/western-digital-is-already-sold-out-of-hard-drives-for-all-of-2026-chief-says-some-long-term-agreements-for-2027-and-2028-already-in-place)
+
+- [The 2026 storage crisis: Why AI data centers are hoarding every hard drive on the market](https://www.howtogeek.com/dont-count-on-hdds-to-save-you-from-rising-storage-costs/)
+
+This all results in shrinking the pool of people who have access to building home computers for any purpose, from gaming to coding to home labs, which in turn makes the tech industry less diverse due to people who have been historically marginalized having less financial resources to learn the skills at home. When this is factored in with the price of college being unaffordable in many places, we will see a sharper decline in disabled people, people of color, women, and the queer community entering the tech industry.