frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Building an HTML-first site doubled our users overnight

https://mohkohn.co.uk/writing/html-first/
86•edent•1h ago•19 comments

I Hate (Most) Keyboard 'Fn' Keys

https://danq.me/2026/06/09/fn-keys/
77•speckx•44m ago•46 comments

Mercedes‑Benz starts large‑scale production of electric axial flux motor

https://media.mercedes-benz.com/en/article/bebac2af-acdc-465a-9538-adb0bf3d8ccf
286•raffael_de•6h ago•155 comments

macOS Container Machines

https://github.com/apple/container/blob/main/docs/container-machine.md
948•timsneath•13h ago•340 comments

Buy a train, bridge or tracks from the Swiss Railway

https://sbbresale.ch/
64•kisamoto•2d ago•37 comments

All 9,300 Japanese train station, animated by the year it opened (1872–2026)

https://jivx.com/eki
46•momentmaker•1h ago•19 comments

Claude Fable 5

https://www.anthropic.com/news/claude-fable-5-mythos-5
2397•Philpax•21h ago•1887 comments

AWS Bedrock to require sharing data with Anthropic for Mythos and future models

230•TomAnthony•5h ago•156 comments

ICE denies having a protester database. A letter to Congress sheds more light

https://www.npr.org/2026/06/10/nx-s1-5843159/ice-protester-database-dhs
22•Jimmc414•32m ago•5 comments

Hacking for Defense Stanford 2026 – Lessons Learned Presentations

https://steveblank.com/2026/06/08/g-for-defense-stanford-2026-lessons-learned-presentations/
46•sblank•1d ago•23 comments

Who Runs Your Rust Future? Hands-On Intro to Async Rust

https://aibodh.com/posts/async-rust-chapter-1-hands-on-intro-to-async-rust/
11•febin•1d ago•0 comments

Reviving Papers with Code

https://paperswithcode.co/
101•nielz_r•2d ago•21 comments

Upcoming breaking changes for npm v12

https://github.blog/changelog/2026-06-09-upcoming-breaking-changes-for-npm-v12/
426•plasma•17h ago•171 comments

Show HN: macOS menu bar gauges for your Claude Code quota

https://github.com/grzegorz-raczek-unit8/claude-quota
29•grzracz•4h ago•22 comments

Magnetoelectric antennas could transform how underwater robots talk

https://newatlas.com/engineering/magnetoelectric-antennas-submarine-robots-communications/
39•breve•3d ago•15 comments

Rich Sutton on AI creativity and discovery

https://twitter.com/RichardSSutton/status/2061216087744946656
165•yimby•11h ago•85 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...
759•ahlCVA•12h ago•419 comments

Ask HN: Are most corporate SWE jobs performative?

23•hnthrow10282910•48m ago•20 comments

RIP software hackathons. Long live the hardware hackathon

https://blog.oscars.dev/posts/rip-software-hackathons-long-live-the-hardware-hackathon/
224•ozcap•15h ago•108 comments

Ultrafast machine learning on FPGAs via Kolmogorov-Arnold Networks

https://aarushgupta.io/posts/kan-fpga/
255•ag2718•18h ago•36 comments

What it feels like to work with Mythos

https://www.oneusefulthing.org/p/what-it-feels-like-to-work-with-mythos
322•swolpers•20h ago•283 comments

Surprise, pay $1000

https://forestwalk.ai/blog/surprise-blacksmith-costs/
251•apike•16h ago•102 comments

Port React Compiler to Rust

https://github.com/react/react/pull/36173
103•boudra•4h ago•90 comments

I thought I knew how electrolysis worked [video]

https://www.youtube.com/watch?v=eq7fR9ISuCw
72•tambourine_man•5d ago•7 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...
132•1659447091•3d ago•24 comments

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

https://opencv.org/opencv-5/
791•ternaus•4d ago•142 comments

More Molly Guards

https://unsung.aresluna.org/more-molly-guards/
161•zdw•3d ago•18 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...
916•mips_avatar•16h ago•452 comments

Premature optimization is fun sometimes

https://invlpg.com/posts/2025-06-19-premature-optimization.html
64•throawayonthe•2d ago•15 comments

Lies we tell ourselves about email addresses

https://gitpush--force.com/commits/2026/06/lies-we-tell-ourselves-about-email/
145•theanonymousone•1d ago•153 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?