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/
490•TangerineDream•7h ago•135 comments

Small Models Have Arrived

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

507 Mechanical Movements

https://507movements.com/
459•helloplanets•11h ago•67 comments

Show HN: OpenTIE and OpenXWA, Modern Ports of Tie Fighter and X-Wing Alliance

https://github.com/elyosh/OpenTIE/
48•elyosh•2h ago•12 comments

Terminal-Bench-Science: Evaluating AI agents on scientific research workflows

https://www.terminal-bench-science.ai/announcement
13•matt_d•1h ago•3 comments

Gemini-3.5-Transcribe

https://blog.google/innovation-and-ai/models-and-research/gemini-models/gemini-3-5-transcribe/
139•k9294•7h ago•33 comments

Show HN: We built open OpenRouter that turns usage into a better model

https://github.com/experientiallabs/experiential
91•SilenN•3h ago•13 comments

AI Engineer Notebooks – free, framework-free RAG/agents/evals on Colab

https://github.com/calmrocks/ai-engineer-notebooks
39•calmrocks•3h ago•0 comments

Microduck

https://pollen-robotics.com/microduck/
500•robotswantdata•14h ago•182 comments

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

https://code.ffmpeg.org/FFmpeg/FFmpeg/issues/24290
171•dclavijo•7h ago•133 comments

The turbulent AI era is here

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

Select * from Internet.blogposts

https://pfrazee.leaflet.pub/3mu3p2smmis22
32•mmattbtw•2h ago•8 comments

M5Stack Launches PaperMono

https://shop.m5stack.com/blogs/news/m5stack-launches-papermono-a-compact-e-ink-development-termin...
86•marksully•7h ago•36 comments

Decompiling a Nintendo 64 game in 84 days

https://blog.chrislewis.au/decompiling-a-nintendo-64-game-in-84-days/
174•knackers•10h ago•111 comments

Show HN: The load-bearing vocabulary of Claude

https://louisabraham.github.io/load-bearing/
338•Labo333•16h ago•161 comments

Previewing the Model Hardware Standard

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

Afterglow: Run classic After Dark screen savers on modern macOS

https://morphing.cloud/afterglow/
86•NaOH•1d ago•34 comments

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

https://rahuljuliato.com/posts/markdown-ts-mode-emacs-31
150•RahulMJ•11h ago•64 comments

Suica, Japan's First IC Transit Card

https://www.tokyodev.com/articles/the-story-of-suica
185•zdw•9h ago•156 comments

Meta Paid $17B – Gets to Write Safety Rules for Other SocMedia Platform

https://www.techdirt.com/2026/08/26/meta-just-paid-nearly-17-billion-to-make-sure-it-gets-to-writ...
125•ano-ther•4h ago•26 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
1827•mfiguiere•23h ago•855 comments

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

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

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

40•Salem_robotics•9h ago•25 comments

Engineered yeast for converting plastic and biomass compounds to food additives

https://acs.digitellinc.com/live/37/session/586399
80•ehwa37•9h ago•58 comments

Show HN: Voronoi Go

https://voronoigo.com/
81•igpay•7h ago•11 comments

Gemini Omni 1.1 Flash

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

The mechanics of the Nepali flash flood

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

MIT's Ad Hoc Committee on AI Use in Teaching, Learning, and Research Training

https://aiandeducation.mit.edu/report/
110•pbui•12h ago•71 comments

Aphantasia Beginner's Guide

https://aphantasia.com/guide
128•ksec•11h ago•291 comments

Doctors are finally learning to manage antidepressant withdrawal

https://www.newscientist.com/article/2584861-antidepressant-withdrawal-symptoms-are-prompting-a-r...
59•eutropheon•2h ago•63 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?