frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Jelly Sheet

https://mrdoob.github.io/codevember-2026/01/
207•memalign•5h ago•48 comments

C++26 Disapproved

https://andreasfertig.com/blog/2026/11/cpp26-dis-failed-how-does-cpp-survive/
269•thatxliner•8h ago•156 comments

Jailbreaking my car's navigation system just so I can change the time

https://blog.nns.ee/2026/11/02/renault-hack/
782•xx_ns•1d ago•312 comments

Stringman, an $800 open-source room scale gripper robot

https://neufangled.com/
566•nharada•15h ago•193 comments

The lost malloc()

https://napcakes.nekoweb.org/posts/malloc/
13•matt_d•1h ago•2 comments

The Internals of PostgreSQL

https://www.interdb.jp/pg/index.html
257•ibobev•10h ago•18 comments

Distinct cellular and genetic differences in colorectal cancer in young patients

https://www.dana-farber.org/newsroom/news-releases/2026/study-reveals-distinct-cellular-and-genet...
65•gmays•5h ago•7 comments

Show HN: Uncracked City, detective game where you question LLM suspects that lie

https://uncracked.city
46•passkey1510•11h ago•16 comments

Giant canyon on Mars is still tectonically active

https://lamont.columbia.edu/news/giant-canyon-mars-still-tectonically-active-today
77•gmays•7h ago•8 comments

Show HN: HackerTV – HN's most-recommended Youtube videos as 24/7 TV channels

https://hackertv.org
312•dsalzman•1d ago•65 comments

Arrows to arrows, categories to queries (2025)

https://reasonablypolymorphic.com/blog/arrows-to-arrows/
42•firstbase•5h ago•2 comments

Fujifilm to boost tape production 5x as AI fuels archiving demand

https://arstechnica.com/gadgets/2026/10/fujifilm-to-boost-tape-production-5x-as-ai-fuels-archivin...
462•bookofjoe•1d ago•192 comments

Japan's Jimi 'Mundane' Halloween Costumes of 2026

https://spoon-tamago.com/japan-jimi-mundane-halloween-costumes-2026/
184•zdw•2d ago•32 comments

Qwen 3.8 27B on my laptop can interpret model weights, too

https://simonwillison.net/2026/Nov/3/qwen-can-interpret-model-weights/
603•theanonymousone•15h ago•178 comments

Safari introduces Adaptive Dark Mode in 27.3

https://webkit.org/blog/18541/introducing-adaptive-dark-mode/
416•paddingtone•11h ago•222 comments

Postman silently auto-installs AI plugins and attempts to share all API data

https://github.com/postmanlabs/postman-app-support/issues/14370
1240•sidgarimella•15h ago•408 comments

We're training a Figma-fluent editing model

https://www.figma.com/blog/training-a-figma-fluent-editing-model/
115•gmays•3d ago•49 comments

How I use AI (Oct 2026)

https://ben.stolovitz.com/posts/how-use-ai-oct-2026/
161•citelao•14h ago•145 comments

Why Clip Art Was Everywhere Until It Wasn't [video]

https://www.youtube.com/watch?v=XfLlpxE6AYM
36•surprisetalk•20h ago•10 comments

There is no posttraining data commons

https://openathena.ai/blog/there-is-no-posttraining-data-commons/
66•lukasschwab•17h ago•21 comments

The Little Book of Generative AI Foundations: An Intuitive Mathematical Primer

https://arxiv.org/abs/2605.29713
331•ibobev•11h ago•51 comments

Show HN: Kairos – Open-source risk and fraud decisioning platform

https://github.com/finic-ai/kairos
89•ayanb9440•11h ago•22 comments

Microsoft fixes a Windows 11 annoyance as PC revenue declines

https://arstechnica.com/gadgets/2026/10/windows-11-gets-right-click-menu-improvements-as-pc-reven...
70•rbanffy•19h ago•167 comments

AI stocks slide as Texas governor result raises data center risks

https://www.cnbc.com/2026/11/04/ai-stocks-texas-governor-data-centers.html
15•1659447091•1h ago•3 comments

Curiosity Traps

https://www.autodidacts.io/curiosity-traps/
74•surprisetalk•1d ago•8 comments

The 'Astra can read and write weights to improve Qwen' post is misleading

https://honnibal.dev/blog/astra-read-write-misleading
969•syllogism•20h ago•201 comments

Mac at any scale

https://namespace.so/blog/mac-at-any-scale
376•anner_•17h ago•211 comments

Introduction to Programming in ATS

https://ats-lang.sourceforge.net/DOCUMENT/INT2PROGINATS/HTML/book1.html
72•ibobev•13h ago•9 comments

Union Types and Option Types (2025)

https://tibleiz.net/blog/2025-03-16-union-types-and-option-types.html
43•g0xA52A2A•1d ago•18 comments

Writing seen in PHerc. 306B, for the first time in 2000 years

https://scrollprize.substack.com/p/writing-seen-in-pherc-306b-for-the
128•benbreen•1d ago•18 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?