frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

WallHop – 12ft.io is gone, so I built a replacement

https://wallhop.io/
38•TheWaffleHax•30m ago•18 comments

Build your own decision model

https://nishtahir.com/build-your-own-decision-model/
100•softwaredoug•2h ago•16 comments

2D Vehicles

https://patkerr.co.uk/2d-vehicles/
353•Michelangelo11•3d ago•82 comments

A city-building game in which the city would prefer you didn't

https://housing.over.pizza/
163•JumpCrisscross•4h ago•63 comments

The Lightbulb Computer

https://lightbulbcomputer.com/
227•oskarth•21h ago•42 comments

Nix wrote half of my debugger

https://fzakaria.com/2026/10/07/nix-wrote-half-of-my-debugger
124•ingve•1d ago•20 comments

A minimal Rust TUI for managing GitHub repos and branches

https://github.com/jorgeandrecastro/github-workflow
4•drew0670•59m ago•1 comments

Knuth reward check

https://www.thomas-huehn.com/knuth-reward-check/
143•Curiositry•9h ago•51 comments

Five months treating bugs like patients and coding agents like a medical team

https://www.cockroachlabs.com/blog/experiment-running-hospital-code/
53•rafiss•1d ago•26 comments

Why DuckDB 2.0 is faster

https://motherduck.com/blog/why-duckdb-20-is-faster/
138•tosh•7h ago•48 comments

Talorys – A self-hosted personal AI agent on Cloudflare's free tier

https://github.com/rociiu/talorys
246•rociiu•14h ago•121 comments

Mxc: Microsoft Execution Containers version 1.0.0

https://blogs.windows.com/windowsdeveloper/2026/10/07/microsoft-execution-containers-policy-drive...
158•smokel•1d ago•36 comments

REA Reverse – Engineer Anything

https://rea.tools/
699•modinfo•1d ago•303 comments

Recent AI models struggled to match a human algorithmic innovation

https://epoch.ai/publications/innovationeval
75•merksittich•1d ago•55 comments

Unikernels were hard. key word: were

https://ghuntley.com/unikernels/
93•ghuntley•10h ago•41 comments

Getting old Macromedia Director Games to run on modern Hardware

https://werwolv.net/posts/macromedia_copy_protection/
36•speckx•1d ago•5 comments

Grieving the loss of details

https://purplesyringa.moe/blog/grieving-the-loss-of-details/
343•signa11•4d ago•273 comments

OpenSCAD the Programmers Solid 3D CAD Modeller

https://openscad.org/
99•b-man•4d ago•85 comments

Nvidia in talks to acquire US 'open' model startup Reflection AI

https://www.ft.com/content/052610c5-22b4-4dd4-932e-b7f9f0628b6a
116•arkj•6h ago•82 comments

Rampart: Browser native on-device PII radaction

https://ndstudio.gov/posts/say-hello-to-rampart
71•nateb2022•1d ago•29 comments

Bitwarden Dual License Model

https://community.bitwarden.com/t/published-version-update-in-app-stores/102750
345•Cider9986•10h ago•247 comments

Show HN: Diffle, a keyboard-centric diff viewer with LSP support

https://github.com/moritzwilksch/diffle
8•mwil1000•2d ago•1 comments

Food processing influences metabolism and brain activity

https://news.vt.edu/articles/2026/10/research_fralinbiomed_upfhutelin.html
106•gmays•19h ago•81 comments

C for Rust programmers

https://bd103.dev/blog/2026-10-07-c-for-rust-programmers/
97•xyproto•2d ago•98 comments

Telegram Desktop vulnerability allowed any user's file to be stolen

https://beaksec.github.io/posts/telegram-desktop-one-click-account-takeover/
411•g-b-r•22h ago•265 comments

Apple/macOS removed from official Unix registry

https://www.opengroup.org//openbrand/register/
250•john_alan•14h ago•218 comments

Eye of Sauron: Long-Range Hidden Spy Camera Detection (2024)

https://www.usenix.org/conference/usenixsecurity24/presentation/zhang-qibo
311•ortusdux•3d ago•74 comments

I would like the value of my home to rise, while my property taxes fall

https://conversableeconomist.com/2026/09/28/i-would-like-the-value-of-my-home-to-rise-while-my-pr...
214•colinprince•11h ago•509 comments

Chernobyl particles reveal unexpectedly stable nuclear fuel after 40 years

https://phys.org/news/2026-10-chernobyl-particles-reveal-unexpectedly-stable.html
130•geox•3d ago•49 comments

How strong is the strong interaction?

https://cerncourier.com/how-strong-is-the-strong-interaction/
47•EA-3167•1d ago•12 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?