frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Claude Sonnet 5

https://www.anthropic.com/news/claude-sonnet-5
1019•marinesebastian•11h ago•586 comments

Claude Code is steganographically marking requests

https://thereallo.dev/blog/claude-code-prompt-steganography
1650•kirushik•14h ago•474 comments

The first early human eggs from stem cells

https://www.conception.bio/science-and-updates/the-first-early-human-eggs-from-stem-cells
18•dsr12•44m ago•2 comments

Matrix Orthogonalization Improves Memory in Recurrent Models

https://ayushtambde.com/blog/matrix-orthogonalization-improves-memory-in-recurrent-models/
12•at2005•40m ago•0 comments

Google copybara: moving code between repositories

https://github.com/google/copybara
148•reconnecting•6h ago•20 comments

Department of Commerce has lifted export controls on Claude Fable 5 and Mythos 5

https://twitter.com/AnthropicAI/status/2072106151890809341
510•Pragmata•5h ago•261 comments

Claude Science

https://claude.com/product/claude-science
429•lebovic•12h ago•131 comments

Forestiere Underground Gardens

https://en.wikipedia.org/wiki/Forestiere_Underground_Gardens
48•onemoresoop•4h ago•8 comments

Nano Banana 2 Lite

https://deepmind.google/models/gemini-image/flash-lite/
339•minimaxir•13h ago•140 comments

Pystd, similar-ish functionality with a fraction of the compile time

https://nibblestew.blogspot.com/2026/06/pystd-standard-library-similar-ish.html
9•ibobev•4d ago•2 comments

Leanstral 1.5

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

How does a pull-back car work? Illustrated teardown

https://mechanical-pencil.com/products/car
153•Muhammad523•2d ago•30 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
139•alok-g•8h ago•71 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/
173•HelloUsername•1d ago•42 comments

I ported Kubernetes to the browser

https://ngrok.com/blog/i-ported-kubernetes-to-the-browser
217•peterdemin•9h ago•70 comments

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

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

Hatari – Online Atari ST/STE/TT/Falcon Emulator

https://hatari.frama.io/hatari/online/hatari.html
50•gregsadetsky•7h ago•4 comments

Segmenting Robot Video into Actionable Subtasks

https://macrodata.co/blog/annotating-robot-video-subtasks
11•tomaspduarte•1d ago•2 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-...
109•zdw•10h ago•21 comments

I built a mmWave material classification radar (2025)

https://gauthier-lechevalier.com/radar
164•GL26•12h ago•40 comments

Scaling Laws, Carefully

https://lilianweng.github.io/posts/2026-06-24-scaling-laws/
44•tehnub•4d ago•13 comments

Deriving the SVD (Single Value Decomposition) from scratch

https://stillthinking.net/posts/connections-in-math-svd/
24•pcael•2d ago•9 comments

Building a custom octocopter from scratch with no prior hardware experience

https://karolina.mgdubiel.com/drone/
345•noleary•3d ago•73 comments

Stroustrup's Rule (2024)

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

How employment changes when firms adopt generative AI

https://ramp.com/data/ai-jobs-impact
20•nreece•1h ago•9 comments

TabFM: A zero-shot foundation model for tabular data

https://research.google/blog/introducing-tabfm-a-zero-shot-foundation-model-for-tabular-data/
64•brandonb•7h ago•8 comments

ArXiv's Next Chapter

https://blog.arxiv.org/2026/06/30/arxivs-next-chapter/
15•subset•3h ago•0 comments

Long Island's decommissioned nuclear power plant

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

Have you restarted your computer this week?

https://taonaw.com/2026/06/27/have-you-restarted-your-computer.html
143•surprisetalk•15h ago•246 comments

Knoppix

https://www.knopper.net/knoppix/index-en.html
281•hoangvmpc•17h ago•109 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?