frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

I ported Mac OS X to the Nintendo Wii

https://bryankeller.github.io/2026/04/08/porting-mac-os-x-nintendo-wii.html
1211•blkhp19•9h ago•212 comments

LittleSnitch for Linux

https://obdev.at/products/littlesnitch-linux/index.html
30•pluc•29m ago•10 comments

USB for Software Developers: An introduction to writing userspace USB drivers

https://werwolv.net/posts/usb_for_sw_devs/
171•WerWolv•5h ago•22 comments

Git commands I run before reading any code

https://piechowski.io/post/git-commands-before-reading-code/
1778•grepsedawk•16h ago•382 comments

Understanding the Kalman filter with a simple radar example

https://kalmanfilter.net
205•alex_be•7h ago•31 comments

They're made out of meat (1991)

http://www.terrybisson.com/theyre-made-out-of-meat-2/
397•surprisetalk•13h ago•111 comments

Muse Spark: Scaling towards personal superintelligence

https://ai.meta.com/blog/introducing-muse-spark-msl/?_fb_noscript=1
256•chabons•8h ago•281 comments

Expanding Swift's IDE Support

https://swift.org/blog/expanding-swift-ide-support/
73•frizlab•5h ago•37 comments

ML promises to be profoundly weird

https://aphyr.com/posts/411-the-future-of-everything-is-lies-i-guess
360•pabs3•11h ago•397 comments

Škoda DuoBell: A bicycle bell that penetrates noise-cancelling headphones

https://www.skoda-storyboard.com/en/skoda-world/skoda-duobell-a-bicycle-bell-that-outsmarts-even-...
517•ra•16h ago•533 comments

What Does It Mean to "Write Like You Talk"?

https://arjunpanickssery.substack.com/p/what-does-it-mean-to-write-like-you
9•surprisetalk•2d ago•2 comments

Pgit: I Imported the Linux Kernel into PostgreSQL

https://oseifert.ch/blog/linux-kernel-pgit
64•ImGajeed76•3d ago•9 comments

John Deere to pay $99M in right-to-repair settlement

https://www.thedrive.com/news/john-deere-to-pay-99-million-in-monumental-right-to-repair-settlement
155•CharlesW•4h ago•41 comments

MegaTrain: Full Precision Training of 100B+ Parameter LLMs on a Single GPU

https://arxiv.org/abs/2604.05091
254•chrsw•12h ago•48 comments

Show HN: Is Hormuz open yet?

https://www.ishormuzopenyet.com/
233•anonfunction•3h ago•98 comments

Who is Satoshi Nakamoto? My quest to unmask Bitcoin's creator

https://www.nytimes.com/2026/04/08/business/bitcoin-satoshi-nakamoto-identity-adam-back.html
287•jfirebaugh•20h ago•201 comments

Understanding Traceroute

https://tech.stonecharioteer.com/posts/2026/traceroute/
81•stonecharioteer•2d ago•10 comments

Show HN: Orange Juice – Small UX improvements that make HN easier to read

http://oj-hn.com/
80•latchkey•6h ago•110 comments

Show HN: Tired of logic in useEffect, I built a class-based React state manager

https://thales.me/posts/why-i-built-snapstate/
14•thalesfp•3h ago•21 comments

What does ⍋⍋ even mean? (2023)

https://blog.wilsonb.com/posts/2023-08-04-what-does-grade-grade-even-mean.html
34•tosh•3d ago•17 comments

Ask HN: Any interesting niche hobbies?

244•e-topy•3d ago•383 comments

I've been waiting over a month for Anthropic to respond to my billing issue

https://nickvecchioni.github.io/thoughts/2026/04/08/anthropic-support-doesnt-exist/
258•nickvec•7h ago•134 comments

Automatic registration for US Military draft to begin in December

https://thehill.com/policy/defense/5822914-automatic-registration-military-draft/
31•c420•1h ago•34 comments

We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2

https://blog.railway.com/p/moving-railways-frontend-off-nextjs
175•bundie•18h ago•160 comments

US cities are axing Flock Safety surveillance technology

https://www.cnet.com/home/security/when-flock-comes-to-town-why-cities-are-axing-the-controversia...
621•giuliomagnifico•12h ago•360 comments

Microsoft terminates VeraCrypt account, halting Windows updates

https://www.404media.co/microsoft-abruptly-terminates-veracrypt-account-halting-windows-updates/
458•donohoe•10h ago•179 comments

Exposing and Understanding Scrolling Transfer Functions (2012) [pdf]

https://direction.bordeaux.inria.fr/~roussel/publications/2012-UIST-scrolling-tf.pdf
6•t23414321•2d ago•0 comments

Teardown of unreleased LG Rollable shows why rollable phones aren't a thing

https://arstechnica.com/gadgets/2026/04/teardown-of-unreleased-lg-rollable-shows-why-rollable-pho...
78•DamnInteresting•1d ago•37 comments

Show HN: Skrun – Deploy any agent skill as an API

https://github.com/skrun-dev/skrun
41•frizull•12h ago•9 comments

Audio Reactive LED Strips Are Diabolically Hard

https://scottlawsonbc.com/post/audio-led
194•surprisetalk•1d ago•57 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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