frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Codeberg.org Not Reachable

https://social.anoxinon.de/@codebergstatus/117636437840688845
133•hans_castorp•1h ago•68 comments

Java4Shell: RCE in OpenJDK when processing Base64

https://calif.io/java4shell/
964•werrett•14h ago•246 comments

Google's AI answers reducing search traffic by 40%

https://revscope.co/blog/search-seo-geo-2026/
425•slashdev•11h ago•311 comments

ID.me terms required for IRS sign-in

https://consumerrights.wiki/w/ID.me_terms_required_for_IRS_sign-in
371•DeepLogin•10h ago•166 comments

Quad9's withdrawal from France: A canary in the coal mine

https://blog.cloudflare.com/quad9-withdrawal-from-france/
634•subset•13h ago•221 comments

Energy-Based Reasoners: 385x more efficient inference

https://energy-based-reasoners.github.io/
19•frenchmajesty•1h ago•2 comments

Nvidia stopped disclosing Singapore sales as revenues hit $104B

https://www.ft.com/content/dbde7a30-548c-4f9d-a4be-7898a0c24dcf
558•louiereederson•18h ago•249 comments

Why is Gemini 4 Carbon taking so long?

https://kernel.dev/blog/why-is-gemini-4-carbon-taking-so-long/
110•deenadz•7h ago•54 comments

Talos Linux

https://www.siderolabs.com/talos-linux
48•SweetSoftPillow•3h ago•22 comments

Microsoft's ONNX Runtime has disappeared from GitHub

https://github.com/microsoft/onnxruntime
340•nvader•12h ago•73 comments

Highly classified US national security communications network goes down

https://www.cnn.com/2026/11/17/politics/highly-classified-national-security-communications-networ...
593•monkeydust•19h ago•679 comments

Archive Team is archiving the Apple Support Community

https://wiki.archiveteam.org/index.php/Apple_Discussions
201•digitaldragon•11h ago•72 comments

AI is killing All About Berlin

https://nicolasbouliane.com/blog/death-by-ai
375•grey-area•4h ago•346 comments

Claude was trained on protein sequences at scale

http://xinmingtu.cn/blog/2026/claude-opus-5-5-protein-sequences/
66•gmays•7h ago•26 comments

My Emacs 31 contributions

https://xenodium.com/my-emacs-31-contributions
17•xenodium•1d ago•0 comments

350 years ago, Ole Rømer discovered that light has a finite speed

https://www.sciencenorway.no/culture-history-history-of-science/350-years-ago-this-man-discovered...
339•dxs•16h ago•108 comments

MAI Code 2 and Code 2 Flash

https://microsoft.ai/news/introducing-mai-code-2-and-mai-code-2-flash/
367•lemonish97•17h ago•155 comments

jQuery 4.1.0

https://github.com/jquery/jquery/releases/tag/4.1.0
329•petecooper•15h ago•167 comments

Phrack 73

https://phrack.org/issues/73/introduction_md
390•notmine1337•16h ago•53 comments

Harvard researchers find AI coding agents shifted the bottleneck to code review

https://complexdiscovery.com/harvard-researchers-find-ai-coding-agents-shifted-the-bottleneck-to-...
193•judahmeek•14h ago•270 comments

Why Fibonacci?

https://www.evilgeniuslabs.org/why-fibonacci
39•_Microft•5h ago•5 comments

Australia's full national topographic library at your fingertips

https://www.ga.gov.au/news/australias-full-national-topographic-library-at-your-fingertips
23•bryanrasmussen•4h ago•11 comments

GPT‑6.2 Astra and Sol

https://openai.com/index/introducing-gpt-6-2-astra-sol/
1283•jasondavies•17h ago•798 comments

Solid 2.0

https://www.solidjs.com/blog/solid-2-0-the-long-hold/
319•pier25•16h ago•98 comments

Launch HN: StarSling (YC P25) – Self-improving CI for agent-volume repos

81•yonasb•16h ago•39 comments

Show HN: Unref – A Python dead code finder built on Ruff's parser

https://github.com/Apakottur/unref
31•McAvey•1d ago•5 comments

What is the best harness for each model?

https://runta.com/blog/introducing-frontierharness-eval-v1-1/
379•Edward40•20h ago•128 comments

Cerebras Disaggregated Inference

https://www.cerebras.ai/blog/cerebras-launches-disaggregated-inference
85•emschwartz•10h ago•19 comments

Fun with Constrained Programming (2012)

https://blog.cmpxchg8b.com/2012/09/fun-with-constrained-programming.html
76•colejohnson66•3d ago•3 comments

Flattening Every Memory Peak in Long-Context Mixture-of-Experts Training

https://arxiv.org/abs/2609.14306
5•gmays•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?