frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

How NASA built Artemis II’s fault-tolerant computer

https://cacm.acm.org/news/how-nasa-built-artemis-iis-fault-tolerant-computer/
324•speckx•17h ago•110 comments

I still prefer MCP over skills

https://david.coffee/i-still-prefer-mcp-over-skills/
119•gmays•6h ago•115 comments

Native Instant Space Switching on macOS

https://arhan.sh/blog/native-instant-space-switching-on-macos/
470•PaulHoule•12h ago•213 comments

We've raised $17M to build what comes after Git

https://blog.gitbutler.com/series-a
94•ellieh•6h ago•182 comments

Generative art over the years

https://blog.veitheller.de/Generative_art_over_the_years.html
128•evakhoury•2d ago•29 comments

RAM Has a Design Flaw from 1966. I Bypassed It [video]

https://www.youtube.com/watch?v=KKbgulTp3FE
187•surprisetalk•2d ago•39 comments

Charcuterie – Visual similarity Unicode explorer

https://charcuterie.elastiq.ch/
214•rickcarlino•12h ago•38 comments

Principles of Mechanical Sympathy

https://martinfowler.com/articles/mechanical-sympathy-principles.html
47•zdw•2d ago•4 comments

How Uv Works Under the Hood

https://noos.blog/posts/uv-how-it-works-under-the-hood/
10•vinhnx•1h ago•0 comments

Afrika Bambaataa, hip-hop pioneer, has died

https://www.bbc.co.uk/news/articles/c2evppm30p7o
97•mellosouls•3h ago•13 comments

PicoZ80 – Drop-In Z80 Replacement

https://eaw.app/picoz80/
186•rickcarlino•13h ago•30 comments

Unfolder for Mac – A 3D model unfolding tool for creating papercraft

https://www.unfolder.app/
213•codazoda•15h ago•44 comments

CollectWise (YC F24) Is Hiring

https://www.ycombinator.com/companies/collectwise/jobs/Ktc6m6o-ai-agent-engineer
1•OBrien_1107•3h ago

Old laptops in a colo as low cost servers

https://colaptop.pages.dev/
253•argentum47•13h ago•141 comments

YouTube locked my accounts and I can't cancel my subscription

https://pocketables.com/2026/04/ai-music-corporate-control-and-the-creator-who-cant-even-leave.html
64•digitalhigh•3h ago•48 comments

The Raft consensus algorithm explained through "Mean Girls" (2019)

https://www.cockroachlabs.com/blog/raft-is-so-fetch/
73•vermilingua•5h ago•19 comments

Instant 1.0, a backend for AI-coded apps

https://www.instantdb.com/essays/architecture
137•stopachka•13h ago•76 comments

VFX HQ: Visual Effects Headquarters (2000)

https://www.vfxhq.com/index.html
9•exvi•2d ago•0 comments

Research-Driven Agents: When an agent reads before it codes

https://blog.skypilot.co/research-driven-agents/
173•hopechong•15h ago•48 comments

Knit File Formats

https://soup.agnescameron.info//2026/03/25/kniterate-waste-section.html
11•surprisetalk•3d ago•0 comments

Reverse engineering Gemini's SynthID detection

https://github.com/aloshdenny/reverse-SynthID
146•_tk_•12h ago•50 comments

Hegel, a universal property-based testing protocol and family of PBT libraries

https://hegel.dev
112•PaulHoule•13h ago•32 comments

Will I ever own a zettaflop?

https://geohot.github.io//blog/jekyll/update/2026/01/26/own-a-zettaflop.html
87•surprisetalk•3d ago•56 comments

LLM plays an 8-bit Commander X16 game using structured "smart senses"

https://pvp-ai.russell-harper.com
21•russellharper•1d ago•4 comments

Kagi Product Tips – Customize Your Search Results with URL Redirects

https://blog.kagi.com/tips/redirects
69•treetalker•10h ago•8 comments

Moving from WordPress to Jekyll (and static site generators in general)

https://www.demandsphere.com/blog/rebuilding-demandsphere-with-jekyll-and-claude-code/
77•rgrieselhuber•11h ago•40 comments

An AI robot in my home

https://allevato.me/2026/04/07/an-ai-robot-in-my-home
30•kukanani•2d ago•12 comments

Robots eat cars

https://telemetry.endeff.com/p/robots-eat-cars
57•JMill•3d ago•65 comments

A WebGPU implementation of Augmented Vertex Block Descent

https://github.com/jure/webphysics
141•juretriglav•20h ago•18 comments

Show HN: I built a Cargo-like build tool for C/C++

https://github.com/randerson112/craft
145•randerson_112•16h ago•134 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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