frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Saving 100 terabytes of memory by optimizing 1.1.1.1's DNS cache

https://blog.cloudflare.com/dns-cache-memory-optimization-1111/
167•TangerineDream•1h ago•42 comments

507 Mechanical Movements

https://507movements.com/
338•helloplanets•5h ago•48 comments

Small Models Have Arrived

https://calv.info/small-models-have-arrived
196•tosh•3h ago•85 comments

Gemini Omni 1.1 Flash

https://blog.google/innovation-and-ai/technology/developers-tools/build-with-gemini-omni-1-1-flash/
67•saretup•2h ago•13 comments

We found a division by zero bug in FFmpeg with a vibecoded fuzzer

https://code.ffmpeg.org/FFmpeg/FFmpeg/issues/24290
30•dclavijo•1h ago•20 comments

Decompiling a Nintendo 64 game in 84 days

https://blog.chrislewis.au/decompiling-a-nintendo-64-game-in-84-days/
94•knackers•4h ago•30 comments

M5Stack Launches PaperMono

https://shop.m5stack.com/blogs/news/m5stack-launches-papermono-a-compact-e-ink-development-termin...
25•marksully•1h ago•5 comments

Microduck

https://pollen-robotics.com/microduck/
374•robotswantdata•8h ago•145 comments

Suica, Japan's First IC Transit Card

https://www.tokyodev.com/articles/the-story-of-suica
89•zdw•3h ago•75 comments

Bild AI (YC W25) is hiring product and AI engineers

https://www.bild.ai/jobs
1•rooppal•2h ago

Previewing the Model Hardware Standard

https://www.anthropic.com/news/model-hardware-standard-research-preview
15•surprisetalk•1h ago•7 comments

Emacs 31: An unofficial guide to Markdown-ts-mode

https://rahuljuliato.com/posts/markdown-ts-mode-emacs-31
121•RahulMJ•5h ago•49 comments

Autism mutations drive neurodevelopmental pathology

https://www.science.org/doi/10.1126/science.ady4523
8•slantedview•46m ago•0 comments

The turbulent AI era is here

https://www.gatesnotes.com/work/make-ai-work-for-everyone/reader/a-turbulent-ai-era-and-critical-...
84•nanna•1d ago•331 comments

Launching Route 53 Files

https://www.daemonology.net/blog/2026-08-27-Launching-Route-53-Files.html
64•louis-paul•4h ago•24 comments

Launch HN: Salem Robotics (YC S26) – Software for industrial inspection robots

27•Salem_robotics•3h ago•17 comments

Nvidia Starts Pac as AI Chip Maker Builds DC Influence Force

https://news.bgov.com/bloomberg-government-news/nvidia-starts-a-pac-as-ai-chip-maker-buids-influe...
8•rarisma•35m ago•1 comments

Afterglow: Run classic After Dark screen savers on modern macOS

https://morphing.cloud/afterglow/
12•NaOH•18h ago•2 comments

Engineered yeast for converting plastic and biomass compounds into food

https://acs.digitellinc.com/live/37/session/586399
33•ehwa37•3h ago•25 comments

Nvidia agrees to acquire Hugging Face for $13B

https://www.businessinsider.com/nvidia-in-talks-to-buy-hugging-face-13-billion-dollars-2026-8
1747•mfiguiere•17h ago•815 comments

Show HN: The load-bearing vocabulary of Claude

https://louisabraham.github.io/load-bearing/
173•Labo333•10h ago•89 comments

A curmudgeon tries a language server

https://entropicthoughts.com/curmudgeon-tries-language-server
90•crescit_eundo•1d ago•55 comments

Aphantasia Beginner's Guide

https://aphantasia.com/guide
62•ksec•5h ago•163 comments

The terrifying mechanics of the Nepali flash flood

https://www.economist.com/science-and-technology/2026/08/27/the-terrifying-mechanics-of-the-nepal...
25•vinni2•3h ago•0 comments

Show HN: My Claude quota ran out in 10 minutes, so I made a tool to find out why

https://github.com/kelviq/tare
46•sachinneravath•2h ago•39 comments

Why HPSC Is a Big Deal for Space Exploration

https://www.windriver.com/blog/Why-HPSC-Is-a-Big-Deal-for-Space-Exploration
19•mooreds•3h ago•6 comments

Two German airport workers die of malaria after 'mosquito arrives on plane'

https://www.bbc.com/news/articles/cz6zwgg9y8go
102•vinni2•1h ago•51 comments

Trade (and Tariffs)

https://xkcd.com/3290/
333•throw0101d•5h ago•137 comments

Show HN: Yet another minimal and lightweight terminal multiplexer written in Go.

https://github.com/patriceckhart/hrdx
12•patriceckhart•1h ago•5 comments

Humanity has the debate about AI consciousness backwards

https://economist.com/by-invitation/2026/08/20/humanity-has-the-debate-about-ai-consciousness-bac...
42•semiquaver•16h ago•132 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?