frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Watch Los Angeles get built, one building at a time (1880–2026)

https://lax-skyline.parcelscope.net/
89•rustywasm•1h ago•29 comments

Finding a bug in Dummit and Foote's Abstract Algebra

https://kallus.org/blog/dummit_and_foote.html
12•evakhoury•3d ago•0 comments

Methods for Random Gradients (2024)

https://justinjay.wang/methods-for-random-gradients/
28•nickswalker•3d ago•3 comments

WeatherNext 3

https://deepmind.google/science/weathernext/
62•matthieu_bl•4d ago•6 comments

Simple Is Not Small

https://jyn.dev/simple-is-not-the-same-as-small/
138•zdw•3d ago•43 comments

Decoding the NEC V20 Microcode

https://martypc.blogspot.com/2026/09/decoding-nec-v20-microcode.html
75•mariuz•3d ago•3 comments

Caltech Mathathon – first hackathon ever devoted to research level mathematics

https://mathathonchallenge.com/index.html
190•astroanax•11h ago•57 comments

bzip3

https://github.com/iczelia/bzip3
328•tosh•6h ago•92 comments

The Dataflow Model Revisited

https://www.vldb.org/pvldb/volumes/19/paper/The%20Dataflow%20Model%20Revisited
61•scott_s•1d ago•11 comments

Decapitating a MacBook (2025)

https://mm-dev.rocks/series/decapitating-macbook-an-odyssey/
22•luu•1d ago•11 comments

Trusting-Trust Attack against an Entire Linux Distribution

https://arxiv.org/abs/2607.24888
36•signa11•2d ago•2 comments

216M Spy TVs – The LG Smart TV Problem [video]

https://www.youtube.com/watch?v=6IFVTcM28KA
269•treve•20h ago•595 comments

Academia as a d-index measuring contest

https://kevinmunger.substack.com/p/introducing-the-k-index
22•surprisetalk•5d ago•1 comments

Scientists observe Einstein's gravity in the quantum world

https://www.ox.ac.uk/news/2026-08-28-scientists-observe-einsteins-gravity-in-the-quantum-world
24•mudil•3d ago•4 comments

Keep Our Servers Running

https://blog.archive.org/2026/09/01/keep-our-servers-running-your-recurring-donation-goes-3x-this...
902•sonicrocketman•17h ago•223 comments

Icy Moons Are Ocean Worlds

https://mceglowski.substack.com/p/icy-moons-are-ocean-worlds
74•worldvoyageur•1d ago•10 comments

Replaceable but Employed: Automation and the Meaning of Work

https://www.nber.org/papers/w35559
14•mooreds•1h ago•0 comments

My practical approach to surfing the web safely

https://molily.de/safe-websurfing/
33•ethanhawksley•5d ago•11 comments

This Month in Ladybird – August 2026

https://ladybird.org/newsletter/2026-08-31/
74•exploraz•2d ago•6 comments

How to bring up the Linux Kernel on a new platform

https://werwolv.net/posts/linux_bringup/
35•WerWolv•4d ago•4 comments

Catching Crumbs from the Table (2000)

https://www.nature.com/articles/35014679
8•stefanpie•1d ago•3 comments

Whistle Synth Mac App

https://www.jefftk.com/p/whistle-synth-mac-app
45•luu•3d ago•12 comments

Live map of public transport in Belgium

https://openbaarvervoerbelgie.be/
169•coinfused•11h ago•72 comments

Schemy Lisp En DOS

https://sled.neocities.org/
18•AlexeyBrin•1d ago•1 comments

Show HN: HomeCat – Design your backyard office

https://myhomecat.com
16•dearilos•2h ago•9 comments

Show HN: Wg-admin – web UI for an existing WireGuard host

https://github.com/logimaxx/wg-admin
15•vsergione•3h ago•3 comments

Rebuilding a 1995 GPS Time Server so I don't get Telstra'd

https://www.jeffgeerling.com/blog/2026/truetime-xl-gps-time-server-restomod/
15•Brajeshwar•2d ago•6 comments

Bill Gates tries to install MovieMaker (2003)

https://www.techemails.com/p/bill-gates-tries-to-install-movie-maker
257•highfrequency•5h ago•170 comments

Speculative Decoding in vLLM on AMD GPUs

https://vllm.ai/blog/2026-08-23-speculative-decoding-amd-gpus
120•ankitg12•11h ago•40 comments

Smartphone makers don't bother to comply with EU repairability requirements

https://www.theregister.com/personal-tech/2026/09/07/smartphone-makers-dont-bother-to-comply-with...
257•mdp2021•8h ago•140 comments
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?