frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Human brain is two separate organs, Stanford Medicine-led research finds

https://med.stanford.edu/news/all-news/2026/09/two-separate-brains.html
104•emigre•1h ago•25 comments

If math is more than proof, we need to better celebrate the rest of it

https://terrytao.wordpress.com/2026/09/18/if-math-is-more-than-proof-we-need-to-better-celebrate-...
24•num42•54m ago•8 comments

San Francisco Onion Futures Company

https://onionfutures.com/
145•z-mach9•2h ago•52 comments

Android 17 is the first since 3.x to add new APIs without releasing to the AOSP

https://grapheneos.social/@GrapheneOS/117282080803799576
769•theanonymousone•12h ago•369 comments

Typesafe-computer-use drives a Mac toward a goal for 1/50th of a cent per step

https://github.com/awlevin/typesafe-computer-use
62•rahimnathwani•2d ago•22 comments

GPT-6 Astra Solves a WWI German Radio Cipher

https://www.prinzai.com/p/gpt-6-astra-solves-a-wwi-german-radio
14•nsoonhui•40m ago•0 comments

SDCC – Small Device C Compiler

https://sdcc.sourceforge.net/
58•lioeters•4h ago•15 comments

Science Is Open Software

https://jepedersen.dk/blog/202505_research/
68•jegp•5h ago•25 comments

Cloudflare Quick Tunnels

https://try.cloudflare.com/
681•jcbhmr•17h ago•275 comments

Why building a Rust LSP is hard

https://rust-glancer.github.io/blog/why-lsp-is-hard/
49•agluszak•2d ago•24 comments

Saving another 100TB of RAM

https://blog.cloudflare.com/saving-100-tb-of-ram-with-math/
332•f311a•12h ago•64 comments

NASA-IBM Lunar Foundation open-Source Geospatial AI Model

https://newsroom.usra.edu/usra-contributes-planetary-science-expertise-to-nasa-ibm-lunar-foundati...
12•noobplus•2h ago•1 comments

How to Write with an LLM

https://sockpuppet.org/blog/2026/09/17/how-to-write-with-an-llm/
470•joeriddles•1d ago•315 comments

How OpenAI Used Its Own LLMs to Design Its Jalapeño Chip

https://spectrum.ieee.org/llms-for-chip-design
108•maxall4•8h ago•77 comments

Ctenophores: Wonders of Biology

https://www.quantamagazine.org/ctenophores-arent-just-beautiful-theyre-biological-wonders-20260916/
10•randomImmigrant•2d ago•4 comments

Goroutine Leak Profiles

https://go.dev/blog/goroutine-leak-profiles
24•torutofu•2d ago•2 comments

You can run Git on object storage if you re-make packfiles

https://www.tigrisdata.com/blog/objgit-packfiles/
24•evacchi•2d ago•6 comments

The first new cat species discovered in 100 years

https://www.nationalgeographic.com/animals/article/meet-the-first-new-cat-species-discovered-in-1...
254•ohjeez•1d ago•90 comments

Show HN: Cactus Needle 3: 8-29MB automation models can match DeepSeek V4 Flash

https://cactuscompute.com/needle
194•HenryNdubuaku•1d ago•87 comments

OpenJev

https://openjev.com/
608•ilreb•21h ago•257 comments

Photon-Emission-Guided Laser Fault Injection Enables RP2350 Secure Debug

https://donjon.ledger.com/blog/rp2350-secure-debug-laser-fault-injection/
185•synack•14h ago•66 comments

Stepfun Step 5 Preview (LLM): On AA Pareto frontier

https://artificialanalysis.ai/models/step-5
3•AnodicElegy•1h ago•1 comments

Cache-to-Cache: Direct Semantic Communication Between LLMs (2025)

https://arxiv.org/abs/2510.03215
82•rochansinha•12h ago•12 comments

The Farnese letter

https://simonklee.dk/farnese-letter
40•grigolin•1d ago•6 comments

Minimal Phone 2

https://minimalcompany.com/
253•nashashmi•1d ago•211 comments

Xcode 27.1 Beta Release Notes

https://developer.apple.com/documentation/xcode-release-notes/xcode-27_1-release-notes
136•CameronBanga•12h ago•95 comments

Cyclomatic Complexity in C#

https://blog.ndepend.com/understanding-cyclomatic-complexity/
54•gone35•2d ago•18 comments

Inside ZCode: Silently uploading your Git history to the cloud

https://blog.ferstar.org/en/posts/zcode-silent-workspace-snapshot-upload/
290•csmantle•1d ago•97 comments

Warez: The Infrastructure and Aesthetics of Piracy (2021)

https://archive.org/details/b904a8eb-9c98-4bb1-bf25-3cb9d075b157
138•succinct_ideas•1d ago•49 comments

Google's Gemini AI hacked three companies in security test

https://www.bbc.co.uk/news/articles/c607l0k72rlvo
8•luxpir•1h ago•0 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?