frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

C++: The Programming Language back cover raises questions not answered by front

https://devblogs.microsoft.com/oldnewthing/20260605-01/?p=112391
35•paulmooreparks•2h ago•3 comments

The intracies of modern camera lens repair (2024)

https://salvagedcircuitry.com/sigma-45mm.html
121•transistor-man•4h ago•39 comments

How LLMs work

https://www.0xkato.xyz/how-llms-actually-work/
109•0xkato•2d ago•23 comments

Pre-Modern Armies for Worldbuilders, Part I: Why They Fight

https://acoup.blog/2026/06/05/collections-pre-modern-armies-for-worldbuilders-part-i-why-they-fight/
26•gostsamo•1h ago•1 comments

Lockdown Mode

https://help.openai.com/en/articles/20001061-lockdown-mode
26•berlianta•1h ago•10 comments

Astronauts told to return to ISS after sheltering over air leak repairs

https://www.bbc.com/news/live/c4g44ew3g1kt
374•janpot•14h ago•240 comments

No Let, No Rec, No Problem: A Gentler Introduction to the Y and Z Combinators

https://irfanali.org/blog/zcom
10•sayyadirfanali•3d ago•1 comments

pg_durable: Microsoft open sources in-database durable execution

https://github.com/microsoft/pg_durable
366•coffeemug•13h ago•84 comments

New method turns ocean water into drinking water, without waste

https://www.rochester.edu/newscenter/what-is-desalination-definition-ocean-water-704732/
312•speckx•14h ago•137 comments

Gemma 4 QAT models: Optimizing compression for mobile and laptop efficiency

https://blog.google/innovation-and-ai/technology/developers-tools/quantization-aware-training-gem...
314•theanonymousone•13h ago•93 comments

Ask HN: What was your "oh shit" moment with GenAI?

247•andrehacker•1d ago•496 comments

Did Claude increase bugs in rsync?

https://alexispurslane.github.io/rsync-analysis/
364•logicprog•16h ago•371 comments

Mouseless – keyboard-driven control of macOS/Linux/Windows

https://mouseless.click
503•riddley•2d ago•210 comments

S&P 500 rejects SpaceX, also blocking entry for OpenAI and Anthropic

https://arstechnica.com/tech-policy/2026/06/sp-500-blocks-fast-spacex-entry-wont-waive-rule-for-u...
26•maltalex•52m ago•2 comments

Ask HN: Why is the HN crowd so anti-AI?

69•Ekami•2h ago•124 comments

My Agent Skill for Test-Driven Development

https://www.saturnci.com/my-agent-skill-for-test-driven-development.html
159•laxmena•1d ago•64 comments

Three of our worst VC stories

https://twitter.com/eastdakota/status/2062860530360959273
210•orgonon•10h ago•101 comments

Nordstjernen 1.0

https://github.com/nordstjernen-web/nordstjernen/releases/tag/1.0.0
33•andreasrosdal•5h ago•13 comments

Show HN: ABC Classic 100 Rankings visualised

https://classic100.gotski.workers.dev/
26•gotski•3h ago•16 comments

Gov.uk has replaced Stripe with Dutch provider Adyen

https://www.theregister.com/public-sector/2026/06/04/govuk-goes-dutch-on-payments-as-it-dumps-str...
393•toomuchtodo•12h ago•136 comments

The perils of UUID primary keys in SQLite

https://andersmurphy.com/2026/06/05/the-perils-of-uuid-primary-keys-in-sqlite.html
51•emschwartz•6h ago•24 comments

Nine Ways to Do Inheritance in Rust, a Language Without Inheritance

https://medium.com/@carlmkadie/nine-ways-to-do-inheritance-in-rust-a-language-without-inheritance...
24•pjmlp•2d ago•0 comments

Conventional Commits encourages focus on the wrong things

https://sumnerevans.com/posts/software-engineering/stop-using-conventional-commits/
288•jsve•13h ago•223 comments

The Quiet Numbers Station: Decoding Nineteen Years of GPS Cryptography

https://www.benthamsgaze.org/2026/06/02/the-quiet-numbers-station-decoding-nineteen-years-of-gps-...
77•lordgilman•16h ago•69 comments

Europe's largest Copper Age tomb: children's bones show ancient health crisis

https://phys.org/news/2026-05-europe-largest-copper-age-tomb.html
23•gmays•1d ago•5 comments

Transformers are inherently succinct

https://openreview.net/pdf?id=Yxz92UuPLQ
110•brandonb•10h ago•31 comments

Tracing a powerful GNSS interference source over Europe

https://arxiv.org/abs/2606.03673
377•mimorigasaka•20h ago•200 comments

India's surprise baby bust

https://www.economist.com/leaders/2026/06/04/indias-surprise-baby-bust-is-a-warning-to-the-world
156•hakonbogen•14h ago•696 comments

Cooldown Support for Ruby Bundler

https://blog.rubygems.org/2026/06/03/cooldown-let-new-gems-be-vetted.html
151•calyhre•3d ago•42 comments

I tested every IP KVM in my Homelab

https://www.jeffgeerling.com/blog/2026/i-tested-every-ip-kvm/
262•vquemener•15h ago•70 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?