frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Google SWE points 48 AI agents at NASA Lidar, finds unmapped Maya pyramid in 72h

https://pietromiotti.com/latest/maya-site/?maya
122•eyvindn•1h ago•41 comments

Can a Linear Program Do Weight-Space Programming?

https://nathan.rs/posts/weight-space-lp/
34•emschwartz•57m ago•4 comments

Using voltage glitching to unleash the A100 in my mining card

https://blog.kate.land/posts/using-voltage-glitching-to-unlock-the-a100/
52•lae•2h ago•18 comments

Protecting SSH Keys with macOS Secure Enclave

https://gatezh.com/posts/macos-secure-enclave-ssh-keys/
277•js2•8h ago•99 comments

Next-Level Benchmarking Overfitting – Thomas Neumann

http://databasearchitects.blogspot.com/2026/11/next-level-benchmarking-overfitting.html
14•artrax•1h ago•0 comments

Smart home devices should work without the internet

https://docodethatmatters.com/home-automation-overnight-success/
1055•skittleson•22h ago•370 comments

.name Grandfathered

https://neil.fraser.name/news/2026/11/10/
888•p4bl0•20h ago•191 comments

The Housing Market Is Nuts

https://nuts.logical.li/
18•herTTTz•2h ago•13 comments

Tinfoil (YC P25) is hiring an applied AI security engineer in San Francisco

1•FrasiertheLion•1h ago

Scion is back and is going to sell a kei truck in America

https://www.theautopian.com/scion-is-back-and-its-going-to-sell-a-freaking-kei-truck-in-america/
505•NaOH•17h ago•328 comments

Apple has new Mac app coming to make running local AI models easy

https://9to5mac.com/2026/11/10/apple-has-new-mac-app-coming-to-make-running-local-ai-models-easy/
336•linolevan•16h ago•324 comments

Greg Kurtzer's Ginux is now a userspace kernel

https://github.com/gmkurtzer/ginux
92•d3Xt3r•8h ago•48 comments

A great old-timey game-programming hack (2013)

https://blog.moertel.com/posts/2013-12-14-great-old-timey-game-programming-hack.html
210•palsecam•11h ago•43 comments

Six Math Essentials

https://teorth.github.io/tao-web/six-math-essentials.html
280•digital55•16h ago•54 comments

Starlink Mini 2

https://starlink.com/mini-2
451•robertjfclarke•19h ago•479 comments

Synaptics patent claims stop work on DisplayLink drivers

https://lwn.net/SubscriberLink/1102549/acbc92e00cee3a3f/
430•speckx•19h ago•242 comments

Physically Controllable Relighting of Photographs

https://yaksoy.github.io/PhysicalRelighting/
7•summarity•1h ago•0 comments

AlphaProof Code

https://deepmind.google/blog/introducing-alphaproof-code/
655•ilreb•1d ago•187 comments

Why Amstrad chose the 3" drives

https://www.cpcwiki.eu/forum/amstrad-cpc-hardware/why-amstrad-chose-the-3-drives/
64•Skyfall106•4d ago•21 comments

Why I wrote the BEAM book (2025)

https://happihacking.com/blog/posts/2025/why_I_wrote_theBEAMBook/
124•zenincognito•1d ago•22 comments

Make this forward pass as fast as possible

https://ianbarber.blog/2026/11/09/make-this-forward-pass-as-fast-as-possible/
3•matt_d•1d ago•0 comments

To deter bioterrorism, U.S. imposes new rules on ordering synthetic DNA

https://www.science.org/content/article/deter-bioterrorism-u-s-imposes-new-rules-ordering-synthet...
126•Metacelsus•10h ago•99 comments

Small-Grid Wraparound Cellular Automata

https://justismills.substack.com/p/small-grid-wraparound-cellular-automata
7•surprisetalk•1d ago•0 comments

Show HN: Black Ops II statically recompiled to native ARM64 macOS

https://github.com/adrbn/bo2-mac
59•adrbn•8h ago•17 comments

Val Town is winding down

https://blog.val.town/winding-down
402•tosh•19h ago•98 comments

Show HN: Get your coding agent off ~2019 JavaScript, onto modern web primitives

https://github.com/GoogleChrome/modern-web-guidance
395•paulirish•19h ago•128 comments

Claude Whiteboards, Claude Sheets, and Claude Data

https://claude.com/resources/articles/sheets-whiteboards-data
248•Yorothegoat•19h ago•184 comments

Tracking Anthropic-discovered vulnerabilities

https://www.vulncheck.com/blog/anthropic-glasswing-november-update
424•panic•15h ago•203 comments

Hacking the Meta Ray-Ban smartglasses

https://p0pcycle.com/2026/11/06/hacking-the-meta-ray-ban-smartglasses/
129•moooooky•3d ago•44 comments

A Compendium of Abandoned Greenhouses

https://www.messynessychic.com/2015/01/15/a-compendium-of-abandoned-greenhouses/
56•ohjeez•2d ago•7 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?