frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Muse – Meta’s personal AI agent

https://ai.meta.com/muse/
423•yks•10h ago•447 comments

Tension wood: A 'muscle' that can both bend and straighten plants

https://phys.org/news/2026-09-trees-muscle-posture-newly-role.html
80•mdp2021•5d ago•12 comments

Navier-Stokes – Tristan Buckmaster [pdf]

https://cims.nyu.edu/~tristanb/statement.pdf
1487•procedurecall•1d ago•636 comments

Researchers Spot Fake Ancient Pottery Using the Earth's Magnetic Field

https://www.smithsonianmag.com/smart-news/researchers-determine-how-to-spot-fake-ancient-pottery-...
16•cisc•3d ago•3 comments

How to build a printer

https://nishantjosh.dev/blogs/how-to-build-a-fking-printer/
235•cat-whisperer•8h ago•44 comments

AlphaGenome Atlas: a high-resolution map of human DNA

https://blog.google/innovation-and-ai/models-and-research/google-deepmind/alphagenome-atlas/
529•utiiiD•14h ago•118 comments

Large language models develop novel social biases through adaptive exploration

https://openreview.net/challenge?redirect=%2Fforum%3Fid%3Dpc7fqaOcAH
132•paimapi•7h ago•67 comments

Mercury 2.5

https://www.inceptionlabs.ai/blog/introducing-mercury-2-5
162•Topfi•9h ago•24 comments

The origins of Partner’s computer case

https://www.racunalniski-muzej.si/en/the-origins-of-partners-computer-case/
21•markostamcar•1d ago•2 comments

A Biography of Lee Holloway, the Architect of Cloudflare's Technology (Part 1)

https://note.com/masakazu_urabe/n/n7815f5b64fab?hl=en
11•porridgeraisin•59m ago•2 comments

DaVinci Resolve 21.1

https://www.blackmagicdesign.com/media/release/20260908-03
381•tosh•16h ago•168 comments

An Accidental Blackboard

https://martinfowler.com/articles/exploring-gen-ai/an-accidental-blackboard.html
41•saikatsg•3d ago•18 comments

Tao: Open math problems being non-renewably mined by AI

https://mathstodon.xyz/@tao/117237320796901560
281•_alternator_•8h ago•296 comments

I resigned from Anthropic today

https://twitter.com/hilbertspaess/status/2097476196791709843#m
301•yurivish•5h ago•360 comments

On the Navier–Stokes Millennium Prize Problem

https://openai.com/index/navier-stokes-solution/
1208•tedsanders•12h ago•960 comments

27.5KB language-agnostic WebGPU syntax highlighter

https://gpu-lexer.vercel.app/
42•bpierre•4h ago•15 comments

I-have-ADHD: A skill to stop coding agents from burying the answer

https://github.com/ayghri/i-have-adhd
381•domhudson•15h ago•281 comments

Into the depths of C: Elaborating the de facto standards (2016)

https://dl.acm.org/doi/10.1145/2980983.2908081
8•rramadass•13h ago•1 comments

Benchmarking Qwen3.8 27B quantizations: 4-bit holds up, 1-bit collapses

https://quesma.com/blog/qwen38-27b-quantizations-benchmarked/
229•stared•14h ago•111 comments

A Topological Picture Book, Rendered

https://e-infinity.space/picture-book/
82•mathgenius•7h ago•10 comments

The Microeconomics of Artificial Intelligence (2025)

https://direct.mit.edu/books/oa-monograph/6067/The-Microeconomics-of-Artificial-Intelligence
43•neehao•2d ago•20 comments

Getting phpBB 1.4.4 working in Docker

https://www.thran.uk/writ/devlog/2026/09/phpbb-144-in-docker.html
38•HeckFeck•1d ago•25 comments

ChatGPT Images 2.5

https://openai.com/index/introducing-chatgpt-images-2-5/
304•vertigoruntime•11h ago•379 comments

We built our house for LAN parties (2024)

https://lanparty.house/
472•fittingopposite•3d ago•321 comments

Replacing a Rust Enum with a 64-Bit Word Made My Interpreter 17% Faster

https://pointersgonewild.com/2026-08-25-replacing-a-rust-enum-with-a-64-bit-word/
113•metrofun•3d ago•44 comments

Kimi K3 (2.8T) at 1 token/s on a MacBook Pro, streamed from four SSDs

https://github.com/argonautlabsai/deltafin
243•Argonautlabs•9h ago•123 comments

The Helicopter with Radioactive Blades

https://hackaday.com/2026/09/07/the-helicopter-with-radioactive-blades/
167•zdw•1d ago•52 comments

Animation in Bevy: The Big Picture

https://glocq.com/en/blog/20260827/
60•ibobev•9h ago•5 comments

Ask HN: 3.5 inch diskette read errors, would a period correct drive do better?

26•rietta•1d ago•25 comments

Implementation of GCC's Nested Functions (vs. C++ Lambdas)

https://uecker.codeberg.page/2026-09-05.html
68•uecker•3d ago•11 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•1y ago

Comments

balloob•1y ago
Founder Home Assistant here. Want to chime in that I always love to see write ups like these to see the great things what people achieve with Home Assistant.

Not everyone might know, but last year we started the Open Home Foundation[1] as a non-profit in Switzerland and I donated Home Assistant to it[2]. It's fully funded by users. There are no investors involved.

We are fully committed to building out a smart home that focuses on local control and privacy. Yes there are rough edges, but we're actively working on it in the open, with progress being released every month.

~Paulus Founder Home Assistant & President Open Home Foundation https://github.com/balloob

[1]: https://www.openhomefoundation.org [2]: https://www.openhomefoundation.org/blog/announcing-the-open-...

pabs3•1y ago
Discussion for the other article in the series:

https://news.ycombinator.com/item?id=44011381

tomhow•1y ago
Comments moved thither. Thanks!
pabs3•1y ago
They are two different articles, I don't think that was correct.
tomhow•1y ago
The problem is we can’t have two closely-related threads (i.e., threads where there is significant subject/discussion overlap) active at once.

When that happens it just gets confusing, because it’s hard for people know which thread to comment in, if the comment they want to make is somewhere in the overlap. And then whichever one they choose to comment in, people who only see the other thread won’t see that comment. Then sometimes, anticipating this, people will copy and paste their comment in both threads (which happened in this case). But then each one gets different replies.

So each thread ends up being incomplete and duplicated all at once, and it all becomes a big confusing mess.

The fact that these two articles were by the same author, had the same title, were published just a week apart and could easily have been published as one, longer article, says to me that merging the threads was the right thing to do.

The other option would have been to bury the second thread and consider another thread about that second article a few months later, but that didn’t seem like the best option, given how much the two articles are so related and continuous.

Edit: Just thought I'd add that a major factor in deciding to merge the threads was this opening to the second part by the author:

The first article in this series provided an overview of Home Assistant, its community, and its capabilities. It was deliberately short on descriptions of interesting things that can be done with Home Assistant, though — the reasons why one might actually want to use this program. In this closing article, we'll look at how Home Assistant was used to solve some real problems.

To me it makes all the difference that the first part is introductory/high-level whilst the second part goes deeper into usage-scenarios. We'd treat it differently if each part went deeply into different aspects on the project.

pabs3•1y ago
Thanks for the response, guess that makes sense.
pabs3•1y ago
BTW, on lobste.rs, they can merge threads into one, and all the URLs are shown at the top. That might be a useful change to adopt for HN too?