frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

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

https://github.com/postmanlabs/postman-app-support/issues/14370
625•sidgarimella•2h ago•200 comments

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

https://simonwillison.net/2026/Nov/3/qwen-can-interpret-model-weights/
265•theanonymousone•2h ago•75 comments

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

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

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

https://neufangled.com/
101•nharada•3h ago•46 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...
284•bookofjoe•1d ago•113 comments

Introduction to Programming in ATS

https://ats-lang.sourceforge.net/DOCUMENT/INT2PROGINATS/HTML/book1.html
11•ibobev•33m ago•1 comments

Mac at Any Scale

https://namespace.so/blog/mac-at-any-scale
220•anner_•5h ago•115 comments

OpenAI seems to be silently re-enabling model training on Codex chats

320•user052919•5h ago•94 comments

Kalshi and its co-founders face felony charges for violating Utah gambling laws

https://arstechnica.com/tech-policy/2026/10/trump-admin-sues-utah-to-save-kalshi-from-the-states-...
298•rbanffy•4h ago•215 comments

Preparing for the Flipper One Kickstarter and opening pre-orders

https://flipper.net/pages/flipper-one
10•user_7832•27m ago•2 comments

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

https://honnibal.dev/blog/astra-read-write-misleading
778•syllogism•7h ago•180 comments

Ashby (YC W19) Is Hiring EMs

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

I use AI (Oct 2026)

https://ben.stolovitz.com/posts/how-use-ai-oct-2026/
24•citelao•1h ago•28 comments

USDB: Scaling Storage for Next-Generation Recommender Systems at ByteDance

https://arxiv.org/abs/2611.02618
29•1equalsequals1•3h ago•5 comments

Gitbook Breached

99•punchmesan•3h ago•25 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
85•benbreen•1d ago•12 comments

We're Training a Figma-Fluent Editing Model

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

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

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

Study estimates 75% of NFL players who died over 15-year span had CTE

https://www.nbcnews.com/health/health-news/study-estimates-75-nfl-players-died-15-year-span-may-c...
194•gmays•4h ago•132 comments

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

https://nicholas.carlini.com/writing/2026/algorithmic-improvements-chess.html
362•markusw•12h ago•157 comments

Tiny Basic for Arduino

https://dilshan.github.io/tiny-basic/
49•AlexeyBrin•4h ago•12 comments

Google will turn off search for schools that reject AI

https://www.nytimes.com/2026/11/03/us/google-search-schools-restrict-ai.html
370•ceejayoz•4h ago•285 comments

Show HN: HackerChurn – which SaaS tools HN wants to cancel

https://hissingkitty.com/hacker-churn
56•drewlem•4h ago•21 comments

Queen of the Bagel Business

https://thehustle.co/originals/the-unlikely-queen-of-the-bagel-business
14•qi104104•1d ago•0 comments

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

https://jivx.com/yt
46•momentmaker•5h ago•14 comments

Handles are the better pointers (2018)

https://floooh.github.io/2018/06/17/handles-vs-pointers.html
34•vinhnx•5h ago•18 comments

How to write comparison content that doesn't age like milk

https://posthog.com/blog/comparison-content-guide
14•rbaudibert•2h ago•3 comments

Why Don't We Live in an Art Nouveau World?

https://asteriskmag.com/issues/16/why-don-t-we-life-in-an-art-nouveau-world
92•shcallaway•1d ago•87 comments

Katamari Damacy but it's The Met collection

https://katamari.vaguespac.es/
136•thebigship•1d ago•43 comments

Toit v2.0.0

https://toit.io/blog/toit-v2-0-0/
206•floitsch•2d ago•68 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?