frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Astra for Law

https://openai.com/index/astra-for-law/
204•vertigoruntime•2h ago•219 comments

Bend – A language that blocks AI mistakes via proof, on CPU and GPU

https://bend-lang.com/
198•nicolas-siplis•2h ago•105 comments

Bonsai 2 27B: Near-Lossless Compression in a 9x Smaller Footprint

https://prismml.com/news/bonsai-2-27b
102•JonSchneider•1h ago•30 comments

Hister: A private search engine for the pages you visit and the files you keep

https://github.com/asciimoo/hister
395•bookofjoe•6h ago•121 comments

Wax motor

https://en.wikipedia.org/wiki/Wax_motor
172•mhb•1d ago•37 comments

Fujitsu launches made-in-Japan next-generation CPU FUJITSU-MONAKA

https://global.fujitsu/en-global/pr/news/2026/09/14-02
479•my123•2d ago•174 comments

Sex, AI, and the Apocalypse

https://www.iankduncan.com/personal/2026-09-16-sex-ai-and-the-apocalypse/
59•Anon84•1h ago•33 comments

Flet 1.0 – Build cross-platform apps in Python

https://flet.dev/
25•absqueued•2h ago•3 comments

How to Write with an LLM

https://sockpuppet.org/blog/2026/09/17/how-to-write-with-an-llm/
21•joeriddles•1h ago•11 comments

CrowdSec Source Code Leak

https://www.crowdsec.net/blog/crowdsec-statement-source-code-exposure
118•eccgecko•7h ago•35 comments

Infinite-Parameter LLMs: Generating and Adapting Weights from Live Data

https://arxiv.org/abs/2609.18842
91•Betelbuddy•6h ago•26 comments

Rate limits on GitLab.com are changing

https://about.gitlab.com/blog/rate-limit-change-2026/
139•darkwater•7h ago•103 comments

Diplodocus, Long Thought Exclusively American, Turns Up in Spain

https://www.sci.news/paleontology/spanish-diplodocus-15064.html
10•embedding-shape•2d ago•4 comments

How Uber Protects Against Retry Storms

https://www.uber.com/us/en/blog/protecting-against-retry-storms/
12•iscmt•1h ago•8 comments

The American Religion of Self-Storage Facilities

https://www.newyorker.com/magazine/2026/09/21/the-american-religion-of-self-storage-facilities
173•pseudolus•9h ago•295 comments

TSMC revealing details about next gen A14 node

https://iedm26.mapyourshow.com/8_0/sessions/session-details.cfm?scheduleid=331
77•osnium123•2d ago•28 comments

Everybody's Lost Their Minds

https://www.netmeister.org/blog/everybodys-lost-their-minds.html
259•ibobev•3h ago•173 comments

Zettascale (YC S24) Is Hiring ASIC/FPGA Engineers to Build Chips for ASI

https://zscc.ai/careers?job_id=109821
1•el_al•6h ago

How GLM built its own inference infrastructure

https://z.ai/blog/glm-built-its-inference-infrastructure
351•whiteros_e•14h ago•255 comments

Why I didn’t sign the Fields medallists’ letter

https://gowers.wordpress.com/2026/09/17/why-i-didnt-sign-the-fields-medallists-letter/
187•simianwords•14h ago•242 comments

How do we prevent mathemathics from devolving into the Medieval Era of secrecy?

https://mathoverflow.net/questions/515260/how-do-we-prevent-mathematics-from-devolving-into-the-m...
57•jjgreen•2d ago•31 comments

The most important product decision is what you don't build

https://liamnugent.me/posts/what-you-dont-build/
14•ChrisArchitect•2h ago•5 comments

Show HN: Snapdrop: Instantly share files between devices. No setup, no signup

https://snapdrop.me
9•Capira•2h ago•6 comments

Canto: A speech model built for the real world

https://wisprflow.ai/canto
29•sleepypandas•4h ago•11 comments

One year of sponsored Servo development

https://servo.org/blog/2026/09/15/one-year-of-sponsorship/
338•AshleysBrain•14h ago•138 comments

Running Ubuntu on the Lenovo IdeaPad Duet

https://vhaudiquet.fr/blog/duet-ubuntu/
61•vhaudiquet•3d ago•19 comments

CCC invites all model citizens to 40C3

https://events.ccc.de/en/2026/09/12/40c3-model-citizens/
319•antonly•15h ago•175 comments

André Weil and the Hodge Conjecture

https://jiahao116.github.io/Articles/
24•caojiahao•5d ago•8 comments

Launch HN: Skillsync (YC W26) – AI chat sessions made portable across agents

38•cat-whisperer•6h ago•43 comments

Towards Self-Driving Codebases

https://blog.detail.dev/posts/towards-self-driving-codebases/
92•wilhelmklopp•6h ago•74 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?