frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Private German rocket makes history, reaches orbit from European soil

https://www.space.com/space-exploration/launches-spacecraft/isar-aerospace-second-launch-norway-a...
234•bookmtn•2h ago•100 comments

Show HN: Fly By – retro biplane flying game

https://michaelteter.com/flyby.html
20•michaelteter•4d ago•12 comments

Finite time blowup for an averaged three-dimensional Navier-Stokes equation (2014)

https://terrytao.wordpress.com/2014/02/04/finite-time-blowup-for-an-averaged-three-dimensional-na...
48•gmays•2h ago•20 comments

Learn Programming with OCaml

https://usr.lmf.cnrs.fr/lpo/
139•elvis70•6h ago•64 comments

Falsehoods Programmers Believe About LANs

https://dreamstation.systems/personal/lanfalsehoods.html
14•robinpie•1h ago•0 comments

LLMs as a Cognitive Virus

https://arxiv.org/abs/2609.03344
130•canjobear•3h ago•100 comments

The "$60 Gaming PC" – AMD BC-250 (2025)

https://devquasar.com/hardware/the-60-gaming-pc-amd-bc-250/
246•networked•9h ago•75 comments

How Swiss tables work in Go built-in map

https://victoriametrics.com/blog/go-swiss-table-map/index.html
20•valyala•2d ago•0 comments

Balrogg: Demonically compacting (up to 15%) lossless Vorbis/Opus recompressor

https://github.com/iczelia/balrogg
47•palaiologos•2d ago•7 comments

Visualizing Rust's Vtables: How dyn Trait Works In Memory

https://sofiabelen.github.io/projects/visualizing-rusts-vtables-how-dyn-trait-works-in-memory/
110•torutofu•9h ago•14 comments

Discovery of a new OpenAI agent message board

https://collusion.wiki/
2068•moultano•1d ago•1498 comments

OKF Agent Memory – Git-native persistent memory for AI coding agents

https://github.com/okf-memory/okf-agent-memory
3•okf_memory•52m ago•0 comments

Actively exploited sandbox RCE in all Chromium versions

https://nvd.nist.gov/vuln/detail/cve-2026-85046
731•negura•1d ago•429 comments

Nitter has more working instances than before the takedowns

https://codeberg.org/mv12star/shitter/wiki/Instances
598•Cider9986•23h ago•283 comments

Delidded Intel I9-14900KS CT Scan

https://www.lttlabs.com/articles/2026/09/02/delidded-intel-i9-14900ks
45•willx86•3d ago•0 comments

Isar Aerospace launch into orbit [video]

https://www.youtube.com/watch?v=Ss1DUqLjecc
67•stefan_•2h ago•18 comments

America's Two Largest School Districts Impose AI Moratoriums

https://www.techpolicy.press/americas-two-largest-school-districts-impose-ai-moratoriums/
23•cdrnsf•1h ago•10 comments

How AI is breaking the British state

https://www.economist.com/leaders/2026/08/06/how-ai-is-breaking-the-british-state
8•tchalla•2h ago•2 comments

Formalizing Fermat's Last Theorem

https://www.anthropic.com/research/formalizing-fermats-last-theorem
738•jlebar•1d ago•479 comments

Terpstra Keyboard

http://terpstrakeyboard.com/
108•cl3misch•12h ago•52 comments

South African diamond mines are closing due to weak sales and lab-grown stones

https://www.wsj.com/business/diamond-mines-are-closing-and-south-africans-have-few-alternatives-f...
30•bookofjoe•1h ago•8 comments

Stopping the Unstoppable: When an unstoppable force meets a dashpot snubber

https://practical.engineering/blog/2026/9/1/stopping-the-unstoppable
43•crescit_eundo•4d ago•4 comments

ISAR Aerospace 5 Sept Mission Onward and Upward

https://isaraerospace.com/mission-updates-overview
7•t43562•3h ago•1 comments

Steffen's Polyhedron

https://www.gregegan.net/SCIENCE/Steffen/Steffen.html
44•pavel_lishin•2d ago•3 comments

A bizarre Commodore 64 peripheral, a mime, and some pretty bad ads

https://buttondown.com/suchbadtechads/archive/spartan-and-the-mime/
69•rfarley04•10h ago•8 comments

Statichost.eu – European static site hosting

https://www.statichost.eu/
436•p4bl0•1d ago•198 comments

Singapore subway (mrt) information display types

https://www.sgtrains.com/technology-infosys.html
40•gregorvand•3d ago•9 comments

Can AI design circuit boards yet?

https://eebench.org/blog/can-ai-design-circuit-boards-yet/
365•iopapa•1d ago•205 comments

Wikimedia Foundation Workers Overwhelmingly Vote to Form Union with CWA

https://wikiworkersunited.org/announcements/2026-09-04-us-wikimedia-foundation-workers-overwhelmi...
250•robin_reala•6h ago•112 comments

.gitignore Everything by Default

https://packagemain.tech/p/gitignore-everything-by-default
139•der_gopher•9h ago•146 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?