frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

LLMs reward expertise

https://www.seangoedecke.com/llms-reward-expertise/
355•MaxMussio•3h ago•157 comments

Ten advances in mathematics and theoretical computer science

https://openai.com/index/ten-advances-in-mathematics/
398•milkshakes•8h ago•681 comments

Devtools must be open source

https://blog.exe.dev/devtools-must-be-open-source
484•bryanmikaelian•10h ago•175 comments

Windows XP 2002 for the Itanium: Unbridled rage

https://virtuallyfun.com/2026/08/03/windows-xp-2002-for-the-itanium-unbridled-rage/
41•jandeboevrie•2h ago•10 comments

Ask HN: Who is hiring? (August 2026)

77•whoishiring•9h ago•89 comments

Ask HN: Who wants to be hired? (August 2026)

39•whoishiring•9h ago•151 comments

Smaller, faster, safer: running Kimi and GLM at scale

https://blog.cloudflare.com/smaller-faster-safer-models/
135•ascorbic•7h ago•35 comments

MiniMax H3 Day-0 Support in ComfyUI: Open Weights, Native Audio, and 2K Video

https://blog.comfy.org/p/minimax-h3-day-0-support-in-comfyui
245•vblanco•10h ago•76 comments

Celebrating 45 Years of Kermit with the First New C-Kermit Release in 15 Years

https://changelog.complete.org/archives/44456-celebrating-45-years-of-kermit-with-the-first-new-c...
121•roryirvine•7h ago•33 comments

Prevent cognitive debt by manually retyping LLM-generated code

https://ankursethi.com/blog/prevent-cognitive-debt-by-manually-retyping-llm-generated-code/
371•mpweiher•15h ago•309 comments

Battle of the Beams

https://en.wikipedia.org/wiki/Battle_of_the_Beams
25•petethomas•2d ago•5 comments

200 Milliseconds

https://200ms.thenodebook.com
174•dimitarpanov•2d ago•56 comments

Andy Pavlo joins ClickHouse to establish ClickHouse Labs

https://clickhouse.com/blog/andy-pavlo-joins-clickhouse
264•nikolay_sivko•10h ago•55 comments

Replacing the Kobo Libra H2O Battery

https://ei3lh.eu/2025/11/20/replacing-the-kobo-libra-h2o-battery/
43•austinallegro•4d ago•11 comments

ZX Spectrum System Tour: Text Mode

https://bumbershootsoft.wordpress.com/2026/05/30/zx-spectrum-system-tour-text-mode/
14•rbanffy•2h ago•0 comments

Launch HN: Hoplite (YC S26) – Effortlessly deploy cloud coding agents

https://hoplite.sh
53•BenceRed•8h ago•50 comments

How Hollywood stopped making movies in Hollywood

https://www.statsignificant.com/p/how-hollywood-stopped-making-movies
163•speckx•6d ago•183 comments

The Dunning-Kruger effect may just be a data artefact (2020)

https://www.mcgill.ca/oss/article/critical-thinking/dunning-kruger-effect-probably-not-real
111•audreyfei•4h ago•116 comments

AirLLM 70B inference with single 4GB GPU

https://github.com/lyogavin/airllm
184•Anon84•13h ago•73 comments

KisakCOD – open-source reimplementation of Call of Duty 4 Multiplayer

https://github.com/SwagSoftware/KisakCOD
34•skibz•5h ago•3 comments

Bonsai: Janestreet's UI Library

https://github.com/janestreet/bonsai
296•KolmogorovComp•16h ago•114 comments

They Forgot What Happened Last Time: Hacking the Windows 365 Link [video]

https://media.ccc.de/v/emf2026-93-1-they-forgot-what-happened-last-time
4•Jimmc414•3d ago•0 comments

Decades-old fish sauce at abandoned factory in Canada finally being removed

https://defector.com/abandoned-fish-sauce-canada-interview
191•ohjeez•3d ago•198 comments

Massively Parallel Postgres Backups

https://planetscale.com/blog/massively-parallel-postgres-backups
85•ksec•3d ago•11 comments

Twenty Years of Pandoc

https://pandoc.org/twenty-years-of-pandoc.html
89•fiddlosopher•9h ago•11 comments

Kelly Criterion Simulator

https://kellysimulator.com/
53•aleyan•3d ago•24 comments

The Billable Usage API: programmatic cost visibility for Cloudflare

https://blog.cloudflare.com/billable-usage-api/
42•ashleypeacock•7h ago•6 comments

What's the largest software project AI can complete on its own?

https://epoch.ai/MirrorCode
64•yusufozkan•8h ago•71 comments

ZX Spectrum System Tour: Sound

https://bumbershootsoft.wordpress.com/2026/08/01/zx-spectrum-system-tour-sound/
29•ibobev•6h ago•7 comments

Use Task Runners for Common Coding Tasks

https://hamvocke.com/blog/task-runners/
66•speckx•7h ago•24 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?