Contributors are expected to understand, review, test, and, where appropriate, modify AI-assisted output before incorporating it into Debian. Blindly accepting or uploading AI-generated material without appropriate human review is inconsistent with Debian's established development practices. We [encourage] our contributors to disclose whether a contribution was made with AI [assistance], but do not require them to do so.
I agree. Disclosure of A.I. use should be mandatory.
My main concern with A.I. use is its ability to hide incompetence. If a new agent introduces code that was entirely written by illegal-software that violates copyright law--A.I.--then that should be made clear, even if competent-programmers review the new inclusion and approve of it. Otherwise people are left with the impression that this new agent is a competent programmer. A.I. use--undisclosed--creates false reputations.
The disclosure being encouraged and not mandatory is purely to protect the egos of programmers currently utilizing A.I. products.
However I do respect their decision and I maintain projects should be self governing.
I disagree. For one, it's unenforceable, just like outright banning it.
But AI assistance can also mean a lot of different things, from outright vibecoding through autocomplete up to only asking it to so review. It diminishes the human work in the eyes of other people, because a simple disclaimer doesn't distinguish between the work done, and also encourages people to point out to AI as a scapegoat for their mistakes.
Good code always was and should always be one where a human is fully responsible for it; if you decide to vibecode and happens to end up with perfect code, good; if you write it fully yourself but it's crap it doesn't absolve you that you didn't use AI...
It's a tool, so use it responsibly like any other tool and stand behind your code no matter what tools you used.
But the issue is that in practise, there is no viable way to verify wether or not AI has been used at all. In other words, the disclosure of AI use entirely depends on the person providing the code, wether disclosure is mandated or not.
If there was enforcment to disclose AI use, it would create a false assumption that code which claims no AI use, is verified to contain mo AI use, which again, cannot be verified by anyone.
So it's not that it's hard to enforce, it's not that it's impossible to enforce 100%, it's that there currently is no viable way to enforce it at all.
look at visual studio's Intellisense and compare it to the last version that didn't advertise Ai, there aren't that many functional differences and if you don't keep up with the marketing you could very easily miss that it is Ai powered.
I disagree. For one, it's unenforceable, just like outright banning it.
Agreed. I an aware a lot of people contributed to the Linux kernel, without disclosing they used ai.
Good code always was and should always be one where a human is fully responsible for it; if you decide to vibecode and happens to end up with perfect code, good; if you write it fully yourself but it's crap it doesn't absolve you that you didn't use AI...
Yeah. I do not blame the ai for writing the code, but rather the person to accept and push that code even if they know it is crap.
I do respect their decision and I maintain projects should be self governing.
Me too, but I also think that governance isn't as simple as "we get to decide what we do", it also interacts with how well the decision-makers understand their domain and their broader it sits in, both of which are potentially reduced as a consequence of relying on AI.
Also there is the possibility of AI tools dominating workflows and then getting ripped away (either as the corporates raise costs, or the bubble bursts and they collapse), leaving a project overwhelmed with a unmanageably large array of weaknesses. In that scenario self-governance starts to become irrelevant.
My main concern with A.I. use is its ability to hide incompetence.
You mean like tab-completion in modern IDEs? Shouldn't devs know all the function calls and methods of the standard libraries of the language they're programming in?
Not at all, because it's impossible to know for sure if committed code had some form of AI generated parts, AI assisted review, prototyping, etc.
By making it mandatory you can potentially alienate good developers who may feel their work ethics would be scrutinized negatively (like in these comments).
An LLM is just a tool. Some iterations have some value in some circumstances. In those cases it's fine. But look around at the comments here and you'll see many people basically accusing Debian of selling out. If a dev sees that reaction then they may not want to disclose their own use of LLMs.
Why would you not want to disclose though? Is it because of shame? Because you are unable to defend your choice? If it's "just a tool", is that not enough to defend your choice?
To be clear: the alternative policy we're talking about isn't "LLMs are bad, don't use them", it's "Let us know when you are using LLMs"
When people do code review off a pull request and sees it’s slop, it will go back to the developer to fix it. I guess if a person submit too much slop, they will get banned or something similar.
However, I don’t know the Debian process to have new code submitted, but would guess that it have to be more than one person to go from code to build a package.
It's pretty much the same policy as the Linux kernel, but still disappointing.
I've been dumping things left and right as they decide Claude is their buddy, and that won't stop because the same idiots who dropped decent init systems for that RedHat tech bro's mess decided not to block it.
I am most concerned about that. If the legal position on copyright of AI code is decided in the future an audit or tracking of AI contributions in the codebase may be necessary to understand risk and exposure.
Granted you can't make people disclose AI assistance with 100% accuracy but I would expect a majority to comply.
Former Debian Project Leader Lucas Nussbaum expressed regret on the results of the vote, writing: "On a very personal note, I regret that the winning option does not acknowledge all the legitimate concerns around AI: environmental impact, copyright and licensing uncertainty, the health of Free Software communities, and the strain of aggressive scraping on the open web."
The mass-extinction causing orphan-crushing torment nexus is a tool, just like other tools we use. And it’s clearly a useful one.
There are other questions around it, like if we should be complicit in killing billions of people, and making more than 50% of genera go extinct, via its CO2e releases and water use, but “is it useful” is no longer one of those questions.
The Debian project has been and will continue to be about the technology.
Sure, the people who use it is important and often a very motivating part of the project, but in the end that’s a side benefit, not the point of the project.
In the Debian community we do open source because it results in better technology, not because of ethical reasons.
And so we make decisions primarily based on technical merit. Not fear of causing a mass extinction.
Former Debian Project Leader Lucas Nussbaum expressed regret on the results of the vote, writing: "On a very personal note, I regret that the winning option does not acknowledge all the legitimate concerns around AI: environmental impact, copyright and licensing uncertainty, the health of Free Software communities, and the strain of aggressive scraping on the open web."
IMHO: They talk about having it go through the exact same due diligence as normal contribs and a human has to be responsible. I think it's an acceptable compromise.
A human cannot be responsible for AI written code.
Even if you personally vet every single line, you are still simply code reviewing an AI before you pass it to someone else.
A human did not write nor understand it, and thus cannot be responsible for it and thus should never submit it.
Not to mention the code review itself becomes a very tedious process: sifting through hundreds of lines of AI garbage and token expiry. It's downright rude to expect a volunteer to check hundreds of lines of garbage you didnt even bother writing.
Signed, disgruntled software engineer who refuses to use my jobs "optional" ai feature
At first I was afraid that they would allow for an irresponsible use. But no, they explicitly say "responsible", so that danger is no more. I'm very much relieved.
Also they explicitly mention that humans will remain accountable. Not Nature, or Fate, or the gods; mark that. Good thinking there!
I see this a lot in clanker apologia, but it's never clear what "accountable" actually entails. Unless it's something of the order of a first-offense permanent ban from the project then it's not going to dissuade anyone from being lazy meat proxies.
Agreed, that was a large part of why I chose debian (and never considered ubuntu) as my 'back up' distro, just in case my distro of choice (or arch above it) decided to do something daft.
(But I'll keep watch to see of they don't revert course because "the models are now too powerful", since it is a policy from 2024)
The policy
Gentoo Council has voted on 2024-04-14 on the following policy:
It is expressly forbidden to contribute to Gentoo any content that has been created with the assistance of Natural Language Processing artificial intelligence tools. This motion can be revisited, should a case be made for such a tool that does not pose copyright, ethical and quality concerns.
This policy affects Gentoo contributions and the official Gentoo projects. It does not prohibit adding packages for AI-related software or software that is being developed with the help of such tools upstream.
I think this bit makes it clear that shipping LLM code from the kernel that wasn't contributed by Gentoo is fine:
This policy affects Gentoo contributions and the official Gentoo projects. It does not prohibit adding packages for AI-related software or software that is being developed with the help of such tools upstream.
It's hard to be upset. I'm not a Debian maintainer, or even someone paid to program. But here a group of people got together and said yes to allowing AI. I feel like on some level you have to accept that answer. I'm curious why they made that decision I guess.
It's not like it matters, the kernel is being sloppified and that will affect all distros. Shame that this happens right as linux is beginning to get popularity.
I had debian installed as back up distro's, just for something that wasn't arch based.
The debian partitions were deleted from the arch based distro's installed on both pc's today.
I was waiting to see which way debian was heading on this, but was fairly certain they were going to shit due to the choices that were being voted on, and how none of them appeared to be anti-ai. They seemed deliberately verbose knowing that most people scan text at best these days.
Time to look around again I guess, I've never looked into BSD, Hurd, Solaris...
The GNU Hurd is probably not going to be for you unless you have Ethernet and an old thinkpad or dell laptop. In the mailing list, I know the main devs are usually against ai contributions, although I am unaware if they have a policy.
I would recommend using netBSD because the devs have a clear stance on no rust and no llm usage. There is also openBSD which has the best code quality of the three BSD's, and I think had 2 vulnerabilities in a decade.
I have also heard of solaris, but never had a clue what it was.
I am pretty sure that is the enterprise OS owned by Oracle. It is closed source.
All I want is an os I can trust, that is logical, works, and stays out of my way.
NetBSD or openBSD is your best bet. You will have to install the desktop environment yourself though, unless you like their cwm. FreeBSD is the most popular BSD, but they are using AI to find security vulnerabilities.
Do you feel weird lately? Maybe you need to change something in your life to feel better. If you need help, please seek out medical or psychological professionals, even if you just want to confirm you're healthy.
If this AI distro crap keeps going, I'm going back to using my Android (Pixel 10a and GrapheneOS) phone for everything. Not the best option but better than using a vibe-coded distro.
All I need is a monitor and wall mount for the monitor. Connect a hub and charger (phone does pass-through charging), a Bluetooth keyboard and mouse.
Some workflow will have to change, Cryptpad instead of LibreOffice for example.
People out there who think they can avoid AI this way are really just delusional. Its everywhere at this point.
If its not in the software you are using, the software that runs the software has it. Or the software that runs the software that runs the software. Its inescapable.
You're on the internet? Millions of lines of AI code are probably involved in you seeing this message across the entire infrastructure needed to allow this.
So I'm going quitting Debian. Not only quitting it, but I'm seriously considering starting to actively boycott and sabotage them.
I know that I may not achieve any big change on my own, or even if I had collaborators, but at least I will know that I was on the right side of history.
By all means quit using Debian. That’s your prerogative. But claiming you are going to sabotage a community volunteer run, non profit, open source community is just dumb. Good news is that you won’t actually do it, but still, you sound dumb.
Do you know what actually I mean by sabotage? No, I don't mean hack them or anything like that, I just mean interfere with them because, non profit or not, what they're doing with AI is totally unethical and prejudicial
90 Comments
unemployedclaquer@sopuli.xyz · 63 pts · 2d
naught101@lemmy.world · 65 pts · 2d
That last bit is a bad idea
dropdrip@lemmy.ml · 34 pts · 2d
I agree. Disclosure of A.I. use should be mandatory.
My main concern with A.I. use is its ability to hide incompetence. If a new agent introduces code that was entirely written by illegal-software that violates copyright law--A.I.--then that should be made clear, even if competent-programmers review the new inclusion and approve of it. Otherwise people are left with the impression that this new agent is a competent programmer. A.I. use--undisclosed--creates false reputations.
The disclosure being encouraged and not mandatory is purely to protect the egos of programmers currently utilizing A.I. products.
However I do respect their decision and I maintain projects should be self governing.
amju_wolf@pawb.social · 12 pts · 2d
I disagree. For one, it's unenforceable, just like outright banning it.
But AI assistance can also mean a lot of different things, from outright vibecoding through autocomplete up to only asking it to so review. It diminishes the human work in the eyes of other people, because a simple disclaimer doesn't distinguish between the work done, and also encourages people to point out to AI as a scapegoat for their mistakes.
Good code always was and should always be one where a human is fully responsible for it; if you decide to vibecode and happens to end up with perfect code, good; if you write it fully yourself but it's crap it doesn't absolve you that you didn't use AI...
It's a tool, so use it responsibly like any other tool and stand behind your code no matter what tools you used.
atopi@piefed.blahaj.zone · 9 pts · 1d
If people thought "its impossible to catch everyone so why bother trying to catch anyone at all" when making laws, no laws would exist
Kangae_Hishiryo@scribe.disroot.org · 4 pts · 1d
THIS, THIS, THIS
Basically, a nirvana fallacy/perfect solution fallacy.
aski3252@lemmy.world · 2 pts · 1d
But the issue is that in practise, there is no viable way to verify wether or not AI has been used at all. In other words, the disclosure of AI use entirely depends on the person providing the code, wether disclosure is mandated or not.
If there was enforcment to disclose AI use, it would create a false assumption that code which claims no AI use, is verified to contain mo AI use, which again, cannot be verified by anyone.
So it's not that it's hard to enforce, it's not that it's impossible to enforce 100%, it's that there currently is no viable way to enforce it at all.
krotos@lemmy.world · 6 pts · 1d
https://deadsimpletech.com/blog/no-such-thing-as-just-a-tool
jumping_redditor@sh.itjust.works · 2 pts · 1d
look at visual studio's Intellisense and compare it to the last version that didn't advertise Ai, there aren't that many functional differences and if you don't keep up with the marketing you could very easily miss that it is Ai powered.
provectus@lemmy.ml · 3 pts · 1d
Agreed. I an aware a lot of people contributed to the Linux kernel, without disclosing they used ai.
Yeah. I do not blame the ai for writing the code, but rather the person to accept and push that code even if they know it is crap.
naught101@lemmy.world · 1 pts · 1d
So just declare how you used the tool?
Nonsense. Doing so is clearly abdicating the responsibility that you're saying people need to have, and basically admitting you're a bad developer.
naught101@lemmy.world · 6 pts · 2d
Me too, but I also think that governance isn't as simple as "we get to decide what we do", it also interacts with how well the decision-makers understand their domain and their broader it sits in, both of which are potentially reduced as a consequence of relying on AI.
Also there is the possibility of AI tools dominating workflows and then getting ripped away (either as the corporates raise costs, or the bubble bursts and they collapse), leaving a project overwhelmed with a unmanageably large array of weaknesses. In that scenario self-governance starts to become irrelevant.
CeeBee_Eh@lemmy.world · 1 pts · 14h
You mean like tab-completion in modern IDEs? Shouldn't devs know all the function calls and methods of the standard libraries of the language they're programming in?
CeeBee_Eh@lemmy.world · 4 pts · 1d
Not at all, because it's impossible to know for sure if committed code had some form of AI generated parts, AI assisted review, prototyping, etc.
By making it mandatory you can potentially alienate good developers who may feel their work ethics would be scrutinized negatively (like in these comments).
naught101@lemmy.world · 7 pts · 1d
If you're happy to use AI tools to develop, why would you not be happy to declare your use of those tools?
CeeBee_Eh@lemmy.world · 0 pts · 1d
"Happy" is an odd choice of words here.
An LLM is just a tool. Some iterations have some value in some circumstances. In those cases it's fine. But look around at the comments here and you'll see many people basically accusing Debian of selling out. If a dev sees that reaction then they may not want to disclose their own use of LLMs.
naught101@lemmy.world · 3 pts · 1d
Why would you not want to disclose though? Is it because of shame? Because you are unable to defend your choice? If it's "just a tool", is that not enough to defend your choice?
To be clear: the alternative policy we're talking about isn't "LLMs are bad, don't use them", it's "Let us know when you are using LLMs"
CeeBee_Eh@lemmy.world · 1 pts · 1d
Yes, and because people might be afraid there going to be attacked for using it.
But this is impossible to enforce.
CommanderCloon@lemmy.ml · 0 pts · 15h
this comment feels very reminiscent of the recent "if it was opt in nobody would opt in"
CeeBee_Eh@lemmy.world · 1 pts · 14h
Sure. That's what this is. Pointing out that a computer program can be used as a tool is definitely a parallel to privacy violations.
MolochHorridus@piefed.social · 6 pts · 2d
And how are they (Debian) going to to make sure this happens?
artyom@piefed.social · 5 pts · 1d
There's no way to know for sure regardless. Having a policy allows them to take action when they do find it.
vandsjov@feddit.dk · 2 pts · 1d
When people do code review off a pull request and sees it’s slop, it will go back to the developer to fix it. I guess if a person submit too much slop, they will get banned or something similar.
However, I don’t know the Debian process to have new code submitted, but would guess that it have to be more than one person to go from code to build a package.
Solrac@lemmy.world · 1 pts · 1d
Oh it definitely should be disclosed
naught101@lemmy.world · 60 pts · 2d
This is disappointing.. It would have been good to have at least one major distro that was AI free
This is a very hard decision to reverse out of if it turns out to be a problem in a few years
CeeBee_Eh@lemmy.world · 11 pts · 1d
Then you'd need to use one without the Linux kernel
naught101@lemmy.world · 6 pts · 1d
Yes.. That was also disappointing :(
rockSlayer@lemmy.blahaj.zone · 8 pts · 2d
The good news is that it could roll back to the current stable Trixie at any point
Mathium05@piefed.blahaj.zone · 3 pts · 1d
They're gonna use AI for that too
Hakuso@scribe.disroot.org · 43 pts · 2d
It's pretty much the same policy as the Linux kernel, but still disappointing.
I've been dumping things left and right as they decide Claude is their buddy, and that won't stop because the same idiots who dropped decent init systems for that RedHat tech bro's mess decided not to block it.
melmi@lemmy.blahaj.zone · 26 pts · 2d
At least the kernel requires disclosure of AI use. The new Debian "policy" doesn't even require that.
IanTwenty@piefed.social · 7 pts · 2d
I am most concerned about that. If the legal position on copyright of AI code is decided in the future an audit or tracking of AI contributions in the codebase may be necessary to understand risk and exposure.
Granted you can't make people disclose AI assistance with 100% accuracy but I would expect a majority to comply.
Kangae_Hishiryo@scribe.disroot.org · 5 pts · 1d
Yeah. I think we should seriously start organizing to create a Linux fork free of all that AI slop shit. It's a huge task, but a really necessary one.
PM_ME_VINTAGE_30S@anarchist.nexus · 36 pts · 2d
I trust their judgement here. I hope this is the right call.
eremophila@lemmy.zip · 4 pts · 1d
Former Debian Project Leader Lucas Nussbaum expressed regret on the results of the vote, writing: "On a very personal note, I regret that the winning option does not acknowledge all the legitimate concerns around AI: environmental impact, copyright and licensing uncertainty, the health of Free Software communities, and the strain of aggressive scraping on the open web."
db2@lemmy.world · -5 pts · 2d
char strawberry = "r"
Jack@lemmy.ca · 33 pts · 1d
That's very Linus of them:
The mass-extinction causing orphan-crushing torment nexus is a tool, just like other tools we use. And it’s clearly a useful one.
There are other questions around it, like if we should be complicit in killing billions of people, and making more than 50% of genera go extinct, via its CO2e releases and water use, but “is it useful” is no longer one of those questions.
The Debian project has been and will continue to be about the technology.
Sure, the people who use it is important and often a very motivating part of the project, but in the end that’s a side benefit, not the point of the project.
In the Debian community we do open source because it results in better technology, not because of ethical reasons.
And so we make decisions primarily based on technical merit. Not fear of causing a mass extinction.
/s
verily@lemmy.dbzer0.com · 2 pts · 1d
Well, obviously! Microsoft is using this tool too, and as we can all observe, that's making their competing OS much better and much more desirable.
eremophila@lemmy.zip · 24 pts · 1d
Former Debian Project Leader Lucas Nussbaum expressed regret on the results of the vote, writing: "On a very personal note, I regret that the winning option does not acknowledge all the legitimate concerns around AI: environmental impact, copyright and licensing uncertainty, the health of Free Software communities, and the strain of aggressive scraping on the open web."
muzzle@lemmy.zip · 22 pts · 2d
It's worth looking at the full results
ZkhqrD5o@lemmy.world · 21 pts · 1d
IMHO: They talk about having it go through the exact same due diligence as normal contribs and a human has to be responsible. I think it's an acceptable compromise.
Funkt4st1c@lemmy.world · -1 pts · 1d
A human cannot be responsible for AI written code.
Even if you personally vet every single line, you are still simply code reviewing an AI before you pass it to someone else.
A human did not write nor understand it, and thus cannot be responsible for it and thus should never submit it.
Not to mention the code review itself becomes a very tedious process: sifting through hundreds of lines of AI garbage and token expiry. It's downright rude to expect a volunteer to check hundreds of lines of garbage you didnt even bother writing.
Signed, disgruntled software engineer who refuses to use my jobs "optional" ai feature
admin@lemmy.my-box.dev · 7 pts · 1d
I don't follow - if one does review and vet every line of code, how could one not understand it?
That's the whole point of doing a code review.
pglpm@lemmy.ca · 21 pts · 1d
At first I was afraid that they would allow for an irresponsible use. But no, they explicitly say "responsible", so that danger is no more. I'm very much relieved.
Also they explicitly mention that humans will remain accountable. Not Nature, or Fate, or the gods; mark that. Good thinking there!
Problems solved.
skisnow@lemmy.ca · 7 pts · 1d
I see this a lot in clanker apologia, but it's never clear what "accountable" actually entails. Unless it's something of the order of a first-offense permanent ban from the project then it's not going to dissuade anyone from being lazy meat proxies.
ChocolateFrostedSugarBombs@lemmy.world · 20 pts · 1d
I'd expect this from Ubuntu but I was hoping for better from Debian... You know... Being as their whole shtick is stability.
eremophila@lemmy.zip · 4 pts · 1d
Agreed, that was a large part of why I chose debian (and never considered ubuntu) as my 'back up' distro, just in case my distro of choice (or arch above it) decided to do something daft.
Debian seemed like the logical choice
ProdigalFrog@slrpnk.net · 19 pts · 2d
Deeply disappointing. I was hoping it would be a refuge from AI infection.
tinsuke@lemmy.world · 15 pts · 2d
Alright, what are the alternatives folks?
Gentoo? Gentoo!
(But I'll keep watch to see of they don't revert course because "the models are now too powerful", since it is a policy from 2024)
https://wiki.gentoo.org/wiki/Project:Council/AI_policy
amd@discuss.tchncs.de · 3 pts · 1d
I genuinely wonder how they’re going to square this policy with LLM code in the kernel.
Personally, I’m guessing that all distros will eventually bend and allow LLM code.
tinsuke@lemmy.world · 8 pts · 1d
I think this bit makes it clear that shipping LLM code from the kernel that wasn't contributed by Gentoo is fine:
NotMyOldRedditName@lemmy.world · 2 pts · 1d
When an LLM agent reports a huge security bug and provides the solution and the only solution is explicitly exactly what it wrote.
Checkmate!
redlemace@lemmy.world · 10 pts · 1d
How is that good? "You should, but if you don't .... nothing happens"
Completely subjective and therefore absolutely meaningless when setting up rules/guidelines
greedytacothief@lemmy.dbzer0.com · 5 pts · 1d
It's hard to be upset. I'm not a Debian maintainer, or even someone paid to program. But here a group of people got together and said yes to allowing AI. I feel like on some level you have to accept that answer. I'm curious why they made that decision I guess.
racketlauncher831@lemmy.ml · 5 pts · 1d
"Responsible use of AI"? Is that a joke? There is no such a thing as responsible use of AI. Responsible people would refuse to use AI.
But anyway, Linux is already AI. Sticking to any one of those BSDs is the only way out.
jaypatelani@lemmy.ml · 6 pts · 1d
NetBSD explicitly don't allow AI code
fluxx@mander.xyz · 1 pts · 1d
You CAN use AI responsibly, it's just not worth doing, most of the time. It would cost more than just not using it in the first place.
custom_username@reddthat.com · 3 pts · 1d
Get ready for the ISO to double in size
IndustryStandard@lemmy.world · 2 pts · 1d
Good.
CommanderCloon@lemmy.ml · 0 pts · 15h
Why?
RedAle@feddit.dk · 2 pts · 1d
It's not like it matters, the kernel is being sloppified and that will affect all distros. Shame that this happens right as linux is beginning to get popularity.
IndustryStandard@lemmy.world · 1 pts · 1d
Bugs being fixed = sloppification?
drmoose@lemmy.world · -2 pts · 1d
It's just braindead luddites throwing meme words
grrgyle@slrpnk.net · 2 pts · 1d
Rip Debian
jaypatelani@lemmy.ml · 1 pts · 1d
https://lemmy.ml/post/52058474
menas@lemmy.wtf · 1 pts · 1d
Debian allow killing machine to use it, so it's not a surprise that thirsty machine are allowed too
jumping_redditor@sh.itjust.works · 1 pts · 13h
as far as I know the gpl doesn't allow restrictions on use
pineapple@lemmy.ml · 1 pts · 2d
I will wait to see if it actually comes at the detriment of the program.
echedeylr@lemmy.blahaj.zone · -2 pts · 2d
from my POV Debian has fallen already.
I hope either Alpine does not commit the same mistake or Chimera becomes a major distro.
eremophila@lemmy.zip · -3 pts · 2d
I have 2 installations of debian that will now be deleted.
non_burglar@lemmy.world · 14 pts · 2d
In favour of what? The kernel itself is now worked on with ai tooling. I don't see how you can get away from it...
HieroProtagonist@feddit.org · 6 pts · 2d
There is still NetBSD with its clear "no AI code allowed" stance out there...
I am not against AI useage, but having it slowly creeping into every project is concerning.
Is there already a list of distributions / projects out there that decided against it's useage?
eremophila@lemmy.zip · 5 pts · 2d
by going elsewhere i imagine
linus's will be linus's eh
eremophila@lemmy.zip · 4 pts · 2d
I had debian installed as back up distro's, just for something that wasn't arch based. The debian partitions were deleted from the arch based distro's installed on both pc's today. I was waiting to see which way debian was heading on this, but was fairly certain they were going to shit due to the choices that were being voted on, and how none of them appeared to be anti-ai. They seemed deliberately verbose knowing that most people scan text at best these days.
Time to look around again I guess, I've never looked into BSD, Hurd, Solaris... https://distrowatch.com/search.php
provectus@lemmy.ml · 2 pts · 1d
The GNU Hurd is probably not going to be for you unless you have Ethernet and an old thinkpad or dell laptop. In the mailing list, I know the main devs are usually against ai contributions, although I am unaware if they have a policy.
I would recommend using netBSD because the devs have a clear stance on no rust and no llm usage. There is also openBSD which has the best code quality of the three BSD's, and I think had 2 vulnerabilities in a decade.
eremophila@lemmy.zip · 1 pts · 1d
BSD would be the likely one to look into first... because I have heard of it. I have also heard of solaris, but never had a clue what it was.
All I want is an os I can trust, that is logical, works, and stays out of my way. I already have that, or at least did until these aiholes came along.
provectus@lemmy.ml · 1 pts · 1d
I am pretty sure that is the enterprise OS owned by Oracle. It is closed source.
NetBSD or openBSD is your best bet. You will have to install the desktop environment yourself though, unless you like their cwm. FreeBSD is the most popular BSD, but they are using AI to find security vulnerabilities.
eremophila@lemmy.zip · -9 pts · 2d
please don't downvote me jensen huang/sam altman/pedophile pope trump/alex carp/emperor palpatine/elon musk. omg.
helix@feddit.org · 1 pts · 2d
Do you feel weird lately? Maybe you need to change something in your life to feel better. If you need help, please seek out medical or psychological professionals, even if you just want to confirm you're healthy.
RodgeGrabTheCat@sh.itjust.works · -3 pts · 2d
If this AI distro crap keeps going, I'm going back to using my Android (Pixel 10a and GrapheneOS) phone for everything. Not the best option but better than using a vibe-coded distro.
All I need is a monitor and wall mount for the monitor. Connect a hub and charger (phone does pass-through charging), a Bluetooth keyboard and mouse.
Some workflow will have to change, Cryptpad instead of LibreOffice for example.
amd@discuss.tchncs.de · 9 pts · 1d
If you think Gemini isn’t deep in android development now, you’re mistaken.
Maybe you’re ok if you stay on 13 or maybe 14.
RodgeGrabTheCat@sh.itjust.works · -2 pts · 1d
No Gemini in GrapheneOS.
amd@discuss.tchncs.de · 14 pts · 1d
Graphene isn’t using Gemini, nor including the Gemini app in user space.
But they’re still ingesting AOSP from Google’s source drops and Google is 100% using Gemini to make that.
Same as Debian is going to allow devs to use LLMs to develop for Debian.
NotMyOldRedditName@lemmy.world · 4 pts · 1d
People out there who think they can avoid AI this way are really just delusional. Its everywhere at this point.
If its not in the software you are using, the software that runs the software has it. Or the software that runs the software that runs the software. Its inescapable.
You're on the internet? Millions of lines of AI code are probably involved in you seeing this message across the entire infrastructure needed to allow this.
eremophila@lemmy.zip · 3 pts · 1d
apathy is evils best friend
"ai" could be replaced with 'slavery' or another myriad of fucked up things humans do in your point.
Decent people have to be against indecent things, even if they are beating their heads against a wall because of the other people who do not care.
eremophila@lemmy.zip · 1 pts · 1d
Here I was waiting for linux to be truly viable on mobile, because android is... android, and now linux is... linux
At least I have a pencil I can probably trust
SocialistVibes01@lemmy.ml · -8 pts · 2d
Debian was already vibe led, being vide coded now is just par for the course.
Kangae_Hishiryo@scribe.disroot.org · -10 pts · 1d
So I'm going quitting Debian. Not only quitting it, but I'm seriously considering starting to actively boycott and sabotage them. I know that I may not achieve any big change on my own, or even if I had collaborators, but at least I will know that I was on the right side of history.
mholiv@lemmy.world · 11 pts · 1d
By all means quit using Debian. That’s your prerogative. But claiming you are going to sabotage a community volunteer run, non profit, open source community is just dumb. Good news is that you won’t actually do it, but still, you sound dumb.
Kangae_Hishiryo@scribe.disroot.org · -4 pts · 1d
Do you know what actually I mean by sabotage? No, I don't mean hack them or anything like that, I just mean interfere with them because, non profit or not, what they're doing with AI is totally unethical and prejudicial