Add brush shell (#826)

Reviewed-on: https://codeberg.org/small-hack/open-slopware/pulls/826
Reviewed-by: Admin <vleermuis-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:
@@ -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?
 

CODE_OF_CONDUCT.md

@@ -7,7 +7,7 @@
 - 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.
@@ -32,7 +32,7 @@ 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.
 
 # On handling rude comments in this repo specifically
 
@@ -53,6 +53,10 @@ We're going to do a 2 strike rule here with an optional warning. You are out on
 
 # 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/small-hack/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](https://codeberg.org/small-hack/open-slopware/src/branch/main#why-not-llms) section of our README.
+
 - We don't want drive by sarcastic comments.
 
 - No references to bodily fluids (vomit, urine, feces), this includes emojis. It's gross and unproductive.
@@ -65,14 +69,20 @@ 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 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)
+
 ## Accessibility
 
 ### Alt Text

CONTRIBUTING.md

@@ -45,6 +45,8 @@ The criteria for being included in this repository are any of following tags. Yo
 
 Alternatives should not contain any slop as defined by our tagging system above.
 
+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.
+
 ### 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.
@@ -82,4 +84,4 @@ In either case, one thing you can do is react positively to a given upstream iss
 
 # Social media
 
-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.
+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. Please also don't quote social media posts in the "Why not LLMs" section.

FAQ.md

@@ -0,0 +1,71 @@
+# 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's FOSS, has a code of conduct (even if it's a solo project), and a No AI Policy, 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/small-hack/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?](https://codeberg.org/small-hack/open-slopware#why-not-llms) 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 @vleermuis-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, beyond "vibecoded" being added in some extreme cases. 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.
+
+## 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?](https://codeberg.org/small-hack/open-slopware#why-not-llms) 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/small-hack/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/small-hack/open-slopware/src/branch/main/CONTRIBUTING.md#removal).)
+
+## 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/small-hack/open-slopware/src/branch/main/CONTRIBUTING.md#removal).
+>
+> 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](https://codeberg.org/small-hack/open-slopware#environmental-impact)
+> - [ties to the war industrial complex](https://codeberg.org/small-hack/open-slopware#ties-to-the-war-industrial-complex)
+> - [effect on hardware prices hurting newcomers to the industry](https://codeberg.org/small-hack/open-slopware#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?](https://codeberg.org/small-hack/open-slopware#why-not-llms) section.
+
+## What about "Open Source AI"?
+
+> Yes, simply being open source does not resolve the issues listed in our [Why Not LLMs?](https://codeberg.org/small-hack/open-slopware#why-not-llms) section and thus such projects will still be included on this list.
+
+## 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, concreate, 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 an 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 mtaintiners 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/small-hack/open-slopware#definitions) stay and are not up for debate.

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:
+```