frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Claude Sonnet 5

https://www.anthropic.com/news/claude-sonnet-5
758•marinesebastian•4h ago•419 comments

Claude Code is steganographically marking requests

https://thereallo.dev/blog/claude-code-prompt-steganography
1221•kirushik•6h ago•323 comments

From brain waves to words: a new path to communication without surgery

https://ai.meta.com/blog/brain2qwerty-brain-ai-human-communication/?_fb_noscript=1
54•alok-g•1h ago•32 comments

Claude Science

https://claude.com/product/claude-science
309•lebovic•5h ago•106 comments

Nano Banana 2 Lite

https://deepmind.google/models/gemini-image/flash-lite/
267•minimaxir•5h ago•102 comments

How does a pull-back car work? Illustrated teardown

https://mechanical-pencil.com/products/car
57•Muhammad523•2d ago•14 comments

I built a mmWave material classification radar (2025)

https://gauthier-lechevalier.com/radar
115•GL26•5h ago•30 comments

I ported Kubernetes to the browser

https://ngrok.com/blog/i-ported-kubernetes-to-the-browser
96•peterdemin•1h ago•21 comments

Stroustrup's Rule (2024)

https://buttondown.com/hillelwayne/archive/stroustrups-rule/
30•bmacho•3d ago•2 comments

TabFM: A zero-shot foundation model for tabular data

https://research.google/blog/introducing-tabfm-a-zero-shot-foundation-model-for-tabular-data/
5•brandonb•28m ago•0 comments

Long Island's decommissioned nuclear power plant

https://nickcarr.com/scouting-a-decommissioned-nuclear-power-plant/
33•mkmk•6d ago•2 comments

CERN bids farewell to the LHC and enters Long Shutdown 3

https://home.cern/cern-bids-farewell-to-the-lhc-and-enters-long-shutdown-3/
66•HelloUsername•1d ago•16 comments

Waveloop: What Fable left me

https://neynt.ca/writing/waveloop/
65•personjerry•3d ago•14 comments

Building a custom octocopter from scratch with no prior hardware experience

https://karolina.mgdubiel.com/drone/
304•noleary•2d ago•68 comments

Understanding lattice risks: Many differences between marketing and reality

https://blog.cr.yp.to/20260630-risk.html
6•ledoge•1h ago•0 comments

Leanstral 1.5

https://docs.mistral.ai/models/model-cards/leanstral-1-5-26-06
16•vetronauta•1h ago•1 comments

Reading the internals of Postgres: Database cluster, databases, and tables

https://www.buraksen.dev/articles/internals-of-postgresql-db-cluster-and-tables
35•buraksen•1d ago•0 comments

Knoppix

https://www.knopper.net/knoppix/index-en.html
221•hoangvmpc•9h ago•93 comments

Show HN: My 13-year-old built an ant colony tracker

https://formicarium.es
21•abelgvidal•5h ago•14 comments

Memoirs of Extraordinary Popular Delusions and the Madness of Crowds (1852)

https://www.gutenberg.org/ebooks/24518
156•lstodd•9h ago•50 comments

RF hacking my cloud-controlled ceiling fan

https://samwilkinson.io/posts/2026-06-24-rf-hacking-dreo
25•sammycdubs•6d ago•10 comments

Have you restarted your computer this week?

https://taonaw.com/2026/06/27/have-you-restarted-your-computer.html
77•surprisetalk•8h ago•169 comments

Set up your own DoH (DNS over HTTPS) service

https://nochan.net/b/Internet-Crap/20260602-Set-Up-Your-Own-DoH-Service/
49•Bender•3d ago•22 comments

Tokyo has only two barley tea makers, we visited one to see how mugicha is made

https://soranews24.com/2026/06/30/tokyo-has-only-two-barley-tea-makers-and-we-visited-one-to-see-...
17•zdw•2h ago•5 comments

Ask HN: Since when does Craigslist's front page have emojis?

5•argee•38m ago•3 comments

I built a 10 inch mini rack from aluminium extrusions

https://louwrentius.com/i-build-a-10-inch-mini-rack-from-aluminium-extrusions.html
43•louwrentius•2d ago•17 comments

Amazon seller reveals glimpse of shadow bribery market

https://www.latimes.com/business/story/2026-06-30/shadow-bribery-market-inside-amazon-preys-on-de...
77•petethomas•4h ago•42 comments

Matrix URIs, a URL syntax from Tim Berners-Lee that never shipped (1996)

https://www.w3.org/DesignIssues/MatrixURIs.html
38•napolux•4d ago•24 comments

Ante: A new way to blend borrow checking and reference counting

https://verdagon.dev/blog/ante-blending-borrowing-rc
8•g0xA52A2A•2d ago•0 comments

Morbid: Debunking Modern Longevity Science

https://www.newyorker.com/magazine/2026/07/06/morbid-saul-justin-newman-book-review-eat-your-ice-...
33•nabbed•2h 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?