frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Decker, a platform that builds on the legacy of Hypercard and classic macOS

https://beyondloom.com/decker/
193•tosh•6h ago•44 comments

I wanted a clock that never needed setting. Things escalated

https://arstechnica.com/gadgets/2026/07/i-wanted-a-clock-that-never-needed-setting-things-escalated/
23•lee_ars•3d ago•17 comments

Teaching Kids Forth

https://gracefulliberty.com/articles/teaching-kids-forth/
39•rbanffy•2h ago•8 comments

French firefighters face 'pyrocumulonimbus' for first time

https://www.france24.com/en/live-news/20260726-french-firefighters-face-pyrocumulonimbus-for-firs...
142•saaaaaam•6h ago•62 comments

Introduction to Data-Oriented Design [pdf]

https://www.gamedevs.org/uploads/introduction-to-data-oriented-design.pdf
91•tosh•6h ago•27 comments

Design is compromise

https://stephango.com/design-is-compromise
178•ankitg12•8h ago•67 comments

Simulate cassette tape audio profiles using FFmpeg

https://github.com/AARomanov1985/Audio-Cassette-Simulation
54•xterminal•4h ago•28 comments

Plasma Tunnels Reveal How Dying Satellites Fall to Earth

https://spectrum.ieee.org/space-debris-atmosphere-burn-up
35•marc__1•3h ago•10 comments

We have proof automation now

https://www.imperialviolet.org/2026/07/26/zstd-lean.html
41•zdw•3h ago•5 comments

Htmx 4.0, the first JavaScript library to release exclusively on the Game Boy

https://swag.htmx.org/en-cad/products/htmx-4-the-game
336•rcy•12h ago•105 comments

Show HN: CheapSecurity – Lightweight, Self-Hosted CCTV for Linux SBCs

https://github.com/gmrandazzo/CheapSecurity
98•zeldone•8h ago•21 comments

Cursor Bridge – Run Unlimited Claude Code on Your Cursor Subscription

https://github.com/hkc5/cursor-bridge
15•hakancan•1h ago•18 comments

How to Block Some of the Bots

https://nochan.net/b/Internet-Crap/20260606-How-To-Block-Some-Of-The-Bots/
67•Bender•5h ago•73 comments

How to Write English Prose

https://thelampmagazine.com/blog/how-to-write-english-prose
64•geneticdrifts•6h ago•35 comments

Go Analysis Framework: modular static analysis by go team

https://pkg.go.dev/golang.org/x/tools/go/analysis
174•AbuAssar•12h ago•35 comments

Wattage: A token-spend profiler and cost-regression gate for AI agents

https://github.com/faizannraza/wattage
3•faizanraza03•57m ago•0 comments

The Usefulness of Useless Knowledge (1939) [pdf]

https://faculty.lsu.edu/kharms/files/flexner_1939.pdf
11•jxmorris12•3d ago•1 comments

The New AI Superpowers: Focus and Followthrough

https://www.rickmanelius.com/p/the-new-ai-superpowers-focus-and
127•mooreds•11h ago•42 comments

How AST-grep Rewrote Tree-sitter in Rust and Made It 30% Faster

https://astgrep.com/blog/tree-sitter-rust-rewrite
48•herrington_d•6h ago•7 comments

GrapheneOS protections against data extraction from locked devices

https://discuss.grapheneos.org/d/40700-grapheneos-protections-against-data-extraction-from-locked...
376•Cider9986•18h ago•219 comments

History of John Backus's functional programming project [draft]

https://softwarepreservation.computerhistory.org/FP/
3•cwbuilds•2d ago•0 comments

The relay market powering token resellers and fraud

https://vectoral.com/blog/token-relay-market
146•mlenhard•9h ago•91 comments

I learned PCB design, 3D printing and C just to listen to music

https://pentaton.app/blog/2026-07-12-introducing-pentaton-lp/
170•interfeco•3d ago•35 comments

Kill The Cookie Banner

https://killthecookiebanner.eu/
782•rapnie•12h ago•385 comments

Japan legend Miura, 59, scores first goal since 2022

https://www.bbc.com/sport/football/articles/c3r087181ndo
37•brudgers•1h ago•7 comments

Jimothy the raccoon has a rare spinal condition. Here's what that means

https://www.popsci.com/science/whats-jimothy-raccoon-condition/
98•speckx•5d ago•51 comments

Using sed to make indexes for books (1997)

https://www.pement.org/sed/make_indexes.txt
47•TMWNN•3d ago•9 comments

Show HN: Reverse Minesweeper

https://sunflowersgame.com/
134•pompomsheep•11h ago•46 comments

It's not empowering to hand off the details

https://davidnicholaswilliams.com/its-not-empowering-to-hand-off-the-details/
173•davnicwil•6h ago•95 comments

Multiway Turing Machines (2021 pre-ai)

https://bulletins.wolframphysics.org/2021/02/multiway-turing-machines/
17•marysminefnuf•3h ago•3 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?