frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Cockpit is a web-based graphical interface for servers

https://github.com/cockpit-project/cockpit
89•modinfo•2h ago•49 comments

Astral to Join OpenAI

https://astral.sh/blog/openai
1128•ibraheemdev•9h ago•703 comments

Google details new 24-hour process to sideload unverified Android apps

https://arstechnica.com/gadgets/2026/03/google-details-new-24-hour-process-to-sideload-unverified...
365•0xedb•5h ago•382 comments

Return of the Obra Dinn: spherical mapped dithering for a 1bpp first-person game

https://forums.tigsource.com/index.php?topic=40832.msg1363742#msg1363742
186•PaulHoule•2d ago•25 comments

How the Turner twins are mythbusting modern technical apparel

https://www.carryology.com/insights/how-the-turner-twins-are-mythbusting-modern-gear/
57•greedo•2d ago•25 comments

Show HN: Three new Kitten TTS models – smallest less than 25MB

https://github.com/KittenML/KittenTTS
277•rohan_joshi•6h ago•86 comments

EsoLang-Bench: Evaluating Genuine Reasoning in LLMs via Esoteric Languages

https://esolang-bench.vercel.app/
30•matt_d•1h ago•10 comments

Be intentional about how AI changes your codebase

https://aicode.swerdlow.dev
25•benswerd•1h ago•13 comments

Noq: n0's new QUIC implementation in Rust

https://www.iroh.computer/blog/noq-announcement
117•od0•4h ago•14 comments

Waymo Safety Impact

https://waymo.com/safety/impact/
143•xnx•2h ago•112 comments

From Oscilloscope to Wireshark: A UDP Story (2022)

https://www.mattkeeter.com/blog/2022-08-11-udp/
56•ofrzeta•3h ago•10 comments

Clockwise acquired by Salesforce and shutting down next week

https://www.getclockwise.com
41•nigelgutzmann•2h ago•21 comments

NanoGPT Slowrun: 10x Data Efficiency with Infinite Compute

https://qlabs.sh/10x
71•sdpmas•3h ago•10 comments

4Chan mocks £520k fine for UK online safety breaches

https://www.bbc.com/news/articles/c624330lg1ko
209•mosura•8h ago•326 comments

Launch HN: Voltair (YC W26) – Drone and charging network for power utilities

41•wweissbluth•5h ago•22 comments

“Your frustration is the product”

https://daringfireball.net/2026/03/your_frustration_is_the_product
362•llm_nerd•11h ago•217 comments

Scaling Karpathy's Autoresearch: What Happens When the Agent Gets a GPU Cluster

https://blog.skypilot.co/scaling-autoresearch/
97•hopechong•5h ago•41 comments

OpenBSD: PF queues break the 4 Gbps barrier

https://undeadly.org/cgi?action=article;sid=20260319125859
170•defrost•9h ago•51 comments

Juggalo makeup blocks facial recognition technology (2019)

https://consequence.net/2019/07/juggalo-makeup-facial-recognition/
212•speckx•9h ago•133 comments

An update on Steam / GOG changes for OpenTTD

https://www.openttd.org/news/2026/03/19/steam-changes-update
240•jandeboevrie•5h ago•168 comments

Tesla: Failure of the FSD's degradation detection system [pdf]

https://static.nhtsa.gov/odi/inv/2026/INOA-EA26002-10023.pdf
131•doener•2h ago•58 comments

The Need for an Independent AI Grid

https://amppublic.com/
6•olalonde•1h ago•0 comments

The Shape of Inequalities

https://www.andreinc.net/2026/03/16/the-shape-of-inequalities/
85•nomemory•8h ago•14 comments

Xiaomi launches next-gen SU7 with 902 km range and Lidar, still undercuts Tesla

https://electrek.co/2026/03/19/xiaomi-launches-next-gen-su7-902-km-range-undercuts-tesla/
30•breve•1h ago•0 comments

macOS 26 breaks custom DNS settings including .internal

https://gist.github.com/adamamyl/81b78eced40feae50eae7c4f3bec1f5a
294•adamamyl•7h ago•142 comments

Connecticut and the 1 Kilometer Effect

https://alearningaday.blog/2026/03/19/connecticut-and-the-1-kilometer-effect/
32•speckx•4h ago•24 comments

Anthropic takes legal action against OpenCode

https://github.com/anomalyco/opencode/pull/18186
311•_squared_•3h ago•265 comments

Successes and Breakdowns in Everyday Non-Display Smart Glasses Use

https://arxiv.org/abs/2602.22340
19•PaulHoule•4d ago•1 comments

Afroman found not liable in defamation case

https://nypost.com/2026/03/18/us-news/afroman-found-not-liable-in-bizarre-ohio-defamation-case/
1057•antonymoose•12h ago•598 comments

Launch HN: Canary (YC W26) – AI QA that understands your code

25•Visweshyc•6h ago•13 comments
Open in hackernews

No AI in Node.js Core

https://github.com/indutny/no-ai-in-nodejs-core
31•porsager•3h ago

Comments

ramesh31•1h ago
This is a silly reactionary response. Where is the line? Can I use AI to look up APIs? Write documentation? What if I write a function and ask AI to test it? What if I manually implemented an idea that I thought about after chatting with AI a few weeks ago?

Stop treating this like it's going to go away. We need actual solutions for the FOSS community that make reviewing AI assisted work tractable.

ronsor•1h ago
Related: https://news.ycombinator.com/item?id=47413195

@indutny explains their views in that thread.

tylerchilds•1h ago
On the one hand, agreed

On the other hand, I haven’t and I believe many of us, have never paid node any money so it feels weird to dictate their approach.

cj•1h ago
I have no unique perspective to add other than an obvious question: If the PR is low quality, why not just close/reject it? Does it matter if it's AI assisted or not?
chjj•1h ago
That means all AI code would simply be rejected. This saves time.
spoiler•1h ago
If AI writes a for loop the same way you would... Does it automatically mean the code is bad because you—or someone you approve of—didn't write it? What is the actual argument being made here? All code has trade offs, does AI make a bad cost/benefit analysis? Hell yeah it does. Do humans make the same mistake? I can tell you for certain they do, because at least half of my career was spent fixing those mistakes... Before there ever was an LLM in sight. So again... What's the argument here? AI can produce more code, so like more possibility for fuck up? Well, don't vibe code with "approve everything" like what are we even talking about? It's not the tool it's the users, and as with any tool theres going to be misuse, especially new and emerging ones lol
chjj•1h ago
If this is your opinion, I ask you: are you okay with AI reviewing the PRs as well, or do you prefer a human to do it?

Think carefully before responding.

spoiler•16m ago
I don't know why you have to qualify your sentence with "think carefully before you respond" it makes it seem like you're setting up some rhetoric trap... But I'll assume it's in good faith? Anyway...

I don't mind if a review is AI-assisted. I've always been a fan of the whole "human in the loop" concept in general. Maybe the AI helps them catch something they'd normally miss or gloss over. Everyone tends to have different priorities when reviewing PRs, and it's not like humans don't have lapses in judgement either (I'm not trying to anthropomorphise AI, but you know what I mean).

My stance is same about writing code. I honestly don't mind if the code was written `ed` on a linux-powered toaster from 2005 with 32x32 screen, or if they wrote it using Claude Code 9000.

At the end of the day, the person who's submitting the code (or signing off a review) is responsible for their actions.

So in a round-about way, to answer your question: I think AI as part of the review is fine. As impressive as their output can be sometimes be, it can be both impressively good and impressively bad. So no, only relying on AI for review is not enough.

graphememes•1h ago
Honestly, this is a small pebble but feels like a ripple in the reasons why node.js is losing to bun and others.
cpursley•1h ago
If they allow AI in Node it just might do a full rewrite into Rust, Go or Elixir ;)
bwestergard•1h ago
This is how I would deal with the problem if I maintained node: "Please, use your tokens and experimental energies to port to Rust and pass the following test suite. Let us know when you've got something that works."
mtndew4brkfst•1h ago
Well, survivorship bias means that Elixir is loudly populated by AI maximalists now. Just go look at the last several years worth of US/EU Elixirconf talks schedules, it's maybe a third of each cohort and included in keynote slots.
pan69•1h ago
> A 19k lines-of-code Pull Request was opened in January, 2026.

Such a PR should be rejected simply because of the shear size of it, regardless of AI use. Seriously, who submits a 19k line PR? Just make many small ones.

tracker1•1h ago
How would you go about breaking up this particular set of functionality into smaller PRs, exactly? It's meant to introduce a virtualized file system... the size is dictated by the feature itself.

Also, no mention at all regarding the test coverage, or impact if any on existing code paths specifically.

spoiler•1h ago
The PR touched a lot of internals, including module code and mirrors the fs APIs. So, yes it was big, but the commit history was largely clean and followed a development story, and it was tested. The code quality was decent too. I didn't review all of it because I don't have a personal stake in this though.

I suggest EVERYONE in this thread go read the the GitHub PR in question. There's some good arguments for and against AI, and what it means for FOSS... But good lord you will have to sift through the virtue signalling bullshit and have patience for the constant moving of goalposts

vova_hn2•9m ago
I don't see, how such policies can possibly achieve more good, then harm.

A person, who posts slop for whatever reason, or runs bots that post slop, will simply ignore them.

An honest person, who cares about the quality of their contribution and genuinely wants to improve the project will be more limited in the choice of tools to do so.

So, this policy only serves to limit honest contributors, while doing absolutely nothing to stop spammers/slopposters.