frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Austin’s surge of new housing construction drove down rents

https://www.pew.org/en/research-and-analysis/articles/2026/03/18/austins-surge-of-new-housing-con...
275•matthest•2h ago•227 comments

Autoresearch for SAT Solvers

https://github.com/iliazintchenko/agent-sat
36•chaisan•1h ago•4 comments

Warranty Void If Regenerated

https://nearzero.software/p/warranty-void-if-regenerated
207•Stwerner•5h ago•113 comments

Nvidia greenboost: transparently extend GPU VRAM using system RAM/NVMe

https://gitlab.com/IsolatedOctopi/nvidia_greenboost
158•mmastrac•3d ago•28 comments

Show HN: Duplicate 3 layers in a 24B LLM, logical deduction .22→.76. No training

https://github.com/alainnothere/llm-circuit-finder
74•xlayn•4h ago•20 comments

OpenRocket

https://openrocket.info/
408•zeristor•3d ago•85 comments

Rob Pike’s Rules of Programming (1989)

https://www.cs.unc.edu/~stotts/COMP590-059-f24/robsrules.html
848•vismit2000•16h ago•413 comments

Wander – A tiny, decentralised tool to explore the small web

https://susam.net/wander/
212•susam•18h ago•53 comments

The math that explains why bell curves are everywhere

https://www.quantamagazine.org/the-math-that-explains-why-bell-curves-are-everywhere-20260316/
60•ibobev•2d ago•23 comments

Nvidia NemoClaw

https://github.com/NVIDIA/NemoClaw
244•hmokiguess•10h ago•190 comments

Show HN: Will my flight have Starlink?

177•bblcla•9h ago•237 comments

Book: The Emerging Science of Machine Learning Benchmarks

https://mlbenchmarks.org/00-preface.html
89•jxmorris12•4d ago•4 comments

What’s on HTTP?

https://whatsonhttp.com/
33•elixx•4h ago•10 comments

Nightingale – open-source karaoke app that works with any song on your computer

https://nightingale.cafe/
514•rzzzzru•18h ago•147 comments

An x86-64 back end for raven-uxn

https://www.mattkeeter.com/blog/2026-03-15-uxn/
11•dcre•3d ago•0 comments

CVE-2026-3888: Important Snap Flaw Enables Local Privilege Escalation to Root

https://blog.qualys.com/vulnerabilities-threat-research/2026/03/17/cve-2026-3888-important-snap-f...
100•askl•10h ago•63 comments

Show HN: I built 48 lightweight SVG backgrounds you can copy/paste

https://www.svgbackgrounds.com/set/free-svg-backgrounds-and-patterns/
172•visiwig•10h ago•30 comments

Show HN: Playing LongTurn FreeCiv with Friends

https://github.com/ndroo/freeciv.andrewmcgrath.info
51•verelo•7h ago•27 comments

2025 Turing award given for quantum information science

https://awards.acm.org/about/2025-turing
98•srvmshr•16h ago•26 comments

Czech Man's Stone in Barn's Foundations Is Rare Bronze Age Spearhead Mold

https://www.smithsonianmag.com/smart-news/a-czech-man-used-this-stone-in-his-barns-foundations-it...
5•bookofjoe•2d ago•1 comments

On a Boat

https://moq.dev/blog/on-a-boat/
128•mmcclure•5d ago•23 comments

Show HN: Tmux-IDE, OSS agent-first terminal IDE

https://tmux.thijsverreck.com
66•thijsverreck•8h ago•34 comments

RX – a new random-access JSON alternative

https://github.com/creationix/rx
10•creationix•2h ago•6 comments

OpenAI Has New Focus (on the IPO)

https://om.co/2026/03/17/openai-has-new-focus-on-the-ipo/
155•aamederen•15h ago•150 comments

Show HN: Hacker News archive (47M+ items, 11.6GB) as Parquet, updated every 5m

https://huggingface.co/datasets/open-index/hacker-news
307•tamnd•4d ago•133 comments

Machine Payments Protocol (MPP)

https://stripe.com/blog/machine-payments-protocol
149•bpierre•11h ago•70 comments

Despite Doubts, Federal Cyber Experts Approved Microsoft Cloud Service

https://www.propublica.org/article/microsoft-cloud-fedramp-cybersecurity-government
439•hn_acker•12h ago•201 comments

Measuring progress toward AGI: A cognitive framework

https://blog.google/innovation-and-ai/models-and-research/google-deepmind/measuring-agi-cognitive...
103•surprisetalk•14h ago•176 comments

Trevor Milton is raising funds for a new jet he claims will transform flying

https://www.wsj.com/business/trevor-milton-pardon-nikola-trump-3163e19c
94•jgalt212•13h ago•152 comments

Explore 19th Century Scientific Correspondence

https://epsilon.ac.uk/
22•rramadass•3d ago•3 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•10mo ago

Comments

balloob•10mo 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•10mo ago
Discussion for the other article in the series:

https://news.ycombinator.com/item?id=44011381

tomhow•10mo ago
Comments moved thither. Thanks!
pabs3•10mo ago
They are two different articles, I don't think that was correct.
tomhow•10mo 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•10mo ago
Thanks for the response, guess that makes sense.
pabs3•10mo 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?