frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Claude Fable 5

https://www.anthropic.com/news/claude-fable-5-mythos-5
1694•Philpax•7h ago•1341 comments

Upcoming breaking changes for NPM v12

https://github.blog/changelog/2026-06-09-upcoming-breaking-changes-for-npm-v12/
157•plasma•3h ago•48 comments

Ultrafast machine learning on FPGAs via Kolmogorov-Arnold Networks

https://aarushgupta.io/posts/kan-fpga/
145•ag2718•5h ago•17 comments

AI misidentification results in wrongful arrest; man seeks justice

https://www.wsoctv.com/news/local/ai-misidentification-results-wrongful-arrest-man-seeks-justice/...
48•text0404•1h ago•12 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...
381•mips_avatar•3h ago•171 comments

Making Graphics Like it's 1993

https://staniks.github.io/articles/catlantean-3d-blog-1/
752•sklopec•13h ago•127 comments

RIP software hackathons. Long live the hardware hackathon

https://blog.oscars.dev/posts/rip-software-hackathons-long-live-the-hardware-hackathon/
26•ozcap•1h ago•3 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/
381•speckx•5h ago•154 comments

Exif Smuggling

https://github.com/signalblur/exifsmugglingpoc
46•rolph•3h ago•20 comments

Lies We Tell Ourselves About Email Addresses

https://gitpush--force.com/commits/2026/06/lies-we-tell-ourselves-about-email/
18•theanonymousone•1d ago•7 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
155•wglb•1d ago•21 comments

It's Death

https://jesseduffield.com/ITS-DEATH/
7•inatreecrown2•48m ago•0 comments

Test-case reducers are underappreciated debugging tools

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

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

https://opencv.org/opencv-5/
680•ternaus•3d ago•119 comments

Show HN: Resonate – Low-latency, high-resolution spectral analysis

https://alexandrefrancois.org/Resonate/
15•arjf•3d ago•8 comments

More Molly Guards

https://unsung.aresluna.org/more-molly-guards/
5•zdw•3d ago•0 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
306•piskov•1d ago•246 comments

Flat Datacenter Networks at Scale at Amazon

https://perspectives.mvdirona.com/2026/06/flat-datacenter-networks-at-scale/
83•tanelpoder•20h ago•16 comments

Grit: Rewriting Git in Rust with Agents

https://blog.gitbutler.com/true-grit
61•cbrewster•4h ago•50 comments

The LD_DEBUG environment variable (2012)

https://bnikolic.co.uk/blog/linux-ld-debug.html
53•tanelpoder•7h ago•1 comments

FCC wants to kill burner phones by forcing telecoms to get all customers' IDs

https://www.404media.co/fcc-wants-to-kill-burner-phones-by-forcing-telecoms-to-get-all-customers-...
425•berlianta•9h ago•267 comments

Apple decided not to roll out Siri in EU after denied request for exemption

https://www.reuters.com/business/apple-failed-make-its-ai-tool-comply-eu-regulations-eu-commissio...
344•flanged•8h ago•579 comments

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

33•nils_spatial•8h ago•10 comments

Starlink shifts hardware from one-time purchase to $10/month rental

https://arstechnica.com/tech-policy/2026/06/starlink-takes-page-from-cable-firms-with-10-monthly-...
11•Lihh27•35m ago•0 comments

Biff.core: system composition for Clojure web apps

https://biffweb.com/p/core/
101•jacobobryant•8h ago•21 comments

Is Grep All You Need? How Agent Harnesses Reshape Agentic Search

https://arxiv.org/abs/2605.15184
116•Anon84•11h ago•52 comments

Company Will Add Phone, AirPod, and Smartwatch Trackers to ALPRs

https://www.404media.co/this-company-will-add-phone-airpod-and-smartwatch-trackers-to-license-pla...
79•Cider9986•3h ago•26 comments

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

https://qunabu.github.io/Gravity/
139•qunabu•12h ago•34 comments

The iPhone's Last Stand?

https://stratechery.com/2026/the-iphones-last-stand/
163•swolpers•14h ago•206 comments

Ask HN: Are you still using a Vision Pro?

126•y1n0•5h ago•149 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?