frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Hurried Announcement: Alessandro Masullo GRH

https://math216.wordpress.com/2026/11/20/hurried-announcement-alessandro-masullo-grh/
1594•jasondavies•7h ago•723 comments

Inkling 2 Mini

https://thinkingmachines.ai/news/inkling-2-mini/
696•jasondavies•6h ago•115 comments

Levent Alpöge claims proof of the Generalized Riemann Hypothesis [pdf]

https://alpo.ge/remark.pdf
2383•iamronaldo•11h ago•1609 comments

NINLIVE: The Nine Inch Nails live archive

https://ninlive.com/
134•CharlesW•3h ago•27 comments

We promoted developers into architects without informing them

https://manidoraisamy.com/developer-to-architect.html
310•QueensGambit•7h ago•188 comments

Valkey kills the skiplist, cuts sorted set overhead by up to 43%

https://valkey.io/blog/from-skiplist-to-b+tree/
39•reconditerose•3d ago•20 comments

Unforced Navier-Stokes Singularity and the Generalized Riemann Hypothesis

https://terrytao.wordpress.com/2026/11/20/unforced-euler-singularity-unforced-navier-stokes-singu...
349•archon1410•8h ago•142 comments

Language Models Can Rewrite Their Own Weights

https://arxiv.org/abs/2611.21885
343•lwhsiao•9h ago•112 comments

Sir Brian May adds new dimension to Hera asteroid

https://www.esa.int/articles/about-us/directorates/operations/space-safety/hera/sir-brian-may-add...
39•mooreds•2h ago•8 comments

DreamCoder: Coding harness and IDE from the author of Mastering Emacs

https://www.masteringemacs.org/article/announcing-dreamcoder
112•facundo_olano•6h ago•17 comments

Finite-time blow-up for the Navier–Stokes equations

https://github.com/tristanbuckmaster/navier-stokes/
260•trotro•10h ago•82 comments

If you can't explain something in simple terms, you don't understand it (2017)

https://kottke.org/17/06/if-you-cant-explain-something-in-simple-terms-you-dont-understand-it
629•sammatilda•16h ago•293 comments

And yet, it moves

https://signoregalilei.com/2026/11/20/and-yet-it-moves/
92•notfried•6h ago•45 comments

Re: Riemann

https://borretti.me/article/re-riemann
123•_dain_•2h ago•110 comments

Vibecoding an inference chip

https://ankitg.me/blog/vibecoding-inference-chip/
117•ankitvgupta•7h ago•41 comments

The stochastic parrots have apparently proved the Riemann Hypothesis

https://scottaaronson.blog/?p=10344
221•stratos123•6h ago•192 comments

Restricting AI agents in mobile operating systems platforms from capturing data

https://signal.org/blog/protecting-your-privacy/
512•dotcoma•16h ago•306 comments

Winedroid – run Android apps without Android (WASM demo)

https://winedroid.soham.sh/demo/
105•sohzm•6h ago•31 comments

The Hungry Butler Effect: Concealed Commercial Incentives in LLMs

https://www.researchgate.net/publication/418143113_The_Hungry_Butler_Effect_Concealed_Commercial_...
18•undefinedmethod•3h ago•8 comments

Forking TuxGuitar into a 17-EDO tab editor

https://frogwizard.bearblog.dev/tuxguitar-17edo/
6•speckx•2d ago•4 comments

Why the Airbus A321XLR often gets stuck climbing for first few hours of flight

https://simpleflying.com/airbus-a321xlr-often-stuck-climbing-1st-few-hours-flight/
88•edward•6d ago•58 comments

Show HN: OpenComputer – an open source alternative to Devin

https://github.com/diggerhq/opencomputer
69•iacguy•5h ago•22 comments

US SEC's Nvidia probe is examining potential accounting issues – sources

https://www.marketscreener.com/news/us-sec-s-nvidia-probe-is-examining-potential-accounting-issue...
228•ftchd•5h ago•117 comments

I can’t believe it’s 1!

https://aperiodical.com/2026/11/i-cant-believe-its-1/
46•ColinWright•4d ago•54 comments

Show HN: I made an audio-to-MIDI model 60x more efficient

https://kobi.music/research/dettato
243•hidude562•4d ago•51 comments

Integrals of Polynomials with Galois Group S_p

https://m-slee.netlify.app/posts/integrals-galois-polynomials
3•richard_chase•57m ago•1 comments

I'm Peter Roberts, immigration attorney who does work for YC and startups. AMA

96•proberts•9h ago•132 comments

Merkle Tree Certificates

https://datatracker.ietf.org/doc/draft-ietf-plants-merkle-tree-certs/
14•mooreds•3h ago•2 comments

Show HN: An API for word timestamps from speech, 75% within 20ms

https://quebec.yarn.so
64•jasperstory•3d ago•10 comments

Replacing implicit optionals with a None type in TypeDB

https://typedb.com/blog/replacing-implicit-optionals-with-a-none-type-in-typedb
8•flyingsilverfin•3d 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?