frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

OpenCiv3: Open-source, cross-platform reimagining of Civilization III

https://openciv3.org/
160•klaussilveira•1h ago•25 comments

The Waymo World Model

https://waymo.com/blog/2026/02/the-waymo-world-model-a-new-frontier-for-autonomous-driving-simula...
616•xnx•7h ago•392 comments

Show HN: Look Ma, No Linux: Shell, App Installer, Vi, Cc on ESP32-S3 / BreezyBox

https://github.com/valdanylchuk/breezydemo
46•isitcontent•1h ago•6 comments

Show HN: I spent 4 years building a UI design tool with only the features I use

https://vecti.com
182•vecti•3h ago•84 comments

Microsoft open-sources LiteBox, a security-focused library OS

https://github.com/microsoft/litebox
266•aktau•8h ago•133 comments

Sheldon Brown's Bicycle Technical Info

https://www.sheldonbrown.com/
258•ostacke•7h ago•61 comments

Show HN: R3forth, a ColorForth-inspired language with a tiny VM

https://github.com/phreda4/r3
15•phreda4•1h ago•1 comments

Monty: A minimal, secure Python interpreter written in Rust for use by AI

https://github.com/pydantic/monty
18•dmpetrov•2h ago•4 comments

Early Christian Writings

https://earlychristianwritings.com/
61•dsego•1h ago•17 comments

I spent 5 years in DevOps – Solutions engineering gave me what I was missing

https://infisical.com/blog/devops-to-solutions-engineering
65•vmatsiiako•6h ago•16 comments

Learning from context is harder than we thought

https://hy.tencent.com/research/100025?langVersion=en
106•limoce•3d ago•55 comments

Understanding Neural Network, Visually

https://visualrambling.space/neural-network/
200•surprisetalk•3d ago•24 comments

An Update on Heroku

https://www.heroku.com/blog/an-update-on-heroku/
234•lstoll•8h ago•179 comments

Evaluating and mitigating the growing risk of LLM-discovered 0-days

https://red.anthropic.com/2026/zero-days/
13•lebovic•1d ago•2 comments

How virtual textures work

https://www.shlom.dev/articles/how-virtual-textures-really-work/
13•betamark•8h ago•3 comments

The Beauty of Slag

https://mag.uchicago.edu/science-medicine/beauty-slag
10•sohkamyung•3d ago•2 comments

I now assume that all ads on Apple news are scams

https://kirkville.com/i-now-assume-that-all-ads-on-apple-news-are-scams/
890•cdrnsf•11h ago•390 comments

Show HN: Smooth CLI – Token-efficient browser for AI agents

https://docs.smooth.sh/cli/overview
66•antves•1d ago•52 comments

How to effectively write quality code with AI

https://heidenstedt.org/posts/2026/how-to-effectively-write-quality-code-with-ai/
120•i5heu•4h ago•87 comments

Masked namespace vulnerability in Temporal

https://depthfirst.com/post/the-masked-namespace-vulnerability-in-temporal-cve-2025-14986
24•bmit•3h ago•2 comments

Show HN: Slack CLI for Agents

https://github.com/stablyai/agent-slack
14•nwparker•1d ago•4 comments

Show HN: Horizons – OSS agent execution engine

https://github.com/synth-laboratories/Horizons
11•JoshPurtell•22h ago•3 comments

The mystery of the mole playing rough (2019) [video]

https://www.youtube.com/watch?v=nwQmwT1ULMU
7•archagon•16h ago•0 comments

Show HN: Gigacode – Use OpenCode's UI with Claude Code/Codex/Amp

https://github.com/rivet-dev/sandbox-agent/tree/main/gigacode
6•NathanFlurry•9h ago•4 comments

Hackers (1995) Animated Experience

https://hackers-1995.vercel.app/
322•todsacerdoti•9h ago•187 comments

Claude Composer

https://www.josh.ing/blog/claude-composer
67•coloneltcb•2d ago•47 comments

Show HN: If you lose your memory, how to regain access to your computer?

https://eljojo.github.io/rememory/
95•eljojo•4h ago•87 comments

FORTH? Really!?

https://rescrv.net/w/2026/02/06/associative
5•rescrv•9h ago•2 comments

Evolution of car door handles over the decades

https://newatlas.com/automotive/evolution-car-door-handle/
28•andsoitis•3d ago•48 comments

Planetary Roller Screws

https://www.humanityslastmachine.com/#planetary-roller-screws
20•everlier•3d ago•3 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•8mo ago

Comments

balloob•8mo 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•8mo ago
Discussion for the other article in the series:

https://news.ycombinator.com/item?id=44011381

tomhow•8mo ago
Comments moved thither. Thanks!
pabs3•8mo ago
They are two different articles, I don't think that was correct.
tomhow•8mo 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•8mo ago
Thanks for the response, guess that makes sense.
pabs3•8mo 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?