frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Keep Our Servers Running

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

Making a Python interpreter in 1024 bytes

https://austinhenley.com/blog/python1024.html
195•azhenley•8h ago•70 comments

I'm a seeing-eye dog for a computer

https://claytonwramsey.com/blog/seeing-eye/
58•claytonwramsey•3d ago•43 comments

It took a year to ship WebAssembly in Anubis

https://anubis.techaro.lol/blog/2026/anubis-wasm/
239•xena•10h ago•119 comments

Ask HN: Fable hacked my piano, can I release the results?

107•jmpman•1d ago•57 comments

Ask HN: How do you manage skills files?

84•imadtaieber•11h ago•66 comments

Ask HN: Would you read a statistics textbook?

65•usernametaken29•1d ago•28 comments

Has anybody seen my keys? A key-hierarchy strategy for rack-level security

https://rfd.shared.oxide.computer/rfd/0301
20•cyb0rg0•5h ago•1 comments

Nitter and XCancel resume service after legal advice

https://github.com/zedeus/nitter/commit/1428b4c2b4246f92a7e5b2673438e5fb39fcc4a3
664•zImPatrick•13h ago•308 comments

I refused to train the AI that could replace me

https://restofworld.org/2026/ai-training-jobs-expert-replacement/
62•colinprince•2h ago•47 comments

Mmuko Boot Sequence – a tiny freestanding C kernel that boots in QEMU

https://github.com/obinexus/mmuko-boot
4•obinexus•3d ago•1 comments

Babylonian Lamb Stew with Beets (1750–1730 BCE)

https://babylonian-collection.yale.edu/about/babylonian-cooking
133•yubblegum•3d ago•86 comments

GrapheneOS Overhauled Default Apps and Secure Clipboard

https://grapheneos.social/@GrapheneOS/117225539756835649
268•Cider9986•10h ago•192 comments

Show HN: Engrim – A universal, local-first SQLite memory engine for AI CLIs

https://github.com/timgordontg/engrim
14•timgordontg•2h ago•2 comments

Harnessing the Universal Geometry of Embeddings

https://arxiv.org/abs/2505.12540
71•ur-whale•10h ago•25 comments

Show HN: GET Together – A social network where you don't need POST to Post

https://gettogether.dev
36•nchudleigh•5h ago•12 comments

Every Novel Is Boring–Until It Isn't

https://www.publicbooks.org/every-novel-is-boring-until-it-isnt/
49•samclemens•3d ago•33 comments

Signing TLS handshakes inside a TPM

https://bschaatsbergen.com/posts/go-tpm-tls/
20•bschaatsbergen•10h ago•15 comments

TiVo to charge money for skipping commercials in your own recordings

https://cordcuttersnews.com/tivo-plans-to-end-free-automatic-commercial-skipping-in-november-test...
39•dmitrygr•2h ago•9 comments

Switzerland's Federal Government Is Replacing Microsoft on 3k Computers

https://itsfoss.com/news/switzerland-replace-microssoft-pilot/
24•ivell•1h ago•11 comments

Research acceleration: The view inside OpenAI

https://openai.com/index/research-acceleration-view-inside-openai
157•iamsyr•16h ago•103 comments

The NX bit is not just about security

https://purplesyringa.moe/blog/guest/the-nx-bit-is-not-just-about-security/
61•torutofu•2d ago•34 comments

Asahi Linux on M3

https://asahilinux.org/2026/09/m2-episode-1/
426•mdp2021•17h ago•257 comments

Show HN: Mador – Make any DOM reactive with a tiny 80-line Proxy state tuple

https://github.com/marsbos/mador
85•bosmarcel•10h ago•26 comments

An Alien Mind

https://openai.com/index/an-alien-mind/
393•tosh•14h ago•341 comments

Is mathematics about to enter the conservatory?

https://mbmccoy.dev/posts/mathematical-conservatory/
35•_alternator_•8h ago•58 comments

Black Hole of Los Alamos: Seller of surplus nuclear research materials (2011)

https://www.atlasobscura.com/places/black-hole-of-los-alamos
60•Bluestein•4d ago•15 comments

Please don't rearrange our shoes when we turn up, paramedics in Japan urge

https://www.theguardian.com/world/2026/aug/28/never-tidy-paramedics-shoes-japan-custom-etiquette
78•high_na_euv•3d ago•85 comments

NetBSD 9.5 released and EOL for NetBSD-9

https://blog.netbsd.org/tnf/entry/netbsd_9_5_released_and
126•jaypatelani•15h ago•12 comments

Reverse engineering the storage format for an undocumented database

https://blog.glazer.ee/posts/converting-cronos/
46•pintprint•3d ago•4 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?