frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Statement from Dario Amodei on our discussions with the Department of War

https://www.anthropic.com/news/statement-department-of-war
1635•qwertox•8h ago•840 comments

The Hunt for Dark Breakfast

https://moultano.wordpress.com/2026/02/22/the-hunt-for-dark-breakfast/
159•moultano•3h ago•56 comments

What Claude Code chooses

https://amplifying.ai/research/claude-code-picks
374•tin7in•13h ago•152 comments

Julia: Performance Tips

https://docs.julialang.org/en/v1/manual/performance-tips/
18•tosh•3d ago•4 comments

80386 Protection

https://nand2mario.github.io/posts/2026/80386_protection/
30•nand2mario•2d ago•4 comments

Layoffs at Block

https://twitter.com/jack/status/2027129697092731343
658•mlex•10h ago•689 comments

What does " 2>&1 " mean?

https://stackoverflow.com/questions/818255/what-does-21-mean
240•alexmolas•11h ago•130 comments

AirSnitch: Demystifying and breaking client isolation in Wi-Fi networks [pdf]

https://www.ndss-symposium.org/wp-content/uploads/2026-f1282-paper.pdf
348•DamnInteresting•15h ago•162 comments

I rendered 1,418 confusables over 230 fonts. Most aren't confusable to the eye

https://paultendo.github.io/posts/confusable-vision-visual-similarity/
37•paultendo•1d ago•14 comments

Parakeet.cpp – Parakeet ASR inference in pure C++ with Metal GPU acceleration

https://github.com/Frikallo/parakeet.cpp
30•noahkay13•3h ago•4 comments

Dear Time Lords: Freeze Computers in 1993

https://graydon2.dreamwidth.org/322461.html
60•zdw•3h ago•25 comments

Move tests to closed source repo

https://github.com/tldraw/tldraw/issues/8082
37•nilsbunger•1d ago•23 comments

Launch HN: Cardboard (YC W26) – Agentic video editor

https://www.usecardboard.com/
109•sxmawl•13h ago•58 comments

An Introduction to the Codex Seraphinianus, the Strangest Book Ever Published

https://www.openculture.com/2026/02/an-introduction-to-the-codex-seraphinianus.html
60•vinhnx•3d ago•13 comments

OsmAnd's Faster Offline Navigation (2025)

https://osmand.net/blog/fast-routing/
149•todsacerdoti•13h ago•48 comments

I baked a pie every day for a year

https://www.theguardian.com/lifeandstyle/2026/feb/22/a-new-start-after-60-i-baked-a-pie-every-day...
263•NaOH•3d ago•170 comments

Palm OS User Interface Guidelines (2003) [pdf]

https://cs.uml.edu/~fredm/courses/91.308-spr05/files/palmdocs/uiguidelines.pdf
181•spiffytech•14h ago•87 comments

LiteLLM (YC W23): Founding Reliability Engineer – $200K-$270K and 0.5-1.0% equity

https://www.ycombinator.com/companies/litellm/jobs/unlCynJ-founding-reliability-performance-engineer
1•ij23•6h ago

Smartphone market forecast to decline this year due to memory shortage

https://www.idc.com/resource-center/press-releases/wwsmartphoneforecast4q25/
223•littlexsparkee•9h ago•219 comments

Hydroph0bia – fixed SecureBoot bypass for UEFI firmware from Insyde H2O (2025)

https://coderush.me/hydroph0bia-part3/
55•transpute•9h ago•1 comments

The Origins of Agar

https://www.asimov.press/p/agar
3•surprisetalk•3d ago•0 comments

Museum of Plugs and Sockets

https://plugsocketmuseum.nl/index.html
107•ohjeez•3d ago•36 comments

BuildKit: Docker's Hidden Gem That Can Build Almost Anything

https://tuananh.net/2026/02/25/buildkit-docker-hidden-gem/
171•jasonpeacock•17h ago•62 comments

Show HN: Hacker Smacker – Spot great (and terrible) HN commenters at a glance

https://hackersmacker.org
111•conesus•2d ago•126 comments

Show HN: Deff – Side-by-side Git diff review in your terminal

https://github.com/flamestro/deff
96•flamestro•13h ago•54 comments

Two insider cases we've recently closed

https://news.kalshi.com/p/kalshi-trading-violation-enforcement-cases
23•fortran77•5h ago•49 comments

Understanding the Go Runtime: The Memory Allocator

https://internals-for-interns.com/posts/go-memory-allocator/
59•valyala•3d ago•10 comments

Show HN: Linex – A daily challenge: placing pieces on a board that fights back

https://www.playlinex.com/
60•Humanista75•2d ago•20 comments

This time is different

https://shkspr.mobi/blog/2026/02/this-time-is-different/
154•speckx•18h ago•244 comments

Nano Banana 2: Google's latest AI image generation model

https://blog.google/innovation-and-ai/technology/ai/nano-banana-2/
552•davidbarker•15h ago•517 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?