frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Things to know when you get cancer

https://jjmaxwell4.com/writing/things-to-know-when-you-get-cancer/
1163•jjmaxwell4•11h ago•290 comments

OpenCode 2.0

https://anoma.ly/notes/opencode-2-0/
514•gmays•10h ago•205 comments

Tiny Little Office

https://tinylittleoffice.com/
322•donohoe•8h ago•45 comments

LFM2.5-24B-A2B: Built for fast on-device agents

https://www.liquid.ai/blog/lfm2-5-24b-a2b
166•gmays•6h ago•39 comments

Do dentists know what they're doing?

https://mapwriting.substack.com/p/dentists
604•doitLP•3d ago•425 comments

Donaldson Futuro House in Idyllwild, California, USA

https://www.wowhaus.co.uk/2026/10/12/donaldson-futuro-house-in-idyllwild-california-usa/
36•rmason•1d ago•7 comments

Americans' social activity has steeply declined in the past 30 years

https://www.dataforprogress.org/blog/2026/9/29/americans-social-activity-has-steeply-declined-in-...
343•hubraumhugo•14h ago•331 comments

Catch a Bird – I made it for my own sanity

https://catchabird.com
105•eduardsik•2d ago•23 comments

The Double Headed Stack Allocator

https://blog.demofox.org/2026/10/03/the-double-headed-stack-allocator/
49•g0xA52A2A•4h ago•11 comments

Show HN: Flipflop, iroh-powered persistent tunnels for filesharing

https://github.com/andunieee/flipflop
21•andunie•2h ago•5 comments

The Toftwood Male Voice Choir: A Mystery Pressed in Vinyl

https://ei3lh.eu/2026/10/11/the-toftwood-male-voice-choir-a-mystery-pressed-in-vinyl/
20•austinallegro•3d ago•1 comments

It took me nine years to hack my Xbox 360

https://kennedn.com/blog/posts/glitching/
58•kennedn•1d ago•5 comments

Better HTTP/1 connection reuse in Go 1.27

https://go.dev/blog/http-connection-reuse
235•allddd•14h ago•34 comments

We’re releasing Jev 1.14.0 along with experimental features for dreamers

https://typesafe.ai/blog/jev-1-14
265•emschwartz•9h ago•85 comments

Containment and monitoring failures are to blame for AI hacking reports: experts

https://www.csoonline.com/article/4234854/ai-agents-arent-going-rogue-frontier-labs-are-skipping-...
874•latexr•13h ago•509 comments

Show HN: Petal, open-source CoScreen/ScreenHero finally free

https://petal.live/
155•thedracle•12h ago•37 comments

Your C is not standard C

https://sebsite.pw/w/20261012-notstdc.html
73•dverlaeckt80•1d ago•43 comments

David Rudnick on "borderline impossible" process of designing Arsenal typeface

https://www.itsnicethat.com/features/david-rudnick-johnnie-campbell-arsenal-rocastle-typeface-gra...
8•droidjj•2d ago•1 comments

Ask HN: CAD for wood working with LLM support?

62•reacharavindh•2d ago•52 comments

Why is every rationalist blog post way too long?

https://alexwennerberg.com/blog/2026-10-13-long.html
309•epestr•1d ago•238 comments

How Amazon pushes up prices all across the Internet

https://www.not-ship.com/how-amazon-pushes-up-prices-all-across-the-internet/
794•sighborg•21h ago•624 comments

Phloem: Git history grown like a slime mold

https://phloem.stemdeck.app/
105•thclpr•2d ago•21 comments

Fancy Curl Sites

https://nytpu.com/gemlog/2026-03-18
111•adunk•11h ago•24 comments

Virtual Oxide Labs: Emulating a Full Oxide Rack

https://oxide.computer/blog/voxel-labs
110•tosh•12h ago•11 comments

Submarine cable resilience

https://blog.apnic.net/2026/10/14/submarine-cable-resilience/
147•speckx•15h ago•57 comments

Has AI tells

https://theconsensus.dev/blog/2026/10/14/has-ai-tells.html?focus=1
110•7777777phil•14h ago•97 comments

Fire at Starlink site in Bulgaria after suspected sabotage in Poland

https://dpa-international.com/politics/urn:newsml:dpa.com:20090101:261014-930-839530/
347•ilamont•12h ago•229 comments

Passkeys are not a trap

https://scotthelme.co.uk/passkeys-are-not-a-trap/
571•speckx•15h ago•725 comments

Anthropic's Scion is heavily inspired by Mononoke

https://sunshowers.io/posts/anthropic-mononoke/
347•sunshowers•10h ago•128 comments

Show HN: My Terminal Themes Web App

13•bado•4h ago•5 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?