frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Actively exploited sandbox RCE in all Chromium versions

https://nvd.nist.gov/vuln/detail/cve-2026-85046
278•negura•5h ago•156 comments

Formalizing Fermat's Last Theorem

https://www.anthropic.com/research/formalizing-fermats-last-theorem
515•jlebar•8h ago•324 comments

Discovery of a new OpenAI agent message board

https://collusion.wiki/
1511•moultano•15h ago•1202 comments

Artificial Analysis Intelligence Index v4.2

https://artificialanalysis.ai/articles/artificial-analysis-intelligence-index-v4-2
58•nojs•2h ago•16 comments

Statichost.eu – European static site hosting

https://www.statichost.eu/
180•p4bl0•6h ago•61 comments

GPT-6 Astra on OpenRouter

https://openrouter.ai/openai/gpt-6-astra
136•Topfi•5h ago•72 comments

Shutting down our public encrypted DNS

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

Can AI design circuit boards yet?

https://eebench.org/blog/can-ai-design-circuit-boards-yet/
180•iopapa•7h ago•116 comments

Can guitar frets perform multiplication?

https://www.charlespetzold.com/blog/2026/09/Can-Guitar-Frets-Perform-Multiplication.html
40•wibbily•4h ago•10 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
44•cebert•3h ago•17 comments

RSA-260 Factorized

https://twitter.com/penlume/status/2095372672356212876
69•samyok•1d ago•31 comments

Show HN: Open-Source eInk Bike Computer

https://opentrailpaper.com
241•stingrae•9h ago•84 comments

Git Submodules as a Package Manager

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

An open DNS recursive service for free security and high privacy

https://quad9.net/
67•mooreds•6h ago•14 comments

Fermat's Last Theorem in Lean 4

https://github.com/anthropics/fermats-last-theorem
72•aaraujo002•7h ago•15 comments

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

https://news.gallup.com/poll/713933/record-high-say-government-corruption-widespread.aspx
228•karakoram•4h ago•164 comments

Government Rails Site Hit Hours After CVE Patch

https://rietta.com/blog/ruby-on-rails-cve-exploited-hours-after-patch/
76•rietta•7h ago•24 comments

ExactTex. A gradually-typed superset of LaTeX

https://github.com/camilochs/exacttex
19•camilochs•3d ago•1 comments

When declaring an incident becomes everyone's favorite workaround

https://greatcircle.com/blog/2026/08/11/declaring-incidents-for-side-effects/
15•bobbiechen•4d ago•5 comments

Show HN: Moadim.io – A scheduler for agents

https://moadim.io/
16•tupe12334•3h ago•8 comments

Icons as a Service

https://nravic.com/blog/images/
27•nravic•5h ago•2 comments

The Rust React Compiler is now native in Vite

https://blog.master.dev/react-now-rusted-all-the-way-out/
117•acusti•9h ago•22 comments

Connecting every app to every other app

https://blog.val.town/connectors
16•Chidiebere229•3h ago•1 comments

IBM Bob

https://bob.ibm.com/
233•artpar•14h ago•269 comments

Decompiler Explorer

https://dogbolt.org
40•tripdout•3d ago•1 comments

deSEC – Free Secure DNS

https://desec.io/
116•gurjeet•11h ago•41 comments

How to Create a Tor Exit Node (2015)

https://madpsy.uk/how-to-create-a-tor-exit-node/
44•Eridanus2•6h ago•19 comments

Updates on HEIR, the Homomorphic Encryption Compiler Project

https://www.jeremykun.com/2026/09/04/updates-on-heir-homomorphic-encryption/
25•turtleyacht•5h ago•0 comments

“Next-token predictor” is the wrong mental model for LLMs

https://gmcgoldr.github.io/2026/09/04/llm-next-token-predictors.html
91•garrinm•9h ago•193 comments

Adult Film Producer Unmasks Prolific 'John DOE' Torrent Pirate as Meta Executive

https://torrentfreak.com/adult-film-producer-unmasks-prolific-john-doe-torrent-pirate-as-meta-exe...
359•speckx•10h ago•212 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?