frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

ZCode: Claude Code from the Makers of GLM

https://zcode.z.ai/cn
107•handfuloflight•58m ago•30 comments

For first time, a cell built from scratch grows and divides

https://www.quantamagazine.org/for-the-first-time-a-cell-built-from-scratch-grows-and-divides-202...
554•defrost•5h ago•184 comments

What to Learn to Be a Graphics Programmer

https://blog.demofox.org/2026/07/01/what-to-learn-to-be-a-graphics-programmer/
105•atan2•2h ago•41 comments

FFmpeg 9.1's new AAC encoder

https://hydrogenaudio.org/index.php/topic,129691.0.html
151•ledoge•5h ago•60 comments

Physical disc production ending in Jan 2028 for new games on PlayStation

https://blog.playstation.com/2026/07/01/physical-disc-production-ending-in-january-2028-for-new-g...
405•Tiberium•7h ago•481 comments

Fable 5 Is Back

https://twitter.com/claudeai/status/2072402636813607381
98•mfiguiere•34m ago•53 comments

How We Made IPFS Content Publishing 10x Faster

https://probelab.io/blog/optimistic-provide/
109•dennis-tra•4h ago•29 comments

Box3D, an open source 3D physics engine

https://box2d.org/posts/2026/06/announcing-box3d/
325•makepanic•7h ago•71 comments

Ask HN: Who is hiring? (July 2026)

106•whoishiring•5h ago•120 comments

Monetization Gateway

https://blog.cloudflare.com/monetization-gateway/
181•soheilpro•6h ago•101 comments

Internal Combustion Engine

https://ciechanow.ski/internal-combustion-engine/
204•StefanBatory•7h ago•41 comments

Claude Fable 5 Promotional Access

https://support.claude.com/en/articles/15424964-claude-fable-5-promotional-access
14•zbikowski•38m ago•4 comments

Weave Robotics launches Isaac 1, a $7,999 home robot with fall 2026 deliveries

https://runtimewire.com/article/weave-robotics-isaac-1-home-robot-launch
17•ryanmerket•1h ago•29 comments

Understanding the Linux Kernel: The Scheduler

https://internals-for-interns.com/posts/linux-kernel-scheduler/
18•valyala•4d ago•5 comments

Hanami 3.0: In Full Bloom

https://hanakai.org/blog/2026/06/30/hanami-3-0-in-full-bloom
32•PuercoPop•2h ago•4 comments

Show HN: Z-Jail – A 130 KB Linux sandbox-C99 with 7 defense layers and zero deps

https://github.com/Division-36/Z-Jail/
8•Zierax•51m ago•3 comments

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

77•whoishiring•5h ago•173 comments

A complete ClickHouse OLAP engine, compiled to WebAssembly

https://wasm.chdb.io/
26•porridgeraisin•3h ago•3 comments

Mortality associated with non-optimal ambient temperatures from 2000 to 2019

https://www.researchgate.net/publication/353058947_Global_regional_and_national_burden_of_mortali...
17•simonebrunozzi•2h ago•0 comments

Manufact (YC S25) Is Hiring a Developer Advocate in SF

https://www.ycombinator.com/companies/manufact/jobs/4cyWd6S-developer-advocate-partnerships-devrel
1•luigipederzani•6h ago

1-Bit Pixel Art Emojis

https://hypertalking.com/2023/05/15/1-bit-pixel-art-emojis/
99•surprisetalk•6d ago•16 comments

Building Gin: Simple over Easy

https://manualmeida.dev/articles/gin-simple-over-easy/
45•manucorporat•2h ago•13 comments

Launch HN: Parsewise (YC P25) – Reason Across Documents with an API

39•gergelycsegzi•6h ago•35 comments

Fixing a kubelet memory leak in Kubernetes 1.36

https://heyoncall.com/blog/fixing-kubernetes-kubelet-memory-leak
52•compumike•17h ago•11 comments

Sony Deletes 551 Movies PlayStation Owners Paid For

https://reclaimthenet.org/sony-deletes-551-studiocanal-movies-playstation-owners-paid-for
353•bilsbie•5h ago•174 comments

Reduce GVisor Cold Starts with GPU Snapshotting

https://cerebrium.ai/blog/reducing-gpu-cold-starts-with-memory-snapshots-restoring-cuda-workloads...
39•jono_irwin•3h ago•15 comments

Asahi Linux 7.1 Progress Report

https://asahilinux.org/2026/06/progress-report-7-1/
490•pantalaimon•10h ago•176 comments

Apple 'Hide My Email' vulnerability reveals peoples' real email addresses

https://easyoptouts.com/guides/apple-hide-my-email-is-leaking-email-addresses
186•sashk•9h ago•39 comments

Newly discovered spider builds spring loaded snare to catch ants

https://phys.org/news/2026-06-newly-australian-ballista-spider-snare.html
227•chimpanzee•3d ago•58 comments

Show HN: QR code renderer in a TrueType font

https://qr.jim.sh/
49•foodevl•3d ago•10 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?