frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Java4Shell: RCE in OpenJDK when processing Base64

https://calif.io/java4shell/
643•werrett•7h ago•169 comments

ID.me terms required for IRS sign-in

https://consumerrights.wiki/w/ID.me_terms_required_for_IRS_sign-in
198•DeepLogin•3h ago•72 comments

Google's AI answers reducing search traffic by 40%

https://revscope.co/blog/search-seo-geo-2026/
179•slashdev•4h ago•126 comments

GPT‑6.2 Astra and Sol

https://openai.com/index/introducing-gpt-6-2-astra-sol/
1155•jasondavies•10h ago•731 comments

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

https://blog.cloudflare.com/quad9-withdrawal-from-france/
363•subset•6h ago•116 comments

Microsoft's ONNX Runtime has disappeared from GitHub

https://github.com/microsoft/onnxruntime
186•nvader•5h ago•43 comments

Archive Team is archiving the Apple Support Community (closes November 20, 2026)

https://wiki.archiveteam.org/index.php/Apple_Discussions
119•digitaldragon•4h ago•47 comments

GoGoGrandparent (YC S16) Is a Front End JavaScript / TypeScript Engineer

https://www.ycombinator.com/companies/gogograndparent/jobs/05woouL-front-end-javascript-typescrip...
1•davidchl•49m ago

Nvidia stopped disclosing Singapore sales as revenues hit $104B

https://www.ft.com/content/dbde7a30-548c-4f9d-a4be-7898a0c24dcf
437•louiereederson•11h ago•212 comments

Highly classified US national security communications network goes down

https://www.cnn.com/2026/11/17/politics/highly-classified-national-security-communications-networ...
517•monkeydust•12h ago•589 comments

jQuery 4.1.0

https://github.com/jquery/jquery/releases/tag/4.1.0
272•petecooper•8h ago•151 comments

MAI Code 2 and Code 2 Flash

https://microsoft.ai/news/introducing-mai-code-2-and-mai-code-2-flash/
308•lemonish97•9h ago•142 comments

Phrack 73 Released

https://phrack.org/issues/73/introduction_md
309•notmine1337•9h ago•46 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...
274•dxs•8h ago•82 comments

Engineering Vitals in the Age of AI

https://octopus.com/blog/engineering-vitals-in-the-age-of-ai
6•paulstovell•48m ago•0 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-...
89•judahmeek•7h ago•151 comments

Cerebras Disaggregated Inference

https://www.cerebras.ai/blog/cerebras-launches-disaggregated-inference
43•emschwartz•3h ago•13 comments

Solid 2.0

https://www.solidjs.com/blog/solid-2-0-the-long-hold/
255•pier25•9h ago•73 comments

Fun with Constrained Programming

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

What is the best harness for each model?

https://runta.com/blog/introducing-frontierharness-eval-v1-1/
345•Edward40•13h ago•120 comments

Tencent Hy4 Flash

https://hy.tencent.ai/research/hy4-flash
80•lyra1337•7h ago•11 comments

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

https://starsling.dev
62•yonasb•9h ago•35 comments

Apple Services Down

https://developer.apple.com/system-status/
654•willy_k•10h ago•368 comments

Web Browser Engineering (2021)

https://browser.engineering/
136•ibobev•8h ago•20 comments

Latent Lattice Language Models

https://shivamduggal4.github.io/latent-lattice-language-models/
34•E-Reverance•6h ago•4 comments

Effects of a Nuclear Detonation in Low Earth Orbit

https://arxiv.org/abs/2611.09827
90•PaulHoule•8h ago•62 comments

Not Everything Needs an LLM

https://newsletter.posthog.com/p/decision-models
116•speckx•10h ago•45 comments

Who Builds the Machines That Build the Machines?

https://read.corematter.com/p/section-232-us-machine-tools
113•gmays•10h ago•35 comments

Adopting Python 3.15's lazy imports: a 4× faster CLI, and where they didn't help

https://namegarage.com/blog/python-3-15-lazy-imports
6•rbanffy•3d ago•3 comments

Mouse Party

https://aboard.com/lets-have-a-mouse-party/
77•bookofjoe•3d ago•14 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?