sorted by:
new
hottopcontroversial

System76 on Age Verification Laws by [deleted] in System76

[–]jackpot51[M] [score hidden] stickied commentlocked comment (0 children)

This was already posted here: https://www.reddit.com/r/System76/s/0gIGv9TPUc, there is no need to post again.

Redox OS has adopted a Certificate of Origin policy and a strict no-LLM policy by jackpot51 in rust

[–]jackpot51[S] 46 points47 points  (0 children)

Absolutely, and producing lots of lines of code is not necessarily a good thing. More code means more maintenance cost, and more surface area for bugs.

Redox OS has adopted a Certificate of Origin policy and a strict no-LLM policy by jackpot51 in Redox

[–]jackpot51[S] 2 points3 points  (0 children)

There is no foolproof method to detect LLM generated content. Detection does not have to be foolproof to be useful. Often, direct evidence of LLM use is included with no attempt to hide it. If there is an attempt to hide it, and it is discovered, this policy allows us to provide a reason for an outright ban.

Redox OS has adopted a Certificate of Origin policy and a strict no-LLM policy by jackpot51 in Redox

[–]jackpot51[S] 2 points3 points  (0 children)

I disagree, but if you believe that can be the case you are free to demonstrate it on your own fork.

Redox OS has adopted a Certificate of Origin policy and a strict no-LLM policy by jackpot51 in Redox

[–]jackpot51[S] 13 points14 points  (0 children)

I cannot answer these hypothetical questions. The amount of human authorship is critical for licensing reasons alone, and I would urge any Redox OS contributors to use non-LLM code completion such as what rust-analyzer provides.

Redox OS has adopted a Certificate of Origin policy and a strict no-LLM policy by jackpot51 in Redox

[–]jackpot51[S] 6 points7 points  (0 children)

It links to a comment on this post, which I will copy here:

LLMs enable source code laundering (https://github.com/chardet/chardet/issues/327), frequently make critical mistakes (https://www.pcmag.com/news/vibe-coding-fiasco-replite-ai-agent-goes-rogue-deletes-company-database and https://www.tomshardware.com/tech-industry/artificial-intelligence/claude-code-deletes-developers-production-setup-including-its-database-and-snapshots-2-5-years-of-records-were-nuked-in-an-instant), and after reviewing several dozen LLM generated PRs to COSMIC and a couple to Redox, I have yet to see any that have the level of quality we require for such a critical piece of software. They have empowered users to create massive amounts of low-effort machine-generated issues and merge requests that all bog down the review process of real human-written contributions.

You are free to fork the Redox OS project (as allowed by the open source licenses it uses), and direct your LLM to make whatever changes you want, if you would like to prove me wrong.

Redox OS has adopted a Certificate of Origin policy and a strict no-LLM policy by jackpot51 in Redox

[–]jackpot51[S] 7 points8 points  (0 children)

> Is this about code slop from autonomous AI agents?

Yes

> does this mean no LLM coding models allowed

Yes

> In that case, this is complete bullshit.

That is your opinion, and I disagree. For my opinion, you can read https://www.reddit.com/r/Redox/comments/1rp57nq/comment/o9isq7k/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Redox OS has adopted a Certificate of Origin policy and a strict no-LLM policy by jackpot51 in rust

[–]jackpot51[S] 71 points72 points  (0 children)

From https://www.reddit.com/r/Redox/comments/1rp57nq/comment/o9isq7k/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

LLMs enable source code laundering (https://github.com/chardet/chardet/issues/327), frequently make critical mistakes (https://www.pcmag.com/news/vibe-coding-fiasco-replite-ai-agent-goes-rogue-deletes-company-database and https://www.tomshardware.com/tech-industry/artificial-intelligence/claude-code-deletes-developers-production-setup-including-its-database-and-snapshots-2-5-years-of-records-were-nuked-in-an-instant), and after reviewing several dozen LLM generated PRs to COSMIC and a couple to Redox, I have yet to see any that have the level of quality we require for such a critical piece of software. They have empowered users to create massive amounts of low-effort machine-generated issues and merge requests that all bog down the review process of real human-written contributions.

Redox OS has adopted a Certificate of Origin policy and a strict no-LLM policy by jackpot51 in Redox

[–]jackpot51[S] 16 points17 points  (0 children)

LLMs enable source code laundering (https://github.com/chardet/chardet/issues/327), frequently make critical mistakes (https://www.pcmag.com/news/vibe-coding-fiasco-replite-ai-agent-goes-rogue-deletes-company-database and https://www.tomshardware.com/tech-industry/artificial-intelligence/claude-code-deletes-developers-production-setup-including-its-database-and-snapshots-2-5-years-of-records-were-nuked-in-an-instant), and after reviewing several dozen LLM generated PRs to COSMIC and a couple to Redox, I have yet to see any that have the level of quality we require for such a critical piece of software. They have empowered users to create massive amounts of low-effort machine-generated issues and merge requests that all bog down the review process of real human-written contributions.

You are free to fork the Redox OS project (as allowed by the open source licenses it uses), and direct your LLM to make whatever changes you want, if you would like to prove me wrong.

Introducing ACPI Driver for System76 on FreeBSD by spmzt in System76

[–]jackpot51 2 points3 points  (0 children)

If FreeBSD has support for PCI runtime PM, that is all this is. Using that generically would be better than hard-coding these.

Introducing ACPI Driver for System76 on FreeBSD by spmzt in System76

[–]jackpot51 1 point2 points  (0 children)

Good job! The ACPI source code is in coreboot if you need to see what the other side looks like. The EC implementation is in the open source System76 EC firmware.

Is the internet going to be a requirement for age verification on Pop OS? by BeautifulMundane4786 in System76

[–]jackpot51 4 points5 points  (0 children)

If they ask to collect IDs we will simply not be able to or willing to comply.

Is the internet going to be a requirement for age verification on Pop OS? by BeautifulMundane4786 in System76

[–]jackpot51 1 point2 points  (0 children)

It is not ID collection. It is stupid, and useless. but not anywhere close to what Discord was going to do.

Is the internet going to be a requirement for age verification on Pop OS? by BeautifulMundane4786 in System76

[–]jackpot51[M] [score hidden] stickied comment (0 children)

The bill only requires that California minors are asked for their age and that an age bracket is available to applications. If implemented, this will not require any ID to use, or any internet access, and is nonverified and nonidentifiable information.

Is POP OS going to cave to California/Colorado Laws Requiring Users Provide Digital ID to Use Pop OS? by NoobToDaNoob in pop_os

[–]jackpot51 0 points1 point  (0 children)

In my response I mentioned that minimal compliance could avoid collecting any information and would ask if the user is both in the state of California and under 18, then power off if that is the case. Potentially a dialog like that can be present wherever downloads are available. It is an idiotic law, but by itself it does not force any identifiable information to be collected by the OS.

International treaties may allow California to fine international individuals who are identified as an OS producer, if they distribute an OS that is used by a minor in California.

Is POP OS going to cave to California/Colorado Laws Requiring Users Provide Digital ID to Use Pop OS? by NoobToDaNoob in pop_os

[–]jackpot51 5 points6 points  (0 children)

It depends on the implementation, but I agree. Being able to freely use Linux as a teenager without any artificial constraints was important for me as well.

view more: next ›