frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

macOS Container Machines

https://github.com/apple/container/blob/main/docs/container-machine.md
641•timsneath•7h ago•237 comments

Claude Fable 5

https://www.anthropic.com/news/claude-fable-5-mythos-5
2141•Philpax•14h ago•1656 comments

Upcoming breaking changes for npm v12

https://github.blog/changelog/2026-06-09-upcoming-breaking-changes-for-npm-v12/
330•plasma•10h ago•117 comments

How do you design a $30k electric pickup? Inside Ford's skunkworks

https://arstechnica.com/cars/2026/05/how-do-you-design-a-30000-electric-pickup-inside-fords-skunk...
14•PaulHoule•2d ago•1 comments

German ruling declares Google liable for false answers in AI Overviews

https://the-decoder.com/landmark-german-ruling-declares-googles-ai-overviews-are-googles-own-word...
422•ahlCVA•6h ago•235 comments

Vibe coding my way to a healthy family: Introducing Gamow Labs

https://www.ddmckinnon.com/2026/06/09/vibe-coding-my-way-to-a-healthy-family-introducing-gamow-labs/
77•dmckinno•4h ago•20 comments

RIP software hackathons. Long live the hardware hackathon

https://blog.oscars.dev/posts/rip-software-hackathons-long-live-the-hardware-hackathon/
142•ozcap•9h ago•62 comments

Rich Sutton on AI creativity and discovery

https://twitter.com/RichardSSutton/status/2061216087744946656
92•yimby•5h ago•50 comments

Ultrafast machine learning on FPGAs via Kolmogorov-Arnold Networks

https://aarushgupta.io/posts/kan-fpga/
215•ag2718•12h ago•30 comments

The oldest surviving animated feature film at 100

https://www.bbc.com/culture/article/20260603-how-a-26-year-old-german-woman-made-the-worlds-oldes...
87•1659447091•3d ago•11 comments

What it feels like to work with Mythos

https://www.oneusefulthing.org/p/what-it-feels-like-to-work-with-mythos
249•swolpers•14h ago•214 comments

More Molly Guards

https://unsung.aresluna.org/more-molly-guards/
106•zdw•3d ago•11 comments

Surprise, Pay $1000

https://forestwalk.ai/blog/surprise-blacksmith-costs/
110•apike•9h ago•35 comments

If Claude Fable stops helping you, you'll never know

https://jonready.com/blog/posts/claude-fable5-is-allowed-to-sabotage-your-app-if-youre-a-competit...
756•mips_avatar•10h ago•371 comments

Premature Optimization Is Fun Sometimes

https://invlpg.com/posts/2025-06-19-premature-optimization.html
21•throawayonthe•1d ago•5 comments

OpenCV 5 Is Here: The Biggest Leap in Years for Computer Vision

https://opencv.org/opencv-5/
749•ternaus•4d ago•133 comments

Lies we tell ourselves about email addresses

https://gitpush--force.com/commits/2026/06/lies-we-tell-ourselves-about-email/
103•theanonymousone•1d ago•75 comments

Google Chrome is killing all uBlock Origin bypasses, Edge, Opera to follow

https://www.neowin.net/news/google-chrome-is-killing-all-ublock-origin-bypasses-microsoft-edge-op...
161•d3Xt3r•2h ago•123 comments

Let's Encrypt bans certificate usage in any US sanctioned territory [pdf]

https://letsencrypt.org/documents/LE-SA-v1.7-June-04-2026-diff.pdf
396•piskov•1d ago•331 comments

CEOs who think AI replaces their employees are just bad CEOs

https://www.techdirt.com/2026/06/09/ceos-who-think-ai-replaces-their-employees-are-just-bad-ceos/
619•speckx•13h ago•233 comments

A giant star may have destroyed itself in one of the rarest explosions

https://phys.org/news/2026-05-giant-star-destroyed-universe-rarest.html
184•wglb•1d ago•26 comments

Test-case reducers are underappreciated debugging tools

https://tratt.net/laurie/blog/2026/test_case_reducers_are_underappreciated_debugging_tools.html
112•ltratt•20h ago•13 comments

Grit: Rewriting Git in Rust with agents

https://blog.gitbutler.com/true-grit
127•cbrewster•11h ago•173 comments

Launch HN: Transload (YC P26) – Measuring freight items with CCTV

47•nils_spatial•15h ago•15 comments

Computer Lessons

https://technicshistory.com/2026/06/06/computer-lessons/
7•cfmcdonald•1d ago•0 comments

Making Graphics Like it's 1993

https://staniks.github.io/articles/catlantean-3d-blog-1/
847•sklopec•21h ago•144 comments

Value Numbering

https://bernsteinbear.com/blog/value-numbering/
22•surprisetalk•1d ago•0 comments

WWDC 2026: Apple is Folding

https://cupertinolens.com/2026/06/09/wwdc-2026-apple-is-folding/
217•brandonb•17h ago•244 comments

Exif Smuggling (2025)

https://github.com/signalblur/exifsmugglingpoc
81•rolph•10h ago•24 comments

Show HN: Gravity – Interactive solar-system simulator, from Newton to Einstein

https://qunabu.github.io/Gravity/
168•qunabu•20h ago•37 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?