frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Terence Tao Responds to the OpenAI Math Drop

https://mathstodon.xyz/@tao/117395269325940185
29•ent101•25m ago•3 comments

Claude Haiku 5.5

https://www.anthropic.com/claude-haiku-5-5
784•sfkgtbor•11h ago•388 comments

Living off-grid: Hundred Rabbits

https://100r.ca/site/home.html
106•Muhammad523•2d ago•20 comments

Margaret Hamilton has died

https://news.mit.edu/2026/margaret-hamilton-computing-pioneer-dies-1007
1127•muglug•8h ago•126 comments

A 100x faster* alternative to homebrew

https://github.com/zerobrewhq/zerobrew
21•cachebag•2h ago•11 comments

How did Rosalind Franklin miss the helix in her iconic DNA image? She didn't

https://www.science.org/content/article/how-did-rosalind-franklin-miss-helix-her-iconic-dna-image...
127•pavel_lishin•2d ago•46 comments

Cleo (Mathematician)

https://en.wikipedia.org/wiki/Cleo_(mathematician)
102•djoldman•1d ago•11 comments

'Jonathan' is the oldest land animal on Earth

https://www.404media.co/oldest-living-land-animal-jonathan-the-tortoise/
109•gumby•9h ago•43 comments

In Vienna and Beijing, the first (thorium) nuclear clocks begin to tick

https://www.nytimes.com/2026/10/07/science/first-nuclear-clocks-thorium-229.html
64•gumby•11h ago•6 comments

Show HN: Bigwords.page – Turn any screen into a sign. The URL is the app

https://bigwords.page/
431•SpeakingOfBrad•13h ago•126 comments

GPT‑6 and Intelligent UI for everyone

https://openai.com/index/gpt-6-for-everyone/
567•joshuawright11•11h ago•296 comments

Shipping JPEG XL in Chrome

https://developer.chrome.com/blog/jpeg-xl-in-chrome
521•AshleysBrain•18h ago•351 comments

Docker Agent

https://github.com/docker/docker-agent
209•saikatsg•11h ago•97 comments

Push ifs up and fors down: The idiom, its algebra, and its limits

https://debasishg.github.io/blog/push-ifs-up-fors-down/
130•speckx•10h ago•61 comments

ENIAC Programmers (2011)

https://www.columbia.edu/cu/computinghistory/eniac.html
8•adunk•2d ago•0 comments

A minimal kernel in Swift, running in QEMU

https://carette.xyz/posts/minimal_swift_kernel_on_qemu/
52•surprisetalk•1d ago•9 comments

Sharing AI progress in mathematics

https://openai.com/index/sharing-ai-progress-in-mathematics/
1264•OfficialTurkey•1d ago•1432 comments

Navier–Stokes Lost in Translation

https://arxiv.org/abs/2610.08144
283•nill0•14h ago•174 comments

A new write and space optimized storage engine for MySQL is here

https://tidesdb.com/articles/tidesdb-now-available-for-mysql/
51•alexpadula•2d ago•21 comments

Animated ASCII Art for Web Pages

https://ascii.rest/
323•turrini•14h ago•60 comments

How machines learned precision

https://glinscott.github.io/how-machines-learned-precision/
133•glinscott•1d ago•60 comments

The 15-year search for a band that charted once and vanished

https://shahidhussain.com/writing/search-for-salvage/
7•shahidhussain•3d ago•3 comments

House with 15m underground tunnels for sale for 300k

https://www.readingchronicle.co.uk/news/26612080.house-15m-underground-tunnels-sale-300k/
186•librasteve•16h ago•169 comments

Brownian Motion

https://gregorygundersen.com/blog/2026/04/22/brownian-motion/
51•signa11•1d ago•4 comments

If somebody tries to hot-patch an already-hot-patched function

https://devblogs.microsoft.com/oldnewthing/20261005-00/?p=112755/
51•ibobev•1d ago•25 comments

Wood Tape (2004)

http://gamesbyemail.com/WoodTape/Default.htm
178•NaOH•2d ago•27 comments

Anti-patterns in software blogging

https://refactoringenglish.com/blog/anti-patterns-software-blogging/
239•ilreb•16h ago•129 comments

Google Playground: Create and play custom games

https://blog.google/innovation-and-ai/technology/ai/playground-experimental-gaming-platform/
133•acossta•17h ago•211 comments

Why were Victorian elites so effective?

https://worksinprogress.co/issue/the-seven-vices-of-highly-effective-victorians/
125•karakoram•14h ago•193 comments

Visa, Mastercard, major banks facing new litigation over 'anticompetitive' fees

https://www.classaction.org/news/visa-mastercard-major-banks-facing-new-litigation-over-anticompe...
529•DeepLogin•14h ago•382 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?