frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

The Future of CSS

https://www.joshwcomeau.com/css/interop-2027/
283•soheilpro•6h ago•110 comments

Show HN: SimCity, but with Permits

https://permit.petercai.com/
744•pcai•13h ago•359 comments

Muse exposes users' personal and business secrets when they share conversations

https://arstechnica.com/security/2026/10/meta-muse-exposes-users-personal-and-business-secrets-wh...
125•gumby•7h ago•34 comments

Upcoming critical PHP security release (CVE-2026-109618 / -109619)

https://news-web.php.net/php.announce/509
565•xd•11h ago•206 comments

Feds suspect ransom negotiator ran ShinyHunters extortion site

https://krebsonsecurity.com/2026/10/feds-suspect-ransom-negotiator-ran-shinyhunters-extortion-site/
184•Bender•9h ago•76 comments

Voxtral 3

https://mistral.ai/news/voxtral-3/
633•ilreb•15h ago•162 comments

eMudhra intermediate CA compromise

https://emudhra.we-have-a-problem.com/
876•galadran•17h ago•384 comments

In Hilbert space, all things are quantumly possible

https://www.quantamagazine.org/in-hilbert-space-all-things-are-quantumly-possible-20260826/
74•unprovable•5h ago•40 comments

Good type against all odds

https://unsung.aresluna.org/good-type-against-all-odds/
98•firloop•6h ago•10 comments

Composite objects and C++26 the std:polymorphic type

https://mariusbancila.ro/blog/2026/10/18/composite-objects-and-cpp26-the-stdpolymorphic-type/
13•jandeboevrie•2d ago•4 comments

Battlezone Online: BZFlag in the Browser

https://github.com/timriker/bzo
23•indigodaddy•2h ago•13 comments

The Other Epidemic: Trying to get off benzodiazepines

https://www.thebeliever.net/the-other-epidemic/
166•gaplong•8h ago•122 comments

Setting Up SSH Keys on macOS with Touch ID

https://nmattia.com/posts/2026-10-19-setting-up-ssh-keys-touch-id/
33•civilchaos•4h ago•24 comments

ZX Spectrum Next Laptop

https://www.dorchester3d.com/printing/blog/2020/11/zx-spectrum-next-laptop-version-2
47•utopcell•2d ago•4 comments

Four Years with Decker

https://beyondloom.com/blog/fouryearsdecker.html
27•ibobev•19h ago•3 comments

Pillowfort Is Closing

https://www.pillowfort.social/posts/8413273
34•BrenBarn•2h ago•19 comments

Ship Your Interpreter

https://www.basis.ai/blog/ship-your-interpreters/
18•gopiandcode•1d ago•7 comments

Google open-sources TorchTPU, a native PyTorch back end for TPUs

https://github.com/google-pytorch/torch_tpu
327•ilreb•15h ago•74 comments

Borrow Checking Zero-Cost Cyclic Mutability

https://antelang.org/blog/safe_cyclic_mutability/
28•jfecher•1d ago•2 comments

SlopCodeBench 10/2026 – Opus 5.5, Astra wins overall, xhigh considered harmful

https://github.com/humanlayer/advanced-context-engineering-for-coding-agents/blob/main/benchmarki...
245•dhorthy•5d ago•94 comments

What shall I teach my son?

https://stevekrouse.com/ends
370•Curiositry•14h ago•441 comments

Using Claude to reduce the attack surface of code

https://www.anthropic.com/research/attack-surface-reduction
23•dnw•4h ago•6 comments

Apple broke an essential presentation feature of iPads

https://teddysvoronos.com/2026-10-19-apple-broke-an-essential-presentation-feature-of-ipads/
544•evanb•19h ago•270 comments

DeepInfer: High-performance inference framework for DeepSeek models

https://github.com/deepseek-ai/DeepInfer
2228•ggcr•22h ago•853 comments

C# now beats Rust on WASM size

https://github.com/zion-sati/NetWasm
29•sumnole•4h ago•7 comments

Ofcom concedes defeat in 4chan case

https://prestonbyrne.com/2026/10/20/ofcom-concedes-defeat/
377•iamnothere•17h ago•290 comments

Sixteen years after Deepwater Horizon, deep sea life shows few signs of recovery

https://e360.yale.edu/digest/deepwater-horizon-deep-sea-recovery
254•speckx•15h ago•153 comments

Tsrs: A Port of TypeScript to Rust

https://blog.cloudflare.com/typescript-rust-port/
394•hnisjafx40•18h ago•194 comments

To Make, or to Buy: The Economics of Decision Models

https://pncnmnp.github.io/blogs/economics-decision-models.html
40•pncnmnp•2d ago•1 comments

Advanced coding in low-resource programming languages

https://openai.com/index/low-resource-programming-languages/
67•sumnole•14h ago•73 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?