frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

We're going to need default hard budget caps on pretty much everything

https://simonwillison.net/2026/Oct/3/default-hard-budget-caps/
183•elffjs•2h ago•94 comments

Bob Cringely Has Died

96•paveworld•1h ago•13 comments

Hole Punch: Sling your spaceship around gravitational fields

https://notoriousbfg.com/hole-punch/
243•trwhite•8h ago•61 comments

Treachery in the Rodin Museum 3D scan verdict

https://cosmowenman.substack.com/p/rodin-museum-3d-scan-verdict
89•CosmoWenman•8h ago•45 comments

The work by Valve's Timur Kristóf on improving old AMD GPUs on Linux

https://www.phoronix.com/news/XDC-2026-Valve-Timur-AMDGPU
147•speckx•7h ago•21 comments

Reasons I didn't become an EMT, ranked

https://ben.stolovitz.com/posts/reasons-not-emt-ranked/
96•citelao•5h ago•49 comments

Celebrating the 100th birthday of the kidney donated to him as a teenager

https://www.whec.com/top-news/webster-man-celebrating-the-100th-birthday-of-the-kidney-his-mom-do...
151•gscott•2d ago•40 comments

OpenAI safety leader quits, warning AI company's culture is 'broken'

https://www.theguardian.com/technology/2026/oct/03/openai-safety-leader-quits-warning-ai-companys...
170•jethronethro•4h ago•120 comments

Kolibri: A Sovereign Open-Weight Model

https://aleph-alpha.com/en/blog/kolibri-has-landed-a-sovereign-open-weight-model/
523•bastitx•16h ago•302 comments

Math's pedagogical curse – Grant Sanderson [video]

https://www.youtube.com/watch?v=UOuxo6SA8Uc
13•bobajeff•1d ago•6 comments

So You Think You Could Be an Electrician?

https://asteriskmag.com/issues/15/so-you-think-you-could-be-an-electrician
17•zdw•3d ago•4 comments

New York City should carefully measure a new tree

https://blog.willmeye.rs/new-york-city-should-carefully-measure-a-new-tree/
46•willmeyers•23h ago•9 comments

Your body of work thinks back at you

https://photoni.st/index.php/2026/09/25/your-body-of-work-thinks-back-at-you/
22•surprisetalk•3d ago•1 comments

Show HN: Thoreau BASIC – What if BASIC hadn't gone out of fashion?

https://thoreaubasic.com/
35•Gorsefound•18h ago•10 comments

FTL: A new operating system for clouds

https://ftl-os.org/
151•romac•11h ago•60 comments

Getting the most out of Opus 5.5 in Claude and Claude Code

https://claude.dev/blog/getting-the-most-out-of-opus-5-5/
165•saikatsg•7h ago•123 comments

Agents don't need memory, they need documentation

https://liao.gg/blog/agents-dont-need-memory
65•kmeh•9h ago•48 comments

Surely you have ultra-wideband radios on your bins too?

https://sjg.io/writing/binrange-have-you-actually-put-the-bins-out/
45•simonjgreen•5h ago•22 comments

Federal judge calls Flock 'indiscriminate mass surveillance'

https://techcrunch.com/2026/10/03/federal-judge-calls-flock-indiscriminate-mass-surveillance/
319•sbulaev•4h ago•205 comments

Apple's "Clean Design" Is Stupidity When It Comes to Hiding Fire Extinguishers

https://www.gadgetreview.com/apples-clean-design-is-stupidity-when-it-comes-to-hiding-fire-exting...
46•josephcsible•2h ago•11 comments

Docker has always used microVMs (well since 2016)

https://dave.recoil.org/docker-has-always-used-microvms/
23•avsm•10h ago•15 comments

Show HN: Pi pod – Run your pi coding agent in sandboxes on your own server

https://pipod.dev/
77•edverma2•1d ago•30 comments

Memory-Safe WebP Decoding

https://halide.cx/blog/wpd/
42•computerbuster•20h ago•12 comments

RetailReady (YC W24) Is Hiring

https://www.ycombinator.com/companies/retailready/jobs/bFcgIe4-implementations
1•sarah74•9h ago

Woking Electrical Control Room (2016)

http://www.darbiansphotography.com/woking-electrical-control-room-urbex
126•NaOH•1d ago•25 comments

RSS Feed Best Practices (2022)

https://kevincox.ca/2022/05/06/rss-feed-best-practices/
40•KomoD•7h ago•8 comments

How to hack time, with C2PA

https://www.da.vidbuchanan.co.uk/blog/hacking-time.html
24•Retr0id•7h ago•3 comments

Automating my 35mm film scanning pipeline

https://shannadige.com/blog/darkroom/
16•shannadige•8h ago•9 comments

C++ Insights – See your source code with the eyes of a Compiler

https://github.com/andreasfertig/cppinsights
139•rramadass•2d ago•28 comments

We want you to build the next Git platform on Cloudflare

https://blog.cloudflare.com/next-git-platform-on-cloudflare/
100•geoffbp•6h ago•94 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?