frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Git for US Legislation

https://lexifina.com/blog/git-for-the-us-code
131•alansaber•3h ago•56 comments

Genie 4

https://deepmind.google/blog/genie-4-a-new-generation-of-world-simulation/
804•acossta•12h ago•489 comments

Ink droplets in motion snag top prize in Nikon Small World contest

https://arstechnica.com/science/2026/10/meet-the-2026-winner-of-nikons-small-world-photomicrograp...
137•_Microft•2d ago•24 comments

Ghostty 1.4

https://ghostty.org/docs/install/release-notes/1-4-0
870•deaux•12h ago•271 comments

Tailscale SSH: Investigation and remediation update

https://tailscale.com/ssh-investigation-update
242•figmert•9h ago•120 comments

Early progress on accelerating drug development with Claude

https://www.anthropic.com/research/early-progress-drug-development
181•dataking•8h ago•161 comments

Survival LLM: AI assistant and emergency library that runs on your own computer

https://www.brangus.io/survival-llm
252•Luc•9h ago•120 comments

A Love Letter to the Super Dimension Fortress

https://brennan.day/a-love-letter-to-the-super-dimension-fortress/
27•jruohonen•3d ago•3 comments

Assembly Nights

https://ratfactor.com/assembly-nights
33•andsoitis•2d ago•5 comments

Raspberry Pi Zero 3W and Pi 4 Model A spotted in device trees

https://bret.dk/raspberry-pi-zero-3-w-pi-4-model-a/
127•sthlmb•8h ago•58 comments

Reviewers rarely talk about reliability. Owners bring it up twice as often

https://www.bettascore.ai/research/reliability-reviewers-vs-owners
93•tsxng•6h ago•77 comments

New 14‑inch MacBook Pro with M6

https://www.apple.com/in/newsroom/2026/10/apple-introduces-the-new-14-inch-macbook-pro-with-m6/
317•beex•12h ago•406 comments

81 Jokes for the ZX81

https://spelk.press/gb/products/81-jokes-for-the-zx81
54•robin_reala•1d ago•5 comments

Python's experimental JIT to be removed

https://lwn.net/SubscriberLink/1102102/0c00e4d550f25f8c/
469•f311a•17h ago•253 comments

New iMac with M6

https://www.apple.com/imac/
321•notfried•16h ago•396 comments

Classification of Finite Simple Groups Formalized in Lean

https://cfsg.axiommath.ai/
188•pfdietz•12h ago•52 comments

An examination of lost firefly species of the US and Canada

https://journaloflostspecies.org/index.php/jls/article/view/37/33
104•bryanrasmussen•3d ago•27 comments

What Happened to the Neanderthals?

https://www.nytimes.com/2026/10/26/science/what-happened-to-the-neanderthals.html
13•Hooke•1d ago•5 comments

Moxnox 1.0: NT-Like, POSIX-Compatible OS Running Atop Btrfs

https://github.com/maharmstone/moxnox
37•SockThief•5h ago•7 comments

Code-execution flaw in UEFI firmware threatens most servers on planet Earth

https://arstechnica.com/security/2026/10/code-execution-flaw-in-uefi-firmware-threatens-most-serv...
68•DamnInteresting•8h ago•14 comments

Radio-tagged Monarch butterflies

https://news.vt.edu/articles/2026/10/cmi-monarchs.html
42•rdmuser•11h ago•16 comments

US Government is hiding a secret court ruling about how it spies on Americans

https://www.wired.com/story/the-us-government-is-hiding-a-secret-court-ruling-about-how-it-spies-...
864•helterskelter2•14h ago•309 comments

SS United States to be sunk as largest artificial reef

https://divemagazine.com/scuba-diving-news/ss-united-states-to-be-sunk-as-worlds-largest-artifici...
109•geox•2d ago•79 comments

Four Months of Zig

https://gracefulliberty.com/articles/four-months-of-zig/
96•ibobev•8h ago•58 comments

Why Micron Is Suddenly Ditching 4F² DRAM as Rivals Double Down

https://hothardware.com/news/why-micron-is-suddenly-ditching-4f-dram
155•rbanffy•1d ago•23 comments

Nvidia and Micron Make Up 34% of America's Earnings Boom

https://www.wsj.com/finance/stocks/the-earnings-boom-is-heavily-reliant-on-just-a-handful-of-stoc...
121•JumpCrisscross•2d ago•24 comments

Tabletop Whale is an original science illustration blog

https://tabletopwhale.com
33•Levitating•4d ago•3 comments

Expanding our partnership with GSA to bring Claude to all levels of government

https://www.anthropic.com/news/expanding-partnership-gsa
34•matthieu_bl•6h ago•24 comments

Introducing LFM3: Every Modality for Specialized Intelligence

https://www.liquid.ai/blog/lfm3
132•Philpax•11h ago•51 comments

Land Value Capture in Practice: Ethiopia's Urban Land Lease System

https://blog.landeconomics.org/p/land-value-capture-in-practice-reflections
54•surprisetalk•1d ago•11 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?