frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Flux 3 X Mimic: The Next Generation of Video-Action Models

https://bfl.ai/blog/flux-3-mimic
76•kensai•1h ago•6 comments

Flux 3

https://bfl.ai/blog/flux-3
329•ThouYS•4h ago•84 comments

It's getting harder to focus every day

https://glyphack.com/attention/
102•peykar•2h ago•47 comments

Writing by hand is good for your brain

https://nealstephenson.substack.com/p/writing-by-hand-is-good-for-your
1338•dwwoelfel•20h ago•609 comments

Startup founders urge U.S. government not to shut off Chinese open weight AI

https://www.politico.com/news/2026/07/22/startup-founders-urge-trump-not-to-shut-off-chinese-open...
963•theanonymousone•19h ago•785 comments

Claude Cookbook

https://platform.claude.com/cookbook/
85•saikatsg•6h ago•32 comments

The Beam Engine

https://glinscott.github.io/beam-engine/
408•glinscott•1d ago•80 comments

Show HN: Echo – Fable-level results at 1/3 the cost using open-weight models

397•adam_rida•15h ago•190 comments

Buz – A fork of Bun using modern Zig, with sub-1s incremental builds

https://ziggit.dev/t/buz-a-drop-in-replacement-for-bun-using-modern-zig-with-sub-1s-incremental-b...
6•kristoff_it•1h ago•0 comments

The Book Prize Index

https://book-prize-index.vercel.app
12•Luc•2h ago•0 comments

Computational chemistry, Locally? My rant on SSH

https://chillphysicsenjoyer.substack.com/p/computational-chemistry-locally
8•crescit_eundo•2d ago•3 comments

The day Steve Jobs dissed me in a keynote (2010)

https://sive.rs/itunes
68•downbad_•2h ago•11 comments

The PImpl idiom and the C++26 std:indirect type

https://mariusbancila.ro/blog/2026/07/23/the-pimpl-idiom-and-the-cpp26-stdindirect-type/
54•signa11•4h ago•47 comments

AMD's Instinct MI455X: Aiming for the Sun

https://chipsandcheese.com/p/amds-instinct-mi455x-aiming-for-the
18•ingve•4h ago•2 comments

What happened to TheNumbers.com

https://stephenfollows.com/p/what-just-happened-to-thenumberscom-should-worry-us-all
383•nickthegreek•18h ago•180 comments

Why Software Factories Fail (or: harness engineering is not enough)

https://github.com/humanlayer/advanced-context-engineering-for-coding-agents/blob/main/wsff.md
334•dhorthy•19h ago•238 comments

What else do people draw on gradient.horse?

https://rybakov.com/blog/what_else_do_people_draw_on_gradient-copy.horse/
141•spython•5d ago•26 comments

I regret migrating to Codeberg

https://xn--gckvb8fzb.com/i-regret-migrating-to-codeberg/
338•boramalper•21h ago•236 comments

Learn OpenGL, extensive tutorial resource for learning Modern OpenGL

https://learnopengl.com/
252•ibobev•20h ago•128 comments

Future euro banknote design proposals

https://www.ecb.europa.eu/euro/banknotes/future_banknotes/html/design-proposals.en.html
57•robin_reala•1h ago•51 comments

DARPA, U.S. Air Force fly AI-controlled F-16

https://www.darpa.mil/news/2026/darpa-us-air-force-fly-ai-controlled-f-16
253•r2sk5t•21h ago•280 comments

Why Sony can't bring back its classic Walkman models

https://obsoletesony.substack.com/p/why-sony-cant-bring-back-classic-walkman
141•speckx•17h ago•153 comments

Software rendering in 500 lines of bare C++

https://haqr.eu/tinyrenderer/
286•mpweiher•20h ago•65 comments

Projects every RC live races and results

https://rc-replay.dev/lr/vmrc/r/6912053
14•apokly•3d ago•0 comments

Hetzner is working on LLM Inference

https://sliplane.io/blog/hetzner-inference
19•jonas_scholz•1h ago•5 comments

Quickly rewrite Git repository history

https://github.com/newren/git-filter-repo
51•modinfo•3d ago•3 comments

98.css

https://jdan.github.io/98.css/#status-bar
482•lopespm•12h ago•109 comments

Show HN: Palmier Pro – Open-source macOS video editor built for AI

https://github.com/palmier-io/palmier-pro
166•harrisontin•20h ago•26 comments

Fields Medals 2026

https://www.mathunion.org/imu-awards/fields-medal/fields-medals-2026
191•nill0•20h ago•95 comments

I could do that in a weekend (2016)

https://danluu.com/sounds-easy/
9•ntumlin•3d ago•0 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?