frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

There's no point at which turning your brain off will work

https://danluu.com/brain-off/
94•robin_reala•50m ago•59 comments

Cloudflare Quick Tunnels

https://try.cloudflare.com/
255•jcbhmr•3h ago•129 comments

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

https://donjon.ledger.com/blog/rp2350-secure-debug-laser-fault-injection/
26•synack•59m ago•6 comments

An Empirical Study of Harness Design for Coding Agents

https://arxiv.org/abs/2609.20804
178•wek•4h ago•40 comments

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

https://cactuscompute.com/needle
54•HenryNdubuaku•17h ago•20 comments

North Korean nuclear test sets off years of earthquakes

https://www.science.org/content/article/north-korean-nuclear-test-sets-years-earthquakes
97•rbanffy•3h ago•77 comments

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

https://www.sandordargo.com/blog/2026/09/16/cpp26-trivial-infinite-loops
68•ibobev•21h ago•104 comments

OpenJev

https://openjev.com/
402•ilreb•8h ago•210 comments

Mathematicians Build Long-Awaited Graph Sandwich

https://www.quantamagazine.org/mathematicians-build-long-awaited-graph-sandwich-20260918/
32•ibobev•3h ago•6 comments

I vibed a proof of Conway's conjecture

https://overreacted.io/how-i-vibed-a-proof-of-conways-conjecture/
118•m-hodges•3h ago•109 comments

A heap overflow and SSO misconfiguration to compromise OpenAI internal repos

https://www.hacktron.ai/blog/hacking-openai
429•Handy-Man•15h ago•181 comments

I don't like passkeys

https://hawksley.dev/blog/i-dont-like-passkeys
554•ethanhawksley•5h ago•539 comments

GrassLobster: AI Agentic Generation of Parametric Geometry Workflows

https://www.miro.vision/index.php/2026/09/17/grasslobbster/
22•aidog•2h ago•3 comments

Jemalloc 5.4.0

https://github.com/jemalloc/jemalloc/releases/tag/5.4.0
295•gkfasdfasdf•13h ago•76 comments

US Treasuries Have Become Unappetizing for Foreign Central Banks and Governments

https://wolfstreet.com/2026/09/17/treasuries-have-become-badly-unappetizing-for-foreign-central-b...
105•iamnothere•2h ago•64 comments

NATS publishes preliminary report on technical incident of 8 September

https://www.nats.aero/news/nats-publishes-preliminary-report-on-technical-incident-of-8-september/
36•asplake•4h ago•23 comments

Cekura (YC F24) Is Hiring

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

The Shadows Lurking in the Equations – Underwater Islands

https://gods.art/articles/equation_shadows
52•vismit2000•2d ago•9 comments

Show HN: Scry, programmable internet search w/ congestion pricing

https://scry.io/
15•Xyra•18h ago•3 comments

The scourge of x86 emulation

https://fex-emu.com/Scourge-of-emulation/
247•dagmx•13h ago•68 comments

BeanShell3 in Development

https://beanshell.github.io/home.html
24•jimjag•3h ago•13 comments

Bonsai 2 27B: Near-Lossless Compression in a 9x Smaller Footprint

https://prismml.com/news/bonsai-2-27b
546•JonSchneider•20h ago•176 comments

Warren Buffett Steps Down as Berkshire Chairman, Names Son to Replace Him

https://www.nytimes.com/2026/09/18/business/warren-buffett-berkshire-chairman.html
235•saimiam•6h ago•156 comments

Build Faster Feedback Loops Using Qualitative User Research

https://blog.nseldeib.com/p/build-faster-feedback-loops-using
19•nadis•2h ago•1 comments

Qwen 3.8 Omni Flash

https://qwen.ai/blog?id=qwen3.8-omni-flash
312•jjcm•18h ago•118 comments

Second Circuit Allows Government to Search Electronic Devices at the Border

https://knightcolumbia.org/content/second-circuit-allows-government-to-search-electronic-devices-...
78•HotGarbage•3h ago•44 comments

How to Write with an LLM

https://sockpuppet.org/blog/2026/09/17/how-to-write-with-an-llm/
283•joeriddles•20h ago•194 comments

Pre-Greek: The lost language hidden within Ancient Greek

https://linguisticdiscovery.com/posts/pre-greek/
145•axiologist•14h ago•61 comments

Microsoft exec called AI scraping 'the largest theft of labor in human history'

https://techcrunch.com/2026/09/17/microsoft-exec-called-ai-scraping-the-largest-theft-of-labor-in...
748•pluc•8h ago•646 comments

When the fractional part of a float fixes your shader

https://crocidb.com/post/when-the-fractional-part-of-a-float-fixes-your-shader/
92•vinhnx•2d ago•16 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?