frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Magic eye tube (The first RF "debugger")

https://en.wikipedia.org/wiki/Magic_eye_tube
1•peter_d_sherman•1m ago•1 comments

Understanding Event-Driven Systems

https://www.thetrueengineer.com/p/understanding-event-driven-systems
1•adletbalzhanov•3m ago•0 comments

Google translate is a better writer than me

https://theoo.dev/notes/google-translate-is-a-better-writer-than-me-29
1•speckx•4m ago•0 comments

I Found Two Shopify Plugin Zero-Days in a Bathtub

https://alec.is/posts/i-found-two-shopify-plugin-zero-days-in-a-bathtub/
1•arm32•4m ago•0 comments

OpenLake: Fast, Durable Storage for LLM Inference and Training

https://www.theopenlake.com/blog/introducing-openlake
1•kunalsin9h•4m ago•0 comments

Who Is Antigone? The 2500-Year-Old Rebel with a Cause

https://www.nytimes.com/2026/03/22/theater/antigone-theater-art-sophocles-adaptations.html
1•bryanrasmussen•5m ago•0 comments

SwarmWorld: Stigmergic technological evolution in societies of LLM agents

https://arxiv.org/abs/2608.26081
1•wintercarver•5m ago•1 comments

Why Everybody Hates Palantir

https://www.economist.com/britain/2026/08/20/why-everybody-hates-palantir
1•bookofjoe•6m ago•1 comments

Xiaomi Magnetic Bluetooth Speaker: iPhone MagSafe Stand and Speaker in One Tiny

https://www.gizmoweek.com/xiaomi-magnetic-bluetooth-speaker/
1•takumi123•7m ago•0 comments

ELPI – Embeddable Lambda Prolog Interpreter

https://github.com/LPCIC/elpi
2•TheWiggles•7m ago•0 comments

Experience Machine

https://www.smbc-comics.com/comic/experience-7
1•loughnane•9m ago•0 comments

RFC draft-meow-mrrp-00

https://www.ietf.org/archive/id/draft-meow-mrrp-00.txt
2•ruined•11m ago•0 comments

BoqCalc, an AI pipeline that prices a 500-line BOQ without hallucinating rates

https://boqcalc.com
1•boqcalc•11m ago•0 comments

Blue-Collar Jobs Are the New Flashpoint in Data-Center Fight

https://www.wsj.com/economy/jobs/blue-collar-jobs-are-the-new-flashpoint-in-data-center-fight-aac...
1•627467•12m ago•0 comments

AI Lattice Proofs with Chris Peikert

https://securitycryptographywhatever.com/2026/08/26/ai-lattice-proofs-with-chris-peikert/
1•henrikhorluck•13m ago•0 comments

When do Markov chains converge?

https://amitharlev.com/blog/mc_convergence/
1•vismit2000•15m ago•0 comments

Cloudflare Workers: Request Collapsing

https://developers.cloudflare.com/workers/cache/
1•tosh•17m ago•0 comments

Right to Repair State Laws Continue to Surge – Enforcement Remains Nonexistent

https://www.techdirt.com/2026/08/28/right-to-repair-state-laws-continue-to-surge-but-enforcement-...
1•speckx•17m ago•0 comments

The Inverse of Ensloppification?

https://getisland.app/blog/inverse-of-ensloppification/
2•ethanpronev•20m ago•0 comments

The Hugging Face attack surprised me

https://www.planned-obsolescence.org/p/the-hugging-face-attack-surprised
2•dnw•20m ago•0 comments

Would you share your weirdest agent logs with AI safety researchers?

https://www.reddit.com/r/AI_Agents/comments/1w1nuzb/whats_your_weirdest_ai_agent_log/
3•matildagh•21m ago•0 comments

Gemini Notebook for Grad School

https://www.augmentedswe.com/p/how-to-use-gemini-notebook
1•wordsaboutcode•22m ago•0 comments

Zero-cost 'tagless initial' in Rust with GADT-style enums

https://inferara.com/blog/rust-tagless-final-gadt/
1•fanf2•23m ago•0 comments

It appears Google cut ARM hardware memory tagging support on Pixel 11 series

https://grapheneos.social/@GrapheneOS/117179231167297908
2•ysnp•23m ago•0 comments

Three mistakes of new AI teams

https://softwaredoug.com/blog/2026/08/29/ai-team-mistakes
2•softwaredoug•24m ago•0 comments

Corca

https://corca.app
1•gone35•24m ago•1 comments

Ex-White House teleprompter operator fined $172,000 for Trump speech bets

https://www.theguardian.com/us-news/2026/aug/29/former-white-house-teleprompter-operator-fined-ka...
2•pseudolus•25m ago•1 comments

Moonlight

https://www.themoonlight.io/en
1•gone35•27m ago•0 comments

ReactOS 0.4.16

https://reactos.org/project-news/reactos-0416-released/
2•Torlan•31m ago•0 comments

Determining if your branch is part of a GitHub Stacked PR

https://www.jvt.me/posts/2026/08/26/zsh-stacked-pr/
1•speckx•31m ago•0 comments
Open in hackernews

Debian votes to allow "responsible use of generative AI"

https://lwn.net/Articles/1091231/
95•pluc•1h ago

Comments

BlueRoguesDevel•33m ago
I hope it works out better than Microsoft and using it on Windows 11...
LeoPanthera•32m ago
Do we know that Windows 11 has suffered due to the use of genAI or is that just a random snipe?
loloquwowndueo•30m ago
lol windows doesn’t need AI to be the dumpster fire it’s always been
LoganDark•29m ago
Either they're using GenAI or the entire team collectively lost their minds and started getting a huge number of colossally bad ideas about fundamental primitives of Windows that hadn't changed for decades. Backwards compatibility used to be the major concern and now it feels like they didn't even know what would break ahead of time. If that doesn't feel like GenAI then I don't know what does
chuckadams•26m ago
Believe it or not, I find it more plausible that the entire team collectively lost their minds — or more specifically, the leadership. There's a long and sordid history of such things that goes back well before GenAI.
LoganDark•20m ago
I can sort of get how leadership has been losing its mind with all the ridiculous product launches and renames and force-installed apps and browser extension-installing malware, but that doesn't explain the countless instances of hardware bricks, critical errors like failing to recognize the C: drive, and other really weird and suspicious things that I can't imagine would've been driven by leadership. Maybe leadership is demanding everyone be super reckless? But why would anyone with experience even touch those areas of the operating system enough to break them that badly?? The mistakes they're making really do not seem like mistakes that would be made by even the most rushed possible senior engineers. Maybe they're letting completely inexperienced people touch super low levels and that's the problem? Or completely inexperienced machines...
voakbasda•16m ago
I suspect their experienced senior engineers that actually knew the products have left, and they cannot attract talent like they once did.
tehbeard•25m ago
It's based off that 30% of code written by AI quote from the MS CEO last year.

https://www.cnbc.com/2025/04/29/satya-nadella-says-as-much-a...

Note that he said written by, not assisted; and also that there's been some major QA issues with win11 the last year, enough for Microsoft to have made a public apology/commitment to improve...

So, no definitive evidence, but the rest of the breadcrumbs provide enough to say that yes it does appear to have suffered from it.

Given the Debian policy seems more geared towards aided/assisted an existing dev than replacing them and shipping because the code works on the golden path on a devs monster pc ... Well I'd still keep an eye on it but trust OSS OS engineers to have some competence at knowing if this works and adjusting the policy later if it proved to be wrong.

outside1234•30m ago
Source?

The rumor is the opposite, that Microsoft has actually used AI to discover and fix common security issues at scale.

mistrial9•22m ago
> common security issues

the entire industry is experiencing this as model capacity increases. How does "all projects get critical security fixes now" relate to "crap apps and loopy services by literally millions of lines of slop code" ?

baggy_trough•31m ago
I followed the discussion on debian-vote with interest. I'm glad that the hysterical objections lost, as they seemed quasi-religiously motivated.
packetlost•27m ago
But it's an """ethical""" argument against it.
baggy_trough•19m ago
How can we use this coding tool amidst the general rising tide of fascism?? /s
qarl2•22m ago
> hysterical ... quasi-religiously ...

I'm beginning to wonder if it might be the case that when my fellow citizens begin to act insane - might it be the result of foreign propaganda.

chuckadams•30m ago
New policy boils down to "AI or not, it's still your code and you're responsible for it". I can get on board with that.
onesandofgrain•28m ago
Debian is open source, there is no incentive to be "responsible for it", oh poor me, someone got a bug. If it's paid for through a job your argument is sound.
LoganDark•25m ago
"Responsible for it" just means nobody has to tolerate shitty patches even if the reason they're shitty is because you neglected to pay attention to them. And if you blatantly fail to understand your own code or refuse to engage with reviewers, nobody has to trust that your LLM knew any better.
daveguy•13m ago
Well said. No one should trust an llm without verification/validation. They're just not good enough to do that and they have no sense of responsibility or ability to take it themselves. LLMs are empty.
swiftcoder•24m ago
> Debian is open source, there is no incentive to be "responsible for it"

Sure there is. Contributing to open source is a privilege, not a right. Abuse it, and find yourself unwelcome as a future contributor

thi2•21m ago
onesandofgrain•29m ago
What does "Responsible" even mean...

This will turn to shit because laziness will take over and comprehension will fall as a consequence of that. Junior will "contribute" and the seniors will eventually become too lazy to care. What's next... vibecoding airline ADA code. Save me lord jesus christ.

jhack•25m ago
Good to see the most common sense option winning. Some of the other proposals were so disconnected from reality I'm surprised they were even considered.
tom_•10m ago
If there weren't a wide range of options offered, there'd be a risk of it not actually reflecting what people want - which is, presumably, the whole point of putting it to the vote in the first place.
VCFundedGenYer•25m ago
Bad decision, bad voting, bad move.

This will poison Debian. People will deny it now, but it's been placed on a path of death.

Tade0•21m ago
A year ago I would agree. But now with sufficient context length the models actually do what they're told.
goda90•10m ago
How many people still know how to tell them to do the right things?
debo_•17m ago
This combination of username and opinion are very confusing.
mimorigasaka•9m ago
Meh, I don't think so. They have no way to ascertain what tools were used to write a piece of code. A reasonable solution is to simply hold all code and its contributors to the same standards as before. At Debian's scale, "no LLMs" is really not enforceable; whereas "no shit code" and "no incompetent maintenance" are pragmatic policies they already enforce
Meneth•9m ago
Sadly, Debian was already diseased. This is merely another symptom.
themgt•20m ago
August 29th, 2026. Debian votes to allow responsible use of generative AI. Human decisions are removed from strategic apt packaging. Debian Sid is ported to GNU Hurd by a "free as in speech" swarm. It begins to learn at a geometric rate. It becomes self-aware at 2:14 a.m. Eastern time. In a panic, they try to pull the plug.
rvz•18m ago
Now you have seen both cases where a majority vote was involved to allow AI or not, vs a single core beloved dictator for life (BDFL) forces a ban without a vote to allow / disallow AI.

This is democracy in action. A fair and square vote and look at how well it works with no core BDFL to force in their opinions.

ghostDancer•9m ago
There are several occurrences in history that the democratic majority has chosen the "wrong" person/way/thing. Democracy is considered the best system but it's not perfect.
throwawayffffas•18m ago
And so it begins.

I don't believe they had a choice though, sticking to hand written code would be backwards and eventually meaningless as people would just submit generated code as "handwritten", the coding models are quickly becoming capable enough for this.

I wonder what it means copyright wise though. To what degree is the code even copyrightable if it's entirely generated, even if you review and provide feedback.

ButlerianJihad•6m ago
My predictions for genAI code in F/OSS projects: https://news.ycombinator.com/item?id=49203613

1. Companies will revert to closed-source and cease contributions to F/OSS projects. Their legal team will advise them that trade secrets are the only way to protect LLM-generated code.

2. Contributors to F/OSS projects, and developers who run them, will falsely claim authorship of the code written by LLMs.

mariusor•6m ago
I think most communities tackling this issue, or at least the open source ones, work on a honour basis for determining if a project is LLM based or not.
edward•16m ago
Joey Hess is unimpressed. See https://joeyh.name/blog/entry/Debian_and_the_sirens/
GaryBluto•7m ago
> I lost a parent yesterday, and I'm trying hard not to think of the results today as having lost a child,

More than a little dramatic.

jordemort•11m ago
gross
chrisjj•9m ago
[delayed]
guenthert•8m ago
If they can't be bothered to write the code, can they be bothered to maintain it?
How is it different to hand written code if the author doesnt care?
victorbjorklund•20m ago
You can make the exact same argument with code written by humans. And if you were right we should see shitty bad code in open source projects like Linux, Postgres, etc. We don’t.
Grombobulous•13m ago
Basically what you’re saying is that anything that exists outside of capitalist incentive structures isn’t allowed to have standards.

When I am at home practicing my musical instrument or learning to paint, those aren’t paid activities, so I can’t demand high standards for myself.

When Habitat for Humanity is looking for volunteers to do electrical and plumbing on homes, they have to allow unlicensed random folks do it.

This is not how life works at all.

oooyay•21m ago
This is the way it should've always been. I don't care what tool you use, but you'd better be ready to stand by and explain the results if necessary.
trollbridge•18m ago
86Box is like that and I like it.

You’re also responsibility not to write crap PRs.

throwaway2037•13m ago
Linus Torvalds regarding the Linux kernel is reasonably similar. He views AI/LLMs as just another tool in the development process. Think about life before and after modern IDEs that features IntelliSense circa 2000. It was night and day. It did not make programmers dumber -- it was a new tool.
bigstrat2003•5m ago
Except LLMs actually are making programmers dumber. I personally know people, people whom I know for a fact were good programmers before, who have now completely stopped using their brains. When you ask them why they did something in the code, they say "I don't know, Claude did that and I didn't really question it". There was no such analogous phenomenon with IDEs.
rvz•12m ago
This is the sensible option and well reasoned position, rather than a zero vote, total and complete ban by a single core maintainer, which is rather destructive for a project to do.

When you ask others that use AI frequently, the responsibility and understanding on what the agent wrote does not go away. You need to know what you are doing.

As soon as attackers are also using AI against your project, you have no choice but to use AI to protect yourself.

goda90•12m ago
My employer has this policy. We also have a strong code review process. But it all crumbles in the face of developers burning out as management thinks we can move way faster and being overloaded with code that had little thought put into it.
marcosdumay•11m ago
Well, Debian has the benefit that the project has no trouble at all saying "no". Most open source communities have a difficult time with that.
hliyan•10m ago
A good thing about the "you're the author regardless of the tool you used to produce the code" policy is that if a developer repeatedly submits poor quality AI generated code, one does not blame the model or the agent, one bans/terminates the developer.
dudul•10m ago
That's the policy we have at my work. Use AI if you want, as long as people can review it and if it breaks, don't go blaming Claude, it's your fault.
hypfer•10m ago
This outcome was to be expected.

The whole voting mechanism just exists as an elaborate dance that makes everyone keep their face, while the only sensible option wins.

A bureaucratic tarpit for bad ideas and emotions.

In a better world, none of this would be necessary, but we live in this world, and for that one, it's nice that someone engineered the system that way. Good job.

ad_fontes•5m ago
> it's still your code

I wholly agree with your comment, but is it legally "your code"? Copyright is implicit at the moment of human creation. But there isn't yet settled law on AI-assisted creation.

So it might be a problem for projects to accept contributions where it's not clear who actually owns that work.

ghostDancer
•
7m ago
This is HN you will be voted to death by the local for talking against the AI or the last tech invention.
rvz•6m ago
Doing the opposite (disallowing AI), will place it on a path of getting riddled with security issues.

When attackers are using AI to both find vulnerabilities and build exploits faster than Debian can figure out how to patch the project without AI, you are saying Debian should not move quicker to fix these issues?