frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Keep Android Open

https://f-droid.org/2026/02/20/twif.html
1539•LorenDB•17h ago•571 comments

Andrej Karpathy talks about "Claws"

https://simonwillison.net/2026/Feb/21/claws/
56•helloplanets•1h ago•46 comments

Acme Weather

https://acmeweather.com/blog/introducing-acme-weather
55•cryptoz•3h ago•34 comments

Turn Dependabot off

https://words.filippo.io/dependabot/
474•todsacerdoti•13h ago•127 comments

I found a Vulnerability. They found a Lawyer

https://dixken.de/blog/i-found-a-vulnerability-they-found-a-lawyer
616•toomuchtodo•15h ago•278 comments

Facebook is cooked

https://pilk.website/3/facebook-is-absolutely-cooked
1114•npilk•16h ago•600 comments

Trunk Based Development

https://trunkbaseddevelopment.com/
40•handfuloflight•3h ago•35 comments

Ggml.ai joins Hugging Face to ensure the long-term progress of Local AI

https://github.com/ggml-org/llama.cpp/discussions/19759
741•lairv•21h ago•181 comments

EU mandates replaceable batteries by 2027 (2023)

https://environment.ec.europa.eu/news/new-law-more-sustainable-circular-and-safe-batteries-enters...
89•cyrusmg•2h ago•52 comments

Wikipedia deprecates Archive.today, starts removing archive links

https://arstechnica.com/tech-policy/2026/02/wikipedia-bans-archive-today-after-site-executed-ddos...
454•nobody9999•16h ago•272 comments

I Verified My LinkedIn Identity. Here's What I Handed Over

https://thelocalstack.eu/posts/linkedin-identity-verification-privacy/
47•ColinWright•3h ago•15 comments

CERN rebuilt the original browser from 1989 (2019)

https://worldwideweb.cern.ch
184•tylerdane•11h ago•65 comments

Understanding Std:Shared_mutex from C++17

https://www.cppstories.com/2026/shared_mutex/
10•ibobev•3d ago•0 comments

LibreOffice blasts OnlyOffice for working with Microsoft to lock users in

https://www.neowin.net/news/libreoffice-blasts-fake-open-source-onlyoffice-for-working-with-micro...
44•XzetaU8•2h ago•20 comments

Coccinelle: The Linux kernel's source-to-source transformation tool

https://github.com/coccinelle/coccinelle
13•anon111332142•2h ago•0 comments

Lean 4: How the theorem prover works and why it's the new competitive edge in AI

https://venturebeat.com/ai/lean4-how-the-theorem-prover-works-and-why-its-the-new-competitive-edg...
37•tesserato•3d ago•20 comments

Gitas – A tool for Git account switching

https://github.com/letmutex/gitas
14•letmutex•4d ago•5 comments

The bare minimum for syncing Git repos

https://alexwlchan.net/2026/bare-git/
3•speckx•3d ago•0 comments

What Is OAuth?

https://leaflet.pub/p/did:plc:3vdrgzr2zybocs45yfhcr6ur/3mfd2oxx5v22b
128•cratermoon•9h ago•38 comments

Every company building your AI assistant is now an ad company

https://juno-labs.com/blogs/every-company-building-your-ai-assistant-is-an-ad-company
192•ajuhasz•16h ago•101 comments

Cord: Coordinating Trees of AI Agents

https://www.june.kim/cord
100•gfortaine•9h ago•42 comments

24 Hour Fitness won't let you unsubscribe from marketing spam, so I fixed it

https://ahmedkaddoura.com/projects/24hf-unsubscribe
50•daem•2h ago•12 comments

Index, Count, Offset, Size

https://tigerbeetle.com/blog/2026-02-16-index-count-offset-size/
89•ingve•3d ago•26 comments

Large Language Model Reasoning Failures

https://arxiv.org/abs/2602.06176
7•T-A•2h ago•2 comments

Blue light filters don't work – controlling total luminance is a better bet

https://www.neuroai.science/p/blue-light-filters-dont-work
171•pminimax•16h ago•183 comments

When etcd crashes, check your disks first

https://nubificus.co.uk/blog/etcd/
9•_ananos_•3h ago•3 comments

Show HN: Mines.fyi – all the mines in the US in a leaflet visualization

https://mines.fyi/
81•irasigman•13h ago•42 comments

OpenScan

https://openscan.eu/pages/scan-gallery
161•joebig•14h ago•10 comments

The path to ubiquitous AI (17k tokens/sec)

https://taalas.com/the-path-to-ubiquitous-ai/
747•sidnarsipur•1d ago•414 comments

Trump's global tariffs struck down by US Supreme Court

https://www.bbc.com/news/live/c0l9r67drg7t
1406•blackguardx•19h ago•1146 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•9mo ago

Comments

balloob•9mo 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•9mo ago
Discussion for the other article in the series:

https://news.ycombinator.com/item?id=44011381

tomhow•9mo ago
Comments moved thither. Thanks!
pabs3•9mo ago
They are two different articles, I don't think that was correct.
tomhow•9mo 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•9mo ago
Thanks for the response, guess that makes sense.
pabs3•9mo 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?