frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Gemini 4 Carbon

https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-4-carbon/
456•acossta•2h ago•383 comments

CNC Stone Carving

https://carmelitegothic.com/cnc-stone-carving/
271•bschne•4h ago•94 comments

Why Is This Fingerprinting Script Creating Bioweapons?

https://nullpt.rs/fingerprinting-bioweapons
90•hazebooth•1h ago•13 comments

MacBook Pro with PROLED XDR Display and Touch

https://www.apple.com/macbook-pro/proled-xdr-display/
281•etothet•2h ago•435 comments

Dayjob: Tax – evaluating AI agents on 50 professional tax assignments

https://surgehq.ai/blog/dayjob-tax
106•landonxi•3h ago•61 comments

Show HN: SlideBySide – Present slides without sharing your screen

https://slidebyside.com/
24•denismenace•2h ago•11 comments

The Grid, a factory-scale robot in Massachusetts that builds PCBs on demand

https://www.circuithub.com/post/unveiling-the-grid
302•seddona•2d ago•136 comments

Start Doing Graph Theory

https://vertex.degree/
447•ibobev•5d ago•103 comments

Apple's git still trusts the compromised eMudhra certificates

https://emudhra.we-have-a-problem.com/apple.html
874•galadran•8h ago•338 comments

Converge (YC S23) Is Hiring a Founding Platform Engineer

https://www.runconverge.com/careers/founding-platform-engineer
1•thomashlvt•2h ago

The Agent SDK

https://cursor.com/blog/agent-sdk
64•torutofu•5h ago•66 comments

Gaussian Splats part 3: There's always a bigger scene

https://www.magnopus.com/blog/gaussiansplats-part-3-theres-always-a-bigger-scene
63•ibobev•5d ago•13 comments

AlpineBSD

https://wiki.alpinebsd.org
91•bradley_taunt•4h ago•81 comments

Emacs Turns 50

https://www.technologyreview.com/2026/10/20/1145399/emacs-turns-50/
281•internet_points•5h ago•112 comments

Regent's Ground-Effect Vehicle Reimagines Coastal Travel

https://spectrum.ieee.org/ground-effect-vehicle
28•rbanffy•3d ago•17 comments

Git for the US Code

https://lexifina.com/blog/git-for-the-us-code
401•alansaber•17h ago•207 comments

Counting Sand Dunes in the Simpson Desert

https://www.fromtheroad.ford.com/img/en/articles/2026/simpson-desert-ranger-super-duty-counting-d...
5•bryanrasmussen•2d ago•0 comments

From confession to conspiracy: How the Wedgewood fake polls story spread

https://www.cip.uw.edu/2026/10/23/from-confession-to-conspiracy-how-the-wedgewood-fake-polls-stor...
47•croes•4d ago•32 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...
367•_Microft•3d ago•68 comments

Kentucky man becomes the first humanist granted religious exemption from AI

https://religionnews.com/2026/10/26/in-a-first-a-humanist-granted-a-religious-exemption-from-usin...
312•danso•5h ago•365 comments

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

https://www.brangus.io/survival-llm
492•Luc•23h ago•186 comments

Decompiling Fast Food Tycoon 2: Drawing the World

https://healeycodes.com/decompiling-fast-food-tycoon-2-drawing-the-world
160•healeycodes•4d ago•31 comments

At least 68 killed in Spanish high-speed train crash

https://www.bbc.com/news/live/cv1j309d4g98t
5•saikatsg•21m ago•1 comments

US agency approves Amazon Leo’s $11.5B acquisition of Globalstar

https://www.reuters.com/business/media-telecom/us-agency-approves-amazon-leos-115-billion-acquisi...
195•noptd•7h ago•94 comments

Nvidia Nemotron 3.5 Transcribe: open ASR for 40 languages

https://huggingface.co/blog/nvidia/nemotron-transcribe-granary
59•wondersky•3h ago•7 comments

Archive.today links going forward

https://www.reddit.com/r/Seattle/comments/1xhf6qp/archivetoday_links_going_forward/
119•consumer451•3h ago•73 comments

Tailscale SSH: Investigation and remediation update

https://tailscale.com/ssh-investigation-update
357•figmert•23h ago•183 comments

Early progress on accelerating drug development with Claude

https://www.anthropic.com/research/early-progress-drug-development
308•dataking•22h ago•301 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...
282•DamnInteresting•22h ago•177 comments

Executable Archaeology: Reanimating the Heuristic Compiler (1961) and KBEmacs (1984)

https://arxiv.org/abs/2610.36341
8•abrax3141•17h 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?