frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Quality of drinking water varies significantly by airline

https://foodmedcenter.org/2026-center-for-food-as-medicine-longevity-airline-water-study/
85•azinman2•4h ago•51 comments

A faster heart for F-Droid

https://f-droid.org/2025/12/30/a-faster-heart-for-f-droid.html
308•kasabali•9h ago•129 comments

Animated AI

https://animatedai.github.io/
22•frozenseven•4d ago•4 comments

FediMeteo: A €4 FreeBSD VPS Became a Global Weather Service

https://it-notes.dragas.net/2025/02/26/fedimeteo-how-a-tiny-freebsd-vps-became-a-global-weather-s...
238•birdculture•8h ago•57 comments

Show HN: 22 GB of Hacker News in SQLite

https://hackerbook.dosaygo.com
378•keepamovin•11h ago•123 comments

Readings in Database Systems (5th Edition)

http://www.redbook.io/
14•teleforce•2h ago•1 comments

A Vulnerability in Libsodium

https://00f.net/2025/12/30/libsodium-vulnerability/
230•raggi•10h ago•28 comments

Zpdf: PDF text extraction in Zig – 5x faster than MuPDF

https://github.com/Lulzx/zpdf
140•lulzx•8h ago•49 comments

Honey's Dieselgate: Detecting and tricking testers

https://vptdigital.com/blog/honey-detecting-testers/
145•AkshatJ27•6h ago•31 comments

OpenAI's cash burn will be one of the big bubble questions of 2026

https://www.economist.com/leaders/2025/12/30/openais-cash-burn-will-be-one-of-the-big-bubble-ques...
244•1vuio0pswjnm7•6h ago•316 comments

Electrolysis can solve one of our biggest contamination problems

https://ethz.ch/en/news-and-events/eth-news/news/2025/11/electrolysis-can-solve-one-of-our-bigges...
131•PaulHoule•10h ago•35 comments

Loss32: Let's Build a Win32/Linux

https://loss32.org/
223•akka47•1d ago•322 comments

Mitsubishi Diatone D-160 (1985)

https://audio-database.com/MITSUBISHI-DIATONE/diatonesp/d-160-e.html
25•anigbrowl•2d ago•13 comments

Toro: Deploy Applications as Unikernels

https://github.com/torokernel/torokernel
120•ignoramous•11h ago•105 comments

What If Heavy Files Felt Heavy?

https://www.shiveesh.com/thoughts-and-ideas/what-if-heavy-files-actually-felt-heavy
5•shiveeshfotedar•5d ago•1 comments

Non-Zero-Sum Games

https://nonzerosum.games/
344•8organicbits•16h ago•178 comments

Reverse Engineering a Mysterious UDP Stream in My Hotel (2016)

https://www.gkbrk.com/hotel-music
183•bayesnet•1w ago•24 comments

Escaping containment: A security analysis of FreeBSD jails [video]

https://media.ccc.de/v/39c3-escaping-containment-a-security-analysis-of-freebsd-jails
64•todsacerdoti•8h ago•1 comments

Professional software developers don't vibe, they control

https://arxiv.org/abs/2512.14012
133•dpflan•8h ago•160 comments

L1TF Reloaded

https://github.com/ThijsRay/l1tf_reloaded
8•Fnoord•1h ago•0 comments

The British empire's resilient subsea telegraph network

https://subseacables.blogspot.com/2025/12/the-british-empires-resilient-subsea.html
172•giuliomagnifico•14h ago•43 comments

Show HN: RAMBnB.xyz P2P marketplace for RAM rentals

https://www.rambnb.xyz
11•olivierroy•4h ago•1 comments

Times New American: A Tale of Two Fonts

https://hsu.cy/2025/12/times-new-american/
230•firexcy•15h ago•139 comments

Approachable Swift Concurrency

https://fuckingapproachableswiftconcurrency.com/en/
162•wrxd•15h ago•80 comments

Go away Python

https://lorentz.app/blog-item.html?id=go-shebang
365•baalimago•19h ago•336 comments

Igniting the GPU: From Kernel Plumbing to 3D Rendering on RISC-V

https://mwilczynski.dev/posts/riscv-gpu-zink/
75•michalwilczynsk•14h ago•8 comments

What Happened to Abit Motherboards

https://dfarq.homeip.net/what-happened-to-abit-motherboards/
97•zdw•13h ago•68 comments

Five Years of Tinygrad

https://geohot.github.io//blog/jekyll/update/2025/12/29/five-years-of-tinygrad.html
195•iyaja•1d ago•87 comments

Netflix Open Content

https://opencontent.netflix.com/
610•tosh•17h ago•119 comments

S&P500 Priced in Gold

https://pricedingold.com/sp-500/
15•jcartw•3h ago•9 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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