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...
434•gnabgib•7h ago•284 comments

AWS: Inaccurate Estimated Billing Data – $1.7 billion

1121•nprateem•20h ago•663 comments

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

485•nicholasjbs•13h ago•49 comments

Reviving a 15-year-old netbook with Arch Linux

https://parksb.github.io/en/article/41.html
40•parksb•3d ago•18 comments

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

https://www.bbc.com/news/articles/cy4kdd1e0ejo
415•neversaydie•15h ago•251 comments

The Zilog Z80 has turned 50

https://goliath32.com/blog/z80.html
195•st_goliath•10h ago•61 comments

Moonstone: Modern, cross-platform Lua runtime and package manager written in Zig

https://moonstone.sh/
35•ksymph•4h ago•9 comments

I Started a "Dirt Notebook"

https://pinewind.bearblog.dev/i-started-a-dirt-notebook/
38•herbertl•4h ago•29 comments

TP-Link Kasa cameras leaked home GPS via unauthenticated UDP for 6 years

https://github.com/BadChemical/IoT-Vulnerability-Research-Public/blob/main/TP-Link_Kasa_EC71/Kasa...
74•BadChemical•8h ago•18 comments

Learning a few things about running SQLite

https://jvns.ca/blog/2026/07/17/learning-about-running-sqlite/
206•surprisetalk•12h ago•51 comments

The Isomorphic Labs Drug Design Engine unlocks a new frontier beyond AlphaFold

https://www.isomorphiclabs.com/articles/the-isomorphic-labs-drug-design-engine-unlocks-a-new-fron...
60•andsoitis•6h ago•6 comments

Regressive JPEGs

https://maurycyz.com/projects/bad_jpeg/
15•vitaut•2h ago•0 comments

Shipping OpenStrike: A Counter-Strike-Shaped FPS on a 2004 Handheld

https://pocketjs.dev/blog/shipping-openstrike/
25•itvision•6d ago•12 comments

Vāgdhenu: A Sanskrit Chanting TTS System

https://prathosh.in/vagdhenu/
125•subinalex•4d ago•24 comments

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

https://simonwillison.net/2026/Jul/16/kimi-k3/
305•droidjj•15h ago•165 comments

DrDroid (YC W23) Is Hiring

https://www.ycombinator.com/companies/drdroid/jobs/w45QcNV-product-engineer-assignment-mandatory
1•TheBengaluruGuy•4h ago

Stenchill: 3D Printable Solder Paste Stencil Generator

https://www.stenchill.com/en/
28•radeeyate•5h ago•5 comments

An Update on Igalia's Layer Based SVG Engine in WebKit (Reducing Layer Overhead)

https://blogs.igalia.com/nzimmermann/posts/2026-07-14-lbse-conditional-layers/
29•bkardell•3d ago•1 comments

Open Book Touch: open-source e-reader

https://www.crowdsupply.com/oddly-specific-objects/open-book-touch
85•surprisetalk•9h ago•25 comments

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

https://curiouscoding.nl/posts/static-search-tree/
82•lalitmaganti•9h ago•3 comments

Mac gaming is finally getting the overpowered upgrade it deserves

https://www.macworld.com/article/3189951/apples-latest-game-porting-toolkit-beta-changed-how-i-th...
27•kristianp•1h ago•17 comments

Lego building instructions through time

https://www.lego.com/en-us/history/articles/d-lego-building-instructions-through-time
93•NaOH•11h ago•19 comments

Painting the sides of railroad rails white to reduce derailment

https://www.up.com/news/safety/Tracking-Rail-Heat-260608
72•zdw•9h ago•40 comments

Battery packs: Let's talk about crates, baby

https://smallcultfollowing.com/babysteps/blog/2026/07/15/battery-packs/
5•MeetingsBrowser•1d ago•2 comments

Frank Lloyd Wright’s first home

https://www.architecturaldigest.com/story/frank-lloyd-wright-home-and-studio-everything-you-need-...
95•NaOH•5d ago•47 comments

The state of open source AI

https://stateofopensource.ai/
407•rellem•15h ago•297 comments

Show HN: A zoomable timeline of 4M Wikipedia events

https://app.everything.diena.co/
74•lortex•11h ago•30 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
160•hmm37•8h ago•87 comments

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

https://improvesomething.today/responses-to-problems/
219•surprisetalk•15h ago•120 comments

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

https://honeypotlive.cc/
151•tusksm•15h ago•55 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?