frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Make your first edit to OpenStreetMap

https://high5apps.github.io/josm-plugin-website-wizard/
261•juliantigler•6h ago•69 comments

Nvidia is the central bank of AI

https://www.economist.com/interactive/briefing/2026/09/03/nvidia-is-the-central-bank-of-ai
343•tolugenius•7h ago•235 comments

Real-SWE: Benchmarking AI models on private, real-world, enterprise codebases

https://withspecific.com/benchmarks/real-swe
58•theanonymousone•2h ago•41 comments

Apple iPod Engraver (2019)

https://dunstanorchard.com/apple-ipod-engraver/
68•NaOH•3d ago•8 comments

Getting 50 GB/S Back from the Apple Neural Engine

https://eiln.github.io/posts/ane-dma.html
23•eiln•2d ago•3 comments

Stabilizing Rust's Never Type

https://lwn.net/SubscriberLink/1091015/d9e48318ed242b41/
108•cjd8•3d ago•18 comments

LG denies TV spying claims, says tracking and snooping concerns 'not true'

https://www.tomshardware.com/tech-industry/big-tech/lg-strongly-denies-tv-security-claims-says-tr...
366•datakan•2d ago•322 comments

Will There Be a 7G?

https://arxiv.org/abs/2609.01877
69•Betelbuddy•6h ago•119 comments

IKEA made a mod for Skyrim [video]

https://www.youtube.com/watch?v=iZODN0QUgjI
535•kegenaar•2d ago•140 comments

Benchmark: CadQuery vs. OpenSCAD for agentic CAD work

https://modelrift.com/blog/cadquery-vs-openscad/
26•jetter•3h ago•36 comments

We must pace the frontier

https://darioamodei.com/post/we-must-pace-the-frontier
474•apsec112•8h ago•661 comments

I made a build visualizer to understand Bun's compile times

https://lalitm.com/post/buildprof/
81•lalitmaganti•8h ago•15 comments

Microcode in Intel's 8087 floating-point chip: the scale instruction

https://www.righto.com/2026/09/8087-microcode-reverse-engineering-fscale.html
77•pwg•7h ago•23 comments

Linux Zoom client proactively reading everything written to X11 clipboard

https://hachyderm.io/@simontatham/117201594980991062
117•encyclopedism•4h ago•33 comments

How Trail of Bits helps verify the integrity of Signal chats

https://blog.trailofbits.com/2026/08/11/how-trail-of-bits-helps-verify-the-integrity-of-your-sign...
41•dgroshev•11h ago•21 comments

OpenAI's Sam Altman says it would be 'ill-advised' to go public in 2026

https://techcrunch.com/2026/09/12/openais-sam-altman-says-it-would-be-ill-advised-to-go-public-in...
43•humanlion87•2h ago•30 comments

LG Says We're Fake News [video]

https://www.youtube.com/watch?v=ToP9xfLDSME
80•HelloUsername•3h ago•13 comments

I fixed a tractor using John Deere's self-repair service. Farmers aren't sold

https://www.wired.com/story/i-fixed-a-tractor-john-deere-self-repair-service/
90•sbulaev•1d ago•99 comments

Retrospectively Reverse-Engineering Apple's Neural Engine

https://eiln.github.io/posts/ane.html
214•zdw•15h ago•30 comments

Android NAT-T keepalive offload bypasses VPN lockdown

https://supuk.ch/papers/android-natt-keepalive-vpn-bypass
164•mhitza•1d ago•44 comments

A Mathematical Framework for Transformer Circuits (2021)

https://transformer-circuits.pub/2021/framework/index.html
70•Bluestein•9h ago•17 comments

The Magic Behind Cubacadabra

https://andrewarrow.dev/2026/moon/2/day/19/the-magic-behind-cubacadabra/
8•andrewfromx•2d ago•1 comments

Financial Times' 404 Page not Found

https://www.ft.com/article/404
21•sans_souse•1h ago•5 comments

StarCraft returns in 2030 as an open-world shooter

https://www.theverge.com/games/994371/starcraft-returns-in-2030-as-an-open-world-shooter
11•sbulaev•59m ago•5 comments

Performance of WebAssembly Runtimes in 2026

https://00f.net/2026/06/23/webassembly-runtimes-2026/
82•fagnerbrack•3d ago•20 comments

Navier-Stokes Announcement

https://www.claymath.org/news/navier-stokes-announcement/
304•rvz•18h ago•246 comments

Eating Fruit Skins

https://pgadey.ca/blog/eating-fruit-skins/
69•surprisetalk•3d ago•159 comments

The worst spam emails: iLands AI agent hustle

https://tedium.co/2026/09/11/ilands-agents-email-spam-kaixin-tang/
99•ColinWright•11h ago•47 comments

λ Snap – An inviting programming language for kids and adults for CS study

https://snap.berkeley.edu/
170•dr_kiszonka•1d ago•109 comments

Killing with a car costs $1.6M, California requires drivers to carry $30K

https://maxmautner.com/2026/09/11/liability-coverage.html
6•mslate•43m ago•1 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?