frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

LittleSnitch for Linux

https://obdev.at/products/littlesnitch-linux/index.html
707•pluc•9h ago•212 comments

Open Source Security at Astral

https://astral.sh/blog/open-source-security-at-astral
177•vinhnx•5h ago•33 comments

I ported Mac OS X to the Nintendo Wii

https://bryankeller.github.io/2026/04/08/porting-mac-os-x-nintendo-wii.html
1576•blkhp19•17h ago•274 comments

Haunted Paper Toys

http://ravensblight.com/papertoys.html
81•exvi•2d ago•1 comments

Creating the Futurescape for the Fifth Element

https://theasc.com/articles/fantastic-voyage-creating-the-futurescape-for-the-fifth-element
8•nixass•25m ago•3 comments

C# in Unity 2026: Features Most Developers Still Don't Use

https://darkounity.com/blog/c-in-unity-2026-features-most-developers-still-dont-use
8•hacker_13•2d ago•1 comments

Process Manager for Autonomous AI Agents

https://botctl.dev/
34•ankitg12•3h ago•7 comments

The Importance of Being Idle

https://theamericanscholar.org/the-importance-of-being-idle/
179•Caiero•2d ago•96 comments

Dr. Dobb's Developer Library DVD 6

https://archive.org/details/DDJDVD6
33•kristianp•4d ago•10 comments

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

https://werwolv.net/posts/usb_for_sw_devs/
297•WerWolv•14h ago•38 comments

Understanding the Kalman filter with a simple radar example

https://kalmanfilter.net
338•alex_be•16h ago•44 comments

They're made out of meat (1991)

http://www.terrybisson.com/theyre-made-out-of-meat-2/
538•surprisetalk•22h ago•149 comments

Help Keep Thunderbird Alive

https://updates.thunderbird.net/en-US/thunderbird/140.0/apr26-1e/donate/
8•playfultones•2h ago•3 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
485•jfirebaugh•1d ago•546 comments

Six (and a half) intuitions for KL divergence

https://www.perfectlynormal.co.uk/blog-kl-divergence
78•jxmorris12•1d ago•9 comments

ML promises to be profoundly weird

https://aphyr.com/posts/411-the-future-of-everything-is-lies-i-guess
499•pabs3•20h ago•487 comments

Git commands I run before reading any code

https://piechowski.io/post/git-commands-before-reading-code/
2039•grepsedawk•1d ago•435 comments

Muse Spark: Scaling towards personal superintelligence

https://ai.meta.com/blog/introducing-muse-spark-msl/?_fb_noscript=1
340•chabons•17h ago•329 comments

Improving storage efficiency in Magic Pocket, Dropbox's immutable blob store

https://dropbox.tech/infrastructure/improving-storage-efficiency-in-magic-pocket-our-immutable-bl...
8•laluser•5d ago•0 comments

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

https://arxiv.org/abs/2604.05091
294•chrsw•21h ago•54 comments

I imported the full Linux kernel git history into pgit

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

Expanding Swift's IDE Support

https://swift.org/blog/expanding-swift-ide-support/
115•frizlab•14h ago•52 comments

Map Gesture Controls - Control maps with your hands

https://sanderdesnaijer.github.io/map-gesture-controls/
27•hebelehubele•4d ago•5 comments

Understanding Traceroute

https://tech.stonecharioteer.com/posts/2026/traceroute/
128•stonecharioteer•3d ago•21 comments

Ask HN: Any interesting niche hobbies?

366•e-topy•3d ago•540 comments

Show HN: A (marginally) useful x86-64 ELF executable in 301 bytes

https://github.com/meribold/btry
41•meribold•2d ago•8 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
308•CharlesW•12h ago•95 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...
106•DamnInteresting•1d ago•47 comments

Audio Reactive LED Strips Are Diabolically Hard

https://scottlawsonbc.com/post/audio-led
228•surprisetalk•1d ago•63 comments

Union types in C# 15

https://devblogs.microsoft.com/dotnet/csharp-15-union-types/
205•0x00C0FFEE•4d ago•184 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?