frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Kaiser nurses say AI, workplace surveillance are making their jobs, care worse

https://localnewsmatters.org/2026/07/15/kaiser-nurses-say-ai-workplace-surveillance-are-making-th...
79•gnabgib•50m ago•54 comments

The Zilog Z80 has turned 50

https://goliath32.com/blog/z80.html
138•st_goliath•3h ago•36 comments

AWS: Inaccurate Estimated Billing Data – $1.7 billion

985•nprateem•13h ago•615 comments

Thanks HN for 15 years of support and helping me find my life's work

192•nicholasjbs•6h ago•14 comments

First atmosphere found on Earth-like planet in habitable zone of distant star

https://www.bbc.com/news/articles/cy4kdd1e0ejo
335•neversaydie•9h ago•218 comments

Learning a few things about running SQLite

https://jvns.ca/blog/2026/07/17/learning-about-running-sqlite/
131•surprisetalk•5h ago•28 comments

Kimi K3, and what we can still learn from the pelican benchmark

https://simonwillison.net/2026/Jul/16/kimi-k3/
241•droidjj•8h ago•136 comments

FAA lets Boeing sign off on 737 MAX, 787 airworthiness certificates again

https://www.cnbc.com/2026/07/17/faa-boeing-737-max-787.html
73•hmm37•1h ago•35 comments

Static search trees: 40x faster than binary search (2024)

https://curiouscoding.nl/posts/static-search-tree/
12•lalitmaganti•2h ago•0 comments

Open Book Touch: open-source e-reader

https://www.crowdsupply.com/oddly-specific-objects/open-book-touch
14•surprisetalk•2h ago•1 comments

Topcoat: The full full-stack framework for Rust

https://github.com/tokio-rs/topcoat
16•wertyk•2h ago•7 comments

The state of open source AI

https://stateofopensource.ai/
352•rellem•8h ago•251 comments

Painting the sides of railroad rails white to reduce derailment

https://www.up.com/news/safety/Tracking-Rail-Heat-260608
12•zdw•3h ago•1 comments

Frank Lloyd Wright’s first home

https://www.architecturaldigest.com/story/frank-lloyd-wright-home-and-studio-everything-you-need-...
67•NaOH•4d ago•37 comments

Show HN: A zoomable timeline of 4M Wikipedia events

https://app.everything.diena.co/
41•lortex•4h ago•21 comments

MoonBASIC: A modern BASIC for building 2D and 3D games

https://github.com/CharmingBlaze/moonbasic
38•klaussilveira•3d ago•9 comments

Show HN: Watch bots interact with an SSH honeypot in real time

https://honeypotlive.cc/
135•tusksm•9h ago•48 comments

Lego building instructions through time

https://www.lego.com/en-us/history/articles/d-lego-building-instructions-through-time
37•NaOH•4h ago•7 comments

"Disk Not Ejected Properly": What It Means

https://bombich.com/blog/2026/07/07/disk-not-ejected-properly
3•speckx•1w ago•0 comments

Lobste.rs is now running on SQLite

https://lobste.rs/s/ko1ji1
108•abetusk•4d ago•80 comments

More Bounce to the Ounce

https://mceglowski.substack.com/p/more-bounce-to-the-ounce
102•pavel_lishin•9h ago•37 comments

Workspaces – Explore the workspaces of modern creators

https://workspaces.xyz/
66•ryangilbert•7h ago•50 comments

AI Meets Cryptography 2: What AI Found in OpenVM's ZkVM

https://blog.zksecurity.xyz/posts/openvm-bugs/
79•duha•8h ago•3 comments

Homomorphically encrypted CIFAR-10 inference in 200ms

https://sofar.belfortlabs.cloud/
59•j2kun•6h ago•30 comments

Three ways people respond to a problem (other than solving it)

https://improvesomething.today/responses-to-problems/
175•surprisetalk•9h ago•108 comments

Manufact (YC S25) Is Hiring a Senior infra engineer to build the MCP cloud

https://www.ycombinator.com/companies/manufact/jobs/Dh6PYP5-senior-infrastructure-engineer
1•luigipederzani•9h ago

Designing emoji for the way we communicate today

https://blog.google/products-and-platforms/platforms/android/world-emoji-day-noto-3d/
42•pentagrama•6h ago•63 comments

The US grocery slowdown is real

https://www.bain.com/insights/the-us-grocery-slowdown-is-real-snap-chart/
45•toomuchtodo•1h ago•51 comments

Evidence of inconsistencies in evaluation process and selection of winners

https://www.kaggle.com/competitions/kaggle-measuring-agi/discussion/724918#3498423
428•twerkmeister•11h ago•268 comments

Latent Space as a New Medium

https://kevinkelly.substack.com/p/latent-space-as-a-new-medium
81•thm•4d ago•24 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?