frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Run Qwen 3.8 Flash Next (125B) on consumer hardware (RTX 4090) at 100T/s

https://github.com/Niko1221/Strata
159•snehesht•2h ago•60 comments

Glashütte Trash Clock – A 30-minute pendulum clock made from trash

https://niklasroy.com/gtc/
55•r0r0•2d ago•8 comments

Tell HN: Bob Cringely has died

619•paveworld•14h ago•122 comments

Show HN: AI search for every photo and every frame of video on macOS

https://github.com/allenv0/SCM
39•allenleee•5h ago•24 comments

VGHF Digital Archive passes 5000 magazines. Here's what's next

https://gamehistory.org/5k-magazines/
63•rdmuser•5h ago•8 comments

Why don't more developers “use the platform”?

https://nolanlawson.com/2026/10/03/why-dont-more-developers-use-the-platform/
205•vinhnx•10h ago•196 comments

The work by Valve's Timur Kristóf on improving old AMD GPUs on Linux

https://www.phoronix.com/news/XDC-2026-Valve-Timur-AMDGPU
370•speckx•19h ago•65 comments

gpuvis: GPU Trace Visualizer

https://github.com/mikesart/gpuvis
49•luu•1d ago•9 comments

Emitting metadata early makes building/checking Rust up to twice as fast

https://github.com/PowderworksCode/headstart
54•knuckleheads•8h ago•9 comments

The Heilbronn Problem

https://math.tejstead.com/heilbronn/
10•tejstead•1d ago•1 comments

Agents don't need memory, they need documentation

https://liao.gg/blog/agents-dont-need-memory
266•kmeh•21h ago•146 comments

Treachery in the Rodin Museum 3D scan verdict

https://cosmowenman.substack.com/p/rodin-museum-3d-scan-verdict
251•CosmoWenman•21h ago•124 comments

Hole Punch: Sling your spaceship around gravitational fields

https://notoriousbfg.com/hole-punch/
324•trwhite•20h ago•79 comments

LeCun has "zero concerns" about AI wiping out humanity, recent "rogue" incidents

https://fortune.com/2026/10/01/ai-godfather-yann-lecun-has-zero-concerns-about-human-extinction-s...
237•Anon84•21h ago•356 comments

Celebrating the 100th birthday of the kidney donated to him as a teenager

https://www.whec.com/top-news/webster-man-celebrating-the-100th-birthday-of-the-kidney-his-mom-do...
223•gscott•2d ago•57 comments

So you think you could be an electrician?

https://asteriskmag.com/issues/15/so-you-think-you-could-be-an-electrician
356•zdw•3d ago•290 comments

Rejection Sensitivity in Gifted and Twice-Exceptional Children

https://teachyourkids.substack.com/p/rejection-sensitivity-in-gifted-and
59•actfrench•3h ago•23 comments

We're working on a new RuneScape MMO

https://play.runescape.com/4
124•droidjj•13h ago•61 comments

We're going to need default hard budget caps on pretty much everything

https://simonwillison.net/2026/Oct/3/default-hard-budget-caps/
517•elffjs•14h ago•265 comments

Reasons I didn't become an EMT, ranked

https://ben.stolovitz.com/posts/reasons-not-emt-ranked/
189•citelao•18h ago•82 comments

We want you to build the next Git platform on Cloudflare

https://blog.cloudflare.com/next-git-platform-on-cloudflare/
168•geoffbp•19h ago•144 comments

I quit OpenAI because its culture is broken

https://www.theatlantic.com/technology/2026/10/openai-safety-team-resignation/688881/?gift=v5U_Uz...
340•Brajeshwar•1d ago•561 comments

Religious scholars met with Anthropic

https://www.nytimes.com/2026/09/29/us/anthropic-claude-morals-ai.html
130•bookofjoe•12h ago•280 comments

What Meta got right with Muse

https://metedata.substack.com/p/what-meta-got-right-with-muse
81•young_mete•20h ago•110 comments

Your body of work thinks back at you

https://photoni.st/index.php/2026/09/25/your-body-of-work-thinks-back-at-you/
80•surprisetalk•4d ago•13 comments

Math's pedagogical curse – Grant Sanderson [video] (2023)

https://www.youtube.com/watch?v=UOuxo6SA8Uc
61•bobajeff•1d ago•28 comments

What's the Future for Pure Math Research in the Age of AI?

https://writings.stephenwolfram.com/2026/09/whats-the-future-for-pure-math-research-in-the-age-of...
11•6bitquant•7h ago•1 comments

How to hack time, with C2PA

https://www.da.vidbuchanan.co.uk/blog/hacking-time.html
49•Retr0id•20h ago•6 comments

Dirty Optimization Secrets (C for Playdate)

https://devforum.play.date/t/dirty-optimization-secrets-c-for-playdate/23011
36•ibobev•1d ago•4 comments

FTL: A new operating system for clouds

https://ftl-os.org/
188•romac•23h ago•74 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?