frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

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

https://grapheneos.social/@GrapheneOS/117282080803799576
460•theanonymousone•5h ago•214 comments

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

https://spectrum.ieee.org/llms-for-chip-design
34•maxall4•1h ago•31 comments

Cloudflare Quick Tunnels

https://try.cloudflare.com/
545•jcbhmr•10h ago•238 comments

Saving another 100TB of RAM

https://blog.cloudflare.com/saving-100-tb-of-ram-with-math/
197•f311a•5h ago•39 comments

The Farnese letter

https://simonklee.dk/farnese-letter
21•grigolin•1d ago•2 comments

Xcode 27.1 Beta Release Notes

https://developer.apple.com/documentation/xcode-release-notes/xcode-27_1-release-notes
110•CameronBanga•5h ago•63 comments

How to Write with an LLM

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

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

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

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

https://donjon.ledger.com/blog/rp2350-secure-debug-laser-fault-injection/
146•synack•7h ago•51 comments

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

https://cactuscompute.com/needle
159•HenryNdubuaku•1d ago•76 comments

Claude Code now reads AGENTS.md if there is no Claude.md

https://code.claude.com/docs/en/changelog
474•datadrivenangel•3h ago•176 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...
155•ohjeez•1d ago•49 comments

OpenJev

https://openjev.com/
539•ilreb•14h ago•243 comments

Cyclomatic Complexity in C#

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

Two parallel neural ectoderm progenitors contribute to the developing brain

https://www.newscientist.com/article/2589739-our-brain-evolved-from-two-primitive-nervous-systems...
102•Jimmc414•9h ago•53 comments

C++26: Trivial infinite loops are no longer undefined behaviour

https://www.sandordargo.com/blog/2026/09/16/cpp26-trivial-infinite-loops
143•ibobev•1d ago•189 comments

The Implications of Linguistic Illegibility for LLM Security

https://arxiv.org/abs/2609.02852
47•tomjakubowski•5h ago•17 comments

Warez: The Infrastructure and Aesthetics of Piracy (2021)

https://archive.org/details/b904a8eb-9c98-4bb1-bf25-3cb9d075b157
97•succinct_ideas•21h ago•17 comments

Minimal Phone 2

https://minimalcompany.com/
171•nashashmi•22h ago•163 comments

Column built an issuer processor from scratch

https://column.com/card-issuing/
18•Matthalp•2d ago•1 comments

Inside ZCode: Silently uploading your Git history to the cloud

https://blog.ferstar.org/en/posts/zcode-silent-workspace-snapshot-upload/
250•csmantle•18h ago•89 comments

How SpaceX streamlined the Raptor engine

https://www.construction-physics.com/p/how-spacex-streamlined-the-raptor
155•JumpCrisscross•1d ago•29 comments

A search-and-inference database from scratch in pure Zig

https://antfly.io/research/antfly-zig
52•kingcauchy•3d ago•16 comments

Size-Specialized Memory Allocation

https://go.dev/blog/size-specialized-allocations
13•spacey•1d ago•3 comments

I vibed a proof of Conway's conjecture

https://overreacted.io/how-i-vibed-a-proof-of-conways-conjecture/
204•m-hodges•10h ago•180 comments

From Geometry to Algebra and Back Again: 4000 Years of Papers (2023) [video]

https://www.youtube.com/watch?v=1cRFfYQYGxE
27•surprisetalk•1d ago•0 comments

Cekura (YC F24) Is Hiring

https://www.ycombinator.com/companies/cekura-ai/jobs/AiWwUxI-forward-deployed-engineer-us
1•atarus•12h ago

North Korean nuclear test sets off years of earthquakes

https://www.science.org/content/article/north-korean-nuclear-test-sets-years-earthquakes
180•rbanffy•9h ago•151 comments

Mathematicians Build Long-Awaited Graph Sandwich

https://www.quantamagazine.org/mathematicians-build-long-awaited-graph-sandwich-20260918/
69•ibobev•9h ago•18 comments

The scourge of x86 emulation

https://fex-emu.com/Scourge-of-emulation/
273•dagmx•20h ago•80 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?