frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Kimi-K3 Releases on HuggingFace 7/27

https://huggingface.co/moonshotai/Kimi-K3
620•nateb2022•7h ago•283 comments

Should you wash your solar panels?

https://incoherency.co.uk/blog/stories/should-you-wash-your-solar-panels.html
30•surprisetalk•59m ago•14 comments

AI companies are shredding rare books

https://xcancel.com/HedgieMarkets/status/2081534588485296565
257•anon373839•1h ago•147 comments

How is the Bun Rewrite in Rust going?

https://lockwood.dev/ai/2026/07/27/how-is-the-bun-rewrite-in-rust-going.html
207•tomlockwood•2h ago•140 comments

Removing React.js from the codebase and adapting Htmx for UI interactivity

https://misago-project.org/t/removing-reactjs-from-the-codebase-and-adapting-htmx-for-ui-interact...
59•Ralfp•4h ago•33 comments

Libsm64: Mario 64 as a library for use in external game engines

https://github.com/libsm64/libsm64
59•klaussilveira•3h ago•10 comments

PGSimCity - How PostgreSQL Works

https://nikolays.github.io/PGSimCity/
750•jonbaer•13h ago•70 comments

Magnolias Are So Old That They're Pollinated by Beetles, Not Bees

https://mymodernmet.com/magnolia-ancient-flowers-beetles/
144•speckx•4d ago•57 comments

Building a Fast Lock-Free Queue in Modern C++ from Scratch

https://blog.jaysmito.dev/blog/04-fast-lockfree-queues/
33•ibobev•4d ago•10 comments

Show HN: Physically accurate black hole you can put in your room

https://blackhole.plav.in
396•aplavin•4d ago•132 comments

Towards a Theory of Bugs: The Ruliology of the Unexpected

https://writings.stephenwolfram.com/2026/07/towards-a-theory-of-bugs-the-ruliology-of-the-unexpec...
20•nsoonhui•3d ago•2 comments

VLC for Unity now supported on Linux

https://code.videolan.org/videolan/vlc-unity
62•martz•4h ago•18 comments

The Birth of the American 12-string Guitar

https://www.harpguitars.net/history/grunewald/12-string.htm
37•bilegeek•3h ago•16 comments

Elevated errors on Claude Opus 5

https://status.claude.com/incidents/mfdtrknpxghq
42•croemer•2h ago•43 comments

Modern email can be built from borrowed parts

https://en.andros.dev/blog/d7ed8b07/modern-email-can-be-built-from-borrowed-parts/
56•andros•5h ago•18 comments

Shay Locomotives

https://www.shaylocomotives.com/
29•Rygian•4h ago•6 comments

The Proof Machine (2016)

https://incredible.pm/
11•BenoitP•1h ago•0 comments

Scriptc by Vercel: TypeScript-to-Native compiler, no JavaScript engine in binary

https://github.com/vercel-labs/scriptc
227•maxloh•15h ago•114 comments

Worse on Purpose

https://ledger.worseonpurpose.com/brands
57•bookofjoe•1h ago•24 comments

Decker, a platform that builds on the legacy of Hypercard and classic macOS

https://beyondloom.com/decker/
340•tosh•19h ago•77 comments

Elevated errors on Claude Opus 5

https://status.claude.com/incidents/lhqp09kxq7pb
35•flyaway123•5h ago•21 comments

First Robotic Satellite Servicer Launched

https://www.nrl.navy.mil/Media/News/Article/4551871/robotic-servicing-of-geosynchronous-satellite...
8•GlenTheMachine•3d ago•0 comments

US citizen charged after GrapheneOS phone wipes during airport search

https://www.techspot.com/news/113236-us-prosecutors-charge-atlanta-man-after-grapheneos-phone.html
983•eecc•15h ago•755 comments

Google Chrome Arrives on ARM64 Linux, Widevine DRM Included

https://www.omgubuntu.co.uk/2026/07/chrome-arm64-linux-available
28•twapi•2h ago•7 comments

We have proof automation now

https://www.imperialviolet.org/2026/07/26/zstd-lean.html
201•zdw•17h ago•83 comments

I wanted a clock that never needed setting. Things escalated

https://arstechnica.com/gadgets/2026/07/i-wanted-a-clock-that-never-needed-setting-things-escalated/
143•lee_ars•4d ago•123 comments

Measuring developer productivity with the DX Core 4

https://getdx.com/research/measuring-developer-productivity-with-the-dx-core-4/
35•saikatsg•3d ago•27 comments

Introduction to Data-Oriented Design [pdf]

https://www.gamedevs.org/uploads/introduction-to-data-oriented-design.pdf
206•tosh•19h ago•53 comments

8086 Emulator Inside Scratch

https://turbowarp.org/1248315967?size=640x400
19•rickcarlino•4d ago•1 comments

Chinese chipmaker shares surge 470%

https://www.bbc.com/news/articles/c9q9w3x9qn2o
135•pingou•4h ago•122 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?