frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

The Internals of PostgreSQL

https://www.interdb.jp/pg/index.html
126•ibobev•4h ago•3 comments

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

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

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

https://neufangled.com/
395•nharada•9h ago•147 comments

Safari introduces Adaptive Dark Mode in 27.3

https://webkit.org/blog/18541/introducing-adaptive-dark-mode/
305•paddingtone•4h ago•189 comments

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

https://hackertv.org
180•dsalzman•1d ago•38 comments

Japan's Jimi 'Mundane' Halloween Costumes of 2026

https://spoon-tamago.com/japan-jimi-mundane-halloween-costumes-2026/
115•zdw•1d ago•19 comments

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

https://simonwillison.net/2026/Nov/3/qwen-can-interpret-model-weights/
497•theanonymousone•8h ago•155 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...
384•bookofjoe•1d ago•169 comments

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

https://arxiv.org/abs/2605.29713
244•ibobev•4h ago•39 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...
8•rbanffy•13h ago•4 comments

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

https://github.com/finic-ai/kairos
62•ayanb9440•5h ago•7 comments

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

https://github.com/postmanlabs/postman-app-support/issues/14370
1043•sidgarimella•8h ago•346 comments

There is no posttraining data commons

https://openathena.ai/blog/there-is-no-posttraining-data-commons/
31•lukasschwab•11h ago•7 comments

We're training a Figma-fluent editing model

https://www.figma.com/blog/training-a-figma-fluent-editing-model/
74•gmays•2d ago•35 comments

Introduction to Programming in ATS

https://ats-lang.sourceforge.net/DOCUMENT/INT2PROGINATS/HTML/book1.html
58•ibobev•6h ago•7 comments

US tech giants' hidden AI debt swells 90% to $3.2T in 6 months

https://asia.nikkei.com/business/technology/artificial-intelligence/us-tech-giants-hidden-ai-debt...
256•angry_impala•4h ago•115 comments

Curiosity Traps

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

How I use AI (Oct 2026)

https://ben.stolovitz.com/posts/how-use-ai-oct-2026/
89•citelao•8h ago•82 comments

Could a modern chess engine on a Pentium have defeated Kasparov in 1996?

https://nicholas.carlini.com/writing/2026/algorithmic-improvements-chess.html
454•markusw•18h ago•216 comments

Union Types and Option Types (2025)

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

macOS 27 does not support CoreStorage volumes

https://wadetregaskis.com/macos-27-golden-gate-does-not-actually-support-corestorage-or-hfs-volumes/
113•colejohnson66•6h ago•75 comments

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

https://honnibal.dev/blog/astra-read-write-misleading
910•syllogism•13h ago•191 comments

Ashby (YC W19) Is Hiring EMs

https://www.ashbyhq.com/careers?ashby_jid=695b1ce6-c375-4fad-94ef-61b50a3fbd28&utm_source=hn
1•abhikp•9h ago

Pratt parsing is a black box

https://vinipsmaker.github.io/blog/article/pratt-parsing-is-a-black-box/
41•ibobev•6h ago•17 comments

Killing what can't be handled – putting a spaghetti demon to eternal rest

https://themaister.net/blog/2026/10/29/killing-what-cant-be-handled-putting-a-spaghetti-demon-to-...
34•ibobev•1d ago•7 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
116•benbreen•1d ago•16 comments

Mac at any scale

https://namespace.so/blog/mac-at-any-scale
319•anner_•11h ago•187 comments

Preparing for the Flipper One Kickstarter and opening pre-orders

https://flipper.net/pages/flipper-one
172•user_7832•6h ago•79 comments

Antimony: CAD Software Evolved from Lisp Machines and Not Drafting Tables (2015)

https://www.mattkeeter.com/projects/antimony/3/
104•pmkary•1d ago•59 comments

Practice speaking Japanese with real YouTube videos, graded line by line

https://jivx.com/yt
89•momentmaker•11h ago•32 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?