mirror of
https://codeberg.org/small-hack/open-slopware.git
synced 2026-06-03 15:47:02 +02:00
fix stolen training data section to be nested properly and update headings a bit to make it more readable since we have so many sections now
This commit is contained in:
parent
c35dc36efd
commit
e058be39b6
1 changed files with 12 additions and 12 deletions
24
README.md
24
README.md
|
|
@ -11,7 +11,7 @@ To Contribute, checkout our [`CONTRIBUTING.md`](./CONTRIBUTING.md).
|
|||
> [!Note]
|
||||
> This is a fork of a repo by the same name maintained by the @gen-ai-transparency org on Codeberg. If they make their repo available again, we will contribute back.
|
||||
|
||||
* [Definitions](#definitions)
|
||||
* [Definitions](#definitions)
|
||||
* [Tainted Software](#tainted-software)
|
||||
* [Browsers](#browsers)
|
||||
* [Command-Line Shells](#command-line-shells)
|
||||
|
|
@ -39,8 +39,8 @@ To Contribute, checkout our [`CONTRIBUTING.md`](./CONTRIBUTING.md).
|
|||
* [System Services and Daemons](#system-services-and-daemons)
|
||||
* [Operating Systems](#operating-systems)
|
||||
* [Why not LLMs?](#why-not-llms)
|
||||
* [Stolen Training Data](#stolen-training-data)
|
||||
* [Legal Ramifications](#legal-ramifications)
|
||||
* [Stolen Training Data](#stolen-training-data)
|
||||
* [Environmental Impact](#environmental-impact)
|
||||
* [Poor Code Quality](#poor-code-quality)
|
||||
* [Healthy and Safety](#healthy-and-safety)
|
||||
|
|
@ -55,7 +55,7 @@ To Contribute, checkout our [`CONTRIBUTING.md`](./CONTRIBUTING.md).
|
|||
| sloperator | A person who uses AI prompts to generate anything, typically code or images. |
|
||||
| slopshop | Company, Organization, or Group of sloperators working together to use AI to generate content. |
|
||||
|
||||
## Tainted Software
|
||||
# Tainted Software
|
||||
|
||||
### Browsers
|
||||
|
||||
|
|
@ -221,10 +221,14 @@ This is for both social media websites and apps.
|
|||
|---|---|---|
|
||||
| [Linux Kernel](https://kernel.org/) | BSD? Honestly this one's tough | [Maintainers are explicitly trying out the technology and considering LLM-based reviews](https://lwn.net/Articles/1041694/) |
|
||||
|
||||
## Why not LLMs?
|
||||
# Why not LLMs?
|
||||
|
||||
Could use some help writing this with concrete receipts on environmental, social, political, and economic/labor harms.
|
||||
|
||||
## 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 sloperator 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.
|
||||
|
||||
### Stolen Training Data
|
||||
|
||||
AI companies use data from across the web for training 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 AcitivityPub-powered and self-hosted software.
|
||||
|
|
@ -234,21 +238,17 @@ AI companies use data from across the web for training their models, most often
|
|||
|
||||
FOSS projects listed in this repo are using tooling that blatantly disregards licensing and violates even the most basic of Code of Conducts, making said tools antithetical to FOSS' purpose.
|
||||
|
||||
### Legal Ramifications
|
||||
|
||||
1. 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 sloperator 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.
|
||||
|
||||
See also: [lawsuits against AI companies](https://chatgptiseatingtheworld.com/2025/11/02/tracker-of-tort-lawsuits-v-ai-companies/)
|
||||
|
||||
### Environmental Impact
|
||||
## 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.
|
||||
|
||||
### Poor Code Quality
|
||||
## Poor Code Quality
|
||||
|
||||
Vibe coding results in poorer code quality and is compounded by having addition LLMs do the reviews of both bugs and pull requests in repos.
|
||||
|
||||
#### Healthy and Safety
|
||||
### Healthy and Safety
|
||||
|
||||
There's been a number of high profile incidents that have resulted in endangerment or death. Here's some examples:
|
||||
|
||||
|
|
@ -261,7 +261,7 @@ There's been a number of high profile incidents that have resulted in endangerme
|
|||
|
||||
</details>
|
||||
|
||||
#### Maintainer Fatigue
|
||||
### 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:
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue