frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Previewing GPT‑5.6 Sol: a next-generation model

https://openai.com/index/previewing-gpt-5-6-sol/
363•minimaxir•1h ago•224 comments

MicroVMs: Run isolated sandboxes with full lifecycle control

https://aws.amazon.com/blogs/aws/run-isolated-sandboxes-with-full-lifecycle-control-aws-lambda-in...
161•justincormack•3d ago•93 comments

Show HN: Smart model routing directly in Claude, Codex and Cursor

https://github.com/workweave/router
66•adchurch•2h ago•52 comments

U.S. government will decide who gets to use GPT-5.6

https://www.washingtonpost.com/technology/2026/06/26/openai-says-us-government-will-vet-users-its...
82•alain94040•42m ago•325 comments

Ultrasound imaging of the brain

https://alephneuro.com/blog/ultrasound-brain
150•rossant•7h ago•55 comments

Om Malik has died

https://om.co/2026/06/24/1966-2026/
1225•minimaxir•22h ago•148 comments

An entire Herculaneum scroll has been read for the first time

https://scrollprize.org/firstscroll
1578•verditelabs•1d ago•349 comments

Modern GPU Programming for MLSys

https://mlc.ai/modern-gpu-programming-for-mlsys/
14•crowwork•3d ago•1 comments

Springer Nature has removed two studies by Max Planck

https://www.science.org/content/article/why-have-papers-one-history-s-most-famous-physicists-been...
279•adharmad•4h ago•131 comments

Liva AI (YC S25) Is Hiring

https://www.ycombinator.com/companies/liva-ai/jobs/gvtc3Ep-founding-operations-lead
1•ashlleymo•2h ago

What is a Lithium-ion capacitor?

https://www.jtekt.co.jp/e/products/capacitor/capacitor_about.html
15•ksec•3h ago•2 comments

Libre Barcode Project

https://graphicore.github.io/librebarcode/
260•luu•15h ago•45 comments

What Is a Nomogram and Why Would It Interest Me?

https://lefakkomies.github.io/pynomo-doc/introduction/introduction.html#what-is-a-nomogram-and-wh...
10•Eridanus2•1h ago•3 comments

22-year-old Mozart's handwritten notebook unearthed in 'major discovery'

https://www.classicfm.com/composers/mozart/handwritten-notebook-discovered-major-paris/
222•thunderbong•6d ago•70 comments

What happened after 2k people tried to hack my AI assistant

https://www.fernandoi.cl/posts/hackmyclaw/
319•cuchoi•16h ago•149 comments

Incident CVE-2026-LGTM

https://nesbitt.io/2026/06/26/incident-report-cve-2026-lgtm.html
424•mooreds•6h ago•74 comments

Framework's 10G Ethernet module exposes USB-C's complexity

https://www.jeffgeerling.com/blog/2026/framework-10g-ethernet-module-usb-c-complexity/
289•Alupis•17h ago•168 comments

LaTeX.wasm: LaTeX Engines in Browsers

https://www.swiftlatex.com/
44•theanonymousone•2d ago•11 comments

Bipartite Matching Is in NC

https://scottaaronson.blog/?p=9851
92•amichail•3d ago•13 comments

Show HN: WebBase-III – dBASE III rebuilt in the browser with its own interpreter

https://github.com/DDecoene/WebBaseIII
60•ddecoene•2d ago•15 comments

A US military exercise to launch a satellite on short notice

https://arstechnica.com/space/2026/06/a-us-military-exercise-in-space-got-underway-with-barely-an...
91•jonbaer•3d ago•58 comments

Jolla Phone (October 2026)

https://commerce.jolla.com/products/jolla-phone-october-2026
206•mrbn100ful•4h ago•118 comments

A game where you're an OS and have to manage processes, memory and I/O events

https://github.com/plbrault/youre-the-os
331•exploraz•3d ago•73 comments

The 'papers, please' era of the internet will decimate your privacy

https://expression.fire.org/p/the-papers-please-era-of-the-internet
1034•bilsbie•21h ago•525 comments

The Garbage Collection Handbook: The Art of Automatic Memory Management (2nd Ed) (2023)

https://gchandbook.org/
223•teleforce•19h ago•47 comments

Ask HN: Is "no source code was copied" still a sufficient copyright defense?

23•oscgam1•3h ago•28 comments

FEXPRs vs. vtable: how LispE interpreter works

https://github.com/naver/lispe/wiki/2.7-FEXPR-vs.-vtable
79•birdculture•2d ago•6 comments

Oxide computer 3D rack guided tour

https://explorer.oxide.computer/
452•darthcloud•4d ago•195 comments

We all depend on open source. We will defend it together

https://akrites.org/letter/
414•dhruv3006•13h ago•199 comments

IBM debuts sub-1 nanometer chip technology

https://newsroom.ibm.com/2026-06-25-ibm-debuts-worlds-first-sub-1-nanometer-chip-technology
373•porridgeraisin•1d ago•198 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?