frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

John Deere owners will get the right to repair equipment under FTC settlement

https://apnews.com/article/john-deere-right-to-repair-agriculture-equipment-cb7514ffedb95c130a976...
542•djoldman•5h ago•109 comments

Chatto is now open source

https://www.hmans.dev/blog/chatto-is-open-source
842•speckx•13h ago•219 comments

Separating signal from noise in coding evaluations

https://openai.com/index/separating-signal-from-noise-coding-evaluations/
190•sk4rekr0w•8h ago•68 comments

Cloudflare Drop

https://www.cloudflare.com/drop/
341•coloneltcb•9h ago•166 comments

Mistral's Robostral Navigate: a state of the art robotics navigation model

https://mistral.ai/news/robostral-navigate/
446•ottomengis•15h ago•96 comments

Patching MechCommander's "left arm bug" for fun and profit

https://mhloppy.com/2026/05/mechcommander-weapons-left-arm-bug-fix/
39•Narann•3d ago•12 comments

Show HN: Microsoft releases Flint, a visualization language for AI agents

https://microsoft.github.io/flint-chart/#/
237•chenglong-hn•11h ago•96 comments

Benchmarking coding agents on Databricks' multi-million line codebase

https://www.databricks.com/blog/benchmarking-coding-agents-databricks-multi-million-line-codebase
34•tanelpoder•7h ago•9 comments

Show HN: Yamanote.fun – A complete soundscape for Tokyo's Yamanote line

https://www.yamanote.fun/
104•madebymagnolia•1d ago•21 comments

Cargo-nextest: 3x faster than cargo test, per-test isolation, first-class CI

https://nexte.st/
20•nateb2022•3d ago•3 comments

Unicode's transliteration rules are Turing-complete

https://seriot.ch/computation/uts35/
63•beefburger•19h ago•21 comments

Grok 4.5

https://x.ai/news/grok-4-5
535•BoumTAC•11h ago•716 comments

What's slowing down the AI buildout

https://www.worksinprogress.news/p/ai-is-bottlenecked-by-the-grid
7•droidjj•1h ago•1 comments

I think I have LLM burnout

https://www.alecscollon.com/blog/llm-burnout/
241•sosodev•3h ago•178 comments

Turning a pile of documents into a searchable useable knowledge base

https://github.com/linuxrebel/DocuBrowser
105•linuxrebe1•8h ago•23 comments

Rewriting Bun in Rust

https://bun.com/blog/bun-in-rust
410•afturner•7h ago•210 comments

Apache Shiro security framework releases 3.0.0

https://shiro.apache.org/blog/2026/06/apache-shiro-300-released.html
15•lprimak•2d ago•0 comments

GPT‑Live

https://openai.com/index/introducing-gpt-live/
650•logickkk1•12h ago•426 comments

We made Grok 4.5, GPT-5.5, and Claude build the same apps

https://www.tryai.dev/blog/grok-4.5-vs-gpt-5.5-vs-claude-build-off
118•hershyb_•5h ago•58 comments

FAANG Simulator

https://www.abeyk.com/escape-the-rat-race/
354•nerdbiscuits•9h ago•137 comments

Decoding the obfuscated bash script on a Uniqlo t-shirt

https://tris.sherliker.net/blog/obfuscated-self-evaluating-bash-script-by-cdn-akamai-being-suppli...
1336•speerer•20h ago•210 comments

New Sweden: the US's long-lost 'secret' colony

https://www.bbc.com/travel/article/20260629-new-sweden-the-uss-long-lost-secret-colony
76•bookofjoe•9h ago•28 comments

TypeScript 7

https://devblogs.microsoft.com/typescript/announcing-typescript-7-0/
522•DanRosenwasser•13h ago•207 comments

MIRA: Multiplayer Interactive World Models Trained on Rocket League

https://mira-wm.com/
48•ethanlipson•4h ago•9 comments

A bug which affected only left handed users

https://shkspr.mobi/blog/2026/07/a-bug-which-only-affected-left-handed-users/
101•sixhobbits•15h ago•54 comments

Ergo: Long Form Philosophy Lectures

https://ergo.org/
6•agnishom•2h ago•0 comments

Cloudflare Meerkat - Globally distributed consensus

https://blog.cloudflare.com/meerkat-introduction/
238•bobnamob•16h ago•47 comments

My road trip with the do-gooding cactus smugglers

https://economist.com/1843/2026/03/06/my-road-trip-with-the-do-gooding-cactus-smugglers
30•andsoitis•3d ago•1 comments

OpenMandriva: Statement regarding attempted distribution sabotage

https://forum.openmandriva.org/t/statement-regarding-attempted-distribution-sabotage/8997
88•workethics•10h ago•16 comments

Beyond Git: Real-Time Version Control for Godot – Lilith Duncan – GodotCon 2026 [video]

https://www.youtube.com/watch?v=CAJ_iIedx_I
30•surprisetalk•6d ago•1 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?