frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Dav2d

https://code.videolan.org/videolan/dav2d
90•dabinat•1h ago•28 comments

NetHack 5.0.0

https://nethack.org/v500/release.html
188•rsaarelm•1h ago•29 comments

Inventions for battery reuse and recycling increase more than 7-fold in last 10y

https://www.epo.org/en/news-events/news/inventions-battery-reuse-and-recycling-increase-more-seve...
87•JeanKage•2d ago•4 comments

Unsigned Sizes: A Five Year Mistake

https://c3-lang.org/blog/unsigned-sizes-a-five-year-mistake/
14•lerno•43m ago•5 comments

Flue is a TypeScript framework for building the next generation of agents

https://flueframework.com/
26•momentmaker•1h ago•5 comments

California to begin ticketing driverless cars that violate traffic laws

https://www.bbc.com/news/articles/clypjx3rg2go
79•geox•1h ago•73 comments

Do_not_track

https://donottrack.sh/
21•RubyGuy•1h ago•10 comments

Barman – Backup and Recovery Manager for PostgreSQL

https://github.com/EnterpriseDB/barman
104•nateb2022•3d ago•19 comments

How fast is a macOS VM, and how small could it be?

https://eclecticlight.co/2026/05/02/how-fast-is-a-macos-vm-and-how-small-could-it-be/
194•moosia•9h ago•72 comments

Why does it take so long to release black fan versions?

https://www.noctua.at/en/expertise/blog/how-can-it-take-so-long-to-release-black-fan-versions
626•buildbot•14h ago•263 comments

Roblox shares plummet 18% as child safety measures weigh on bookings

https://www.cnbc.com/2026/05/01/roblox-rblx-stock-child-safety-earnings.html
75•1vuio0pswjnm7•2h ago•41 comments

Uber wants to turn its drivers into a sensor grid for self-driving companies

https://techcrunch.com/2026/05/01/uber-wants-to-turn-its-millions-of-drivers-into-a-sensor-grid-f...
85•nickvec•3h ago•104 comments

Refusal in Language Models Is Mediated by a Single Direction

https://arxiv.org/abs/2406.11717
61•fagnerbrack•6h ago•21 comments

Open Design: Use Your Coding Agent as a Design Engine

https://github.com/nexu-io/open-design
138•steveharing1•7h ago•77 comments

Why are there both TMP and TEMP environment variables? (2015)

https://devblogs.microsoft.com/oldnewthing/20150417-00/?p=44213
170•ankitg12•11h ago•80 comments

Why IPv6 is so complicated

https://github.com/becarpenter/book6/blob/main/01.%20Introduction%20and%20Foreword/Why%20IPv6%20i...
38•speckx•2d ago•81 comments

Dotcl: Common Lisp Implementation on .NET

https://github.com/dotcl/dotcl
133•reikonomusha•2d ago•28 comments

Ti-84 Evo

https://education.ti.com/en/products/calculators/graphing-calculators/ti-84-evo
552•thatxliner•23h ago•448 comments

America's Expanding Domestic Surveillance

https://www.wsj.com/articles/americas-expanding-domestic-surveillance-08b73187
127•Brajeshwar•4h ago•72 comments

Little Magazines Are Back

https://wsjfreeexpression.substack.com/p/little-magazines-are-back
4•prismatic•2d ago•0 comments

AI Self-preferencing in Algorithmic Hiring: Empirical Evidence and Insights

https://arxiv.org/abs/2509.00462
304•laurex•3h ago•156 comments

Show HN: Pollen – distributed WASM runtime, no control plane, single binary

https://github.com/sambigeara/pollen
82•sambigeara•2d ago•40 comments

Show HN: DAC – open-source dashboard as code tool for agents and humans

https://github.com/bruin-data/dac
82•karakanb•3d ago•24 comments

Zugzwang

https://en.wikipedia.org/wiki/Zugzwang
74•Qem•3h ago•43 comments

Also-RANS: Asymmetric Numeral Systems for Entropy Coding

https://fergusfinn.com/blog/understanding-rans/
8•mezark•2d ago•0 comments

Artemis II Photo Timeline

https://artemistimeline.com/#artemis-ii-walkout-nhq202604010003
319•geerlingguy•2d ago•26 comments

Canonical Under Attack

https://status.canonical.com
7•ta988•19m ago•1 comments

New research suggests people can communicate and practice skills while dreaming

https://www.newyorker.com/culture/annals-of-inquiry/its-possible-to-learn-in-our-sleep-should-we
426•XzetaU8•1d ago•247 comments

DeepSeek V4—almost on the frontier

https://simonwillison.net/2026/Apr/24/deepseek-v4/
416•indigodaddy•1d ago•263 comments

Welcome to Hell Developer

https://noahclements.com/Wahoo-Bolt-Hidden-Debug-Mode/
5•denysvitali•1h ago•1 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•11mo ago

Comments

balloob•11mo 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•11mo ago
Discussion for the other article in the series:

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

tomhow•11mo ago
Comments moved thither. Thanks!
pabs3•11mo ago
They are two different articles, I don't think that was correct.
tomhow•11mo 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•11mo ago
Thanks for the response, guess that makes sense.
pabs3•11mo 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?