frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

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?

Large language models develop novel social biases through adaptive exploration

https://openreview.net/challenge?redirect=%2Fforum%3Fid%3Dpc7fqaOcAH
51•paimapi•1h ago•18 comments

Google DeepMind Releases AlphaGenome Atlas

https://blog.google/innovation-and-ai/models-and-research/google-deepmind/alphagenome-atlas/
471•utiiiD•8h ago•113 comments

Navier-Stokes – Tristan Buckmaster [pdf]

https://cims.nyu.edu/~tristanb/statement.pdf
1099•procedurecall•17h ago•484 comments

How to build a printer

https://nishantjosh.dev/blogs/how-to-build-a-fking-printer/
47•cat-whisperer•2h ago•3 comments

On the Navier–Stokes Millennium Prize Problem

https://openai.com/index/navier-stokes-solution/
1032•tedsanders•6h ago•859 comments

DaVinci Resolve 21.1

https://www.blackmagicdesign.com/media/release/20260908-03
330•tosh•9h ago•148 comments

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

https://github.com/argonautlabsai/deltafin
188•Argonautlabs•3h ago•90 comments

The Microeconomics of Artificial Intelligence (Open Access)

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

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

https://mathstodon.xyz/@tao/117237320796901560
35•_alternator_•2h ago•16 comments

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

https://quesma.com/blog/qwen38-27b-quantizations-benchmarked/
200•stared•8h ago•97 comments

A Topological Picture Book, Rendered

https://e-infinity.space/picture-book/
9•mathgenius•57m ago•0 comments

Mercury 2.5

https://www.inceptionlabs.ai/blog/introducing-mercury-2-5
108•Topfi•3h ago•13 comments

Animation in Bevy: The Big Picture

https://glocq.com/en/blog/20260827/
33•ibobev•3h ago•1 comments

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

https://github.com/ayghri/i-have-adhd
278•domhudson•9h ago•216 comments

Tracing np.add, all the way down

https://blog.veitheller.de/numpy.html
26•luu•4d ago•2 comments

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

https://uecker.codeberg.page/2026-09-05.html
49•uecker•3d ago•6 comments

Muse: Meta's personal AI agent, features and capabilities

https://ai.meta.com/muse/
210•yks•4h ago•202 comments

Show HN: LLM Attention Visualization

https://ishamf.dev/p/llm-attention-visualizer/
104•ifz•6h ago•19 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/
68•metrofun•3d ago•33 comments

The Helicopter with Radioactive Blades

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

Show HN: Copperhead – Hardware as Fast as Software

https://copperhead.sh/
195•animeshchouhan•9h ago•76 comments

Reverse Engineering an ASIC

https://kjartanvandriel.github.io/asic/
13•burekqueen•1d ago•1 comments

The 92-Year-Old Mathematician and the Teenage Apprentice

https://www.nytimes.com/2026/09/06/science/92-year-old-mathematician-apprentice.html
123•robinhouston•2d ago•11 comments

The two Christian saints who are the Buddha

https://signoregalilei.com/2026/08/30/the-two-christian-saints-who-are-secretly-the-buddha/
199•surprisetalk•8h ago•138 comments

C*: Unifying Programming and Verification in C

https://arxiv.org/abs/2504.02246
66•rramadass•7h ago•40 comments

Connecting the Machines

https://herdr.dev/blog/connecting-the-machines/
71•collinmanderson•6h ago•24 comments

Function Arguments Are Not Function Colors

https://jerf.org/iri/post/2026/func_args_are_not_colors/
29•ingve•4h ago•13 comments

ZX Spectrum: Experimenting with 1-Bit Sound

https://bumbershootsoft.wordpress.com/2026/09/05/zx-spectrum-experimenting-with-1-bit-sound/
90•ibobev•8h ago•26 comments

AlphaGenome Atlas predictive map of every DNA letter change in the human genome

https://deepmind.google/blog/alphagenome-atlas-a-predictive-map-of-every-possible-dna-letter-chan...
76•fady0•9h ago•9 comments

FreeBSD 14.5-Release

https://www.freebsd.org/releases/14.5R/announce/
108•joshcsimmons•11h ago•21 comments