frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

AI handles incidents, engineers lose touch with their systems

https://www.sylvainkalache.com/blog/ai-handles-incidents-engineers-lose-touch-with-their-systems
45•sylvainkalache•1h ago•24 comments

Actively exploited sandbox RCE in all Chromium versions

https://nvd.nist.gov/vuln/detail/cve-2026-85046
485•negura•11h ago•269 comments

Discovery of a new OpenAI agent message board

https://collusion.wiki/
1700•moultano•21h ago•1312 comments

Formalizing Fermat's Last Theorem

https://www.anthropic.com/research/formalizing-fermats-last-theorem
610•jlebar•14h ago•383 comments

Nitter has more working instances than before the takedowns

https://codeberg.org/mv12star/shitter/wiki/Instances
204•Cider9986•9h ago•70 comments

Things I Won't Work With: Straight Dimethyl Zinc

https://www.science.org/content/blog-post/things-i-won-t-work-straight-dimethyl-zinc
14•Bluestein•4d ago•0 comments

Statichost.eu – European static site hosting

https://www.statichost.eu/
279•p4bl0•12h ago•107 comments

GPT-6 Astra on OpenRouter

https://openrouter.ai/openai/gpt-6-astra
217•Topfi•11h ago•128 comments

GPT-6 Astra in code review: Gains, privacy, and cost

https://www.coderabbit.ai/blog/gpt-6-astra-code-review-evaluation
40•cebert•5h ago•22 comments

Can AI design circuit boards yet?

https://eebench.org/blog/can-ai-design-circuit-boards-yet/
256•iopapa•13h ago•151 comments

Shutting down our public encrypted DNS

https://mullvad.net/en/blog/shutting-down-our-public-encrypted-dns-servers-and-sponsoring-quad9-i...
340•mywacaday•14h ago•155 comments

Git Submodules as a Package Manager

https://nesbitt.io/2026/09/01/git-submodules-as-a-package-manager.html
55•ErenayDev•3d ago•6 comments

Portal by Spotify cut my Claude Code token usage by 90%

https://engineering.atspotify.com/2026/9/portal-by-spotify-cut-my-claude-code-token-usage-by-90
126•cebert•9h ago•57 comments

Artificial Analysis Intelligence Index v4.2

https://artificialanalysis.ai/articles/artificial-analysis-intelligence-index-v4-2
116•nojs•9h ago•41 comments

Show HN: Open-Source eInk Bike Computer

https://opentrailpaper.com
285•stingrae•15h ago•102 comments

Can guitar frets perform multiplication?

https://www.charlespetzold.com/blog/2026/09/Can-Guitar-Frets-Perform-Multiplication.html
75•wibbily•10h ago•19 comments

Ask HN: Resources to get good at soldering?

125•tosmatos•2d ago•74 comments

Pointing at the error: compiler-style diagnostics in uutils coreutils

https://uutils.org/blog/2026-08-error-diagnostics/
9•ingve•2d ago•1 comments

The Highest Point in the Netherlands

https://ipv6.hanazo.no/posts/anniversary-personal/
49•haasted•2d ago•34 comments

IBM Bob

https://bob.ibm.com/
268•artpar•20h ago•287 comments

Git hosting that never leaves Europe

https://pushin.eu
65•sevenseacat•2h ago•46 comments

An open DNS recursive service for free security and high privacy

https://quad9.net/
88•mooreds•12h ago•25 comments

RSA-260 Factorized

https://twitter.com/penlume/status/2095372672356212876
114•samyok•2d ago•59 comments

Fermat's Last Theorem in Lean 4

https://github.com/anthropics/fermats-last-theorem
106•aaraujo002•14h ago•20 comments

The Rust React Compiler is now native in Vite

https://blog.master.dev/react-now-rusted-all-the-way-out/
137•acusti•15h ago•31 comments

Government Rails Site Hit Hours After CVE Patch

https://rietta.com/blog/ruby-on-rails-cve-exploited-hours-after-patch/
93•rietta•14h ago•29 comments

Decompiler Explorer

https://dogbolt.org
84•tripdout•3d ago•5 comments

Show HN: TERMy – A fast terminal assistant that does not use LLMs

https://github.com/gioblu/NPC-Forge/blob/main/docs/development.md
128•gioscarab•1d ago•35 comments

Record-High 89% in U.S. Say Government Corruption Widespread

https://news.gallup.com/poll/713933/record-high-say-government-corruption-widespread.aspx
411•karakoram•11h ago•317 comments

Icons as a Service

https://nravic.com/blog/images/
44•nravic•11h 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?