frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Devtools must be open source

https://blog.exe.dev/devtools-must-be-open-source
239•bryanmikaelian•3h ago•75 comments

Ten advances in mathematics and theoretical computer science

https://openai.com/index/ten-advances-in-mathematics/
50•milkshakes•1h ago•365 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
166•vblanco•4h ago•49 comments

Wind and solar overtake fossil fuels in Germany for the first time

https://www.intellinews.com/wind-and-solar-overtake-fossil-fuels-in-germany-for-the-first-time-ev...
134•just_some_user•4h ago•54 comments

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

https://hoplite.sh
18•BenceRed•1h ago•16 comments

Andy Pavlo joins ClickHouse to establish ClickHouse Labs

https://clickhouse.com/blog/andy-pavlo-joins-clickhouse
138•nikolay_sivko•3h ago•27 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...
18•roryirvine•54m ago•4 comments

How Hollywood stopped making movies in Hollywood

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

Qwen3.8-Max: A New Bar for Coding and Cowork

https://qwen.ai/blog?id=qwen3.8
957•ai2027•15h ago•491 comments

Show HN: Product analytics (and evals) for agent sessions on your MCP

https://armature.tech/
15•screm•1h ago•0 comments

AirLLM 70B inference with single 4GB GPU

https://github.com/lyogavin/airllm
134•Anon84•6h ago•46 comments

Bonsai: Janestreet's UI Library

https://github.com/janestreet/bonsai
229•KolmogorovComp•9h ago•84 comments

C++ float-to-int conversion can be undefined behavior

https://kttnr.net/blog/cpp-float-to-int-conversion-undefined-behavior/
18•signa11•4d ago•17 comments

SQLite Critical CVEs or LLM Slop?

https://research.jfrog.com/post/sqlite-critical-cves-or-llm-slops/
638•ymir_e•6h ago•266 comments

SPF Record Syntax: Mechanisms, Qualifiers, Modifiers, and Macros

https://dmarcguard.io/blog/spf-record-syntax/
30•meysamazad•4h ago•7 comments

Taylor Farms has rewritten its cyclospora statement four times in sixteen days

https://www.marlerblog.com/case-news/taylor-farms-has-rewritten-its-cyclospora-statement-four-tim...
210•speckx•2h ago•120 comments

Don't be a meat proxy

https://gruhn.me/blog/2026-08-03/
1463•ngruhn•11h ago•622 comments

Explanation of INT8 ConvRot (FP8 is no longer needed)

https://note.com/hirorohi03/n/n047a8c5f7f8b?hl=en
10•peter_d_sherman•1h ago•4 comments

Massively Parallel Postgres Backups

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

SearXNG in Rust

https://github.com/MikeLuu99/searxng-rust
8•dluuuu•1h ago•2 comments

Show HN: Nightcrawler – A local AI pentesting agent running on a smartphone

https://github.com/garagehq/nightcrawler/
85•NickySlicks•6h ago•23 comments

What DMARC Protects You From, and What It Does Not

https://senderledger.com/articles/what-dmarc-actually-protects-you-from
97•adulion•8h ago•25 comments

Rust project goals: Immobile types and guaranteed destructors

https://github.com/rust-lang/rust-project-goals/blob/main/src/2026/move-trait.md
191•paavohtl•11h ago•72 comments

Kraid is a now a real compiler

https://www.collabora.com/news-and-blog/news-and-events/kraid-is-a-now-a-real-compiler.html
15•losgehts•4d ago•4 comments

Prevent cognitive debt by manually retyping LLM-generated code

https://ankursethi.com/blog/prevent-cognitive-debt-by-manually-retyping-llm-generated-code/
290•mpweiher•8h ago•256 comments

Games at the press of a button: The Rip-O-Bot (1989)

https://blog.gingerbeardman.com/2026/08/02/games-at-the-press-of-a-button-the-rip-o-bot/
25•msephton•21h ago•5 comments

Help Wanted

https://lake.computer/blog/help-wanted/
5•whwhyb•1h ago•0 comments

Octane – React’s programming model, compiled

https://octanejs.dev
112•nnx•9h ago•37 comments

Walk on Decomposed Subdomains

https://clementjambon.github.io/wods/index.html#blogpost
32•E-Reverance•6d ago•2 comments

Train Simulator Controller

https://z80.me/blog/tsc-2026-july/
82•austinallegro•3d ago•5 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?