frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Personal Encyclopedias

https://whoami.wiki/blog/personal-encyclopedias
177•jrmyphlmn•14h ago•44 comments

Swift 6.3

https://www.swift.org/blog/swift-6.3-released/
45•ingve•2h ago•14 comments

Running Tesla Model 3's computer on my desk using parts from crashed cars

https://bugs.xdavidhu.me/tesla/2026/03/23/running-tesla-model-3s-computer-on-my-desk-using-parts-...
634•driesdep•13h ago•203 comments

What came after the 486?

https://dfarq.homeip.net/what-came-after-486/
30•jnord•2d ago•22 comments

Obsolete Sounds

https://citiesandmemory.com/obsolete-sounds/
18•benbreen•6h ago•3 comments

ARC-AGI-3

https://arcprize.org/arc-agi/3
402•lairv•16h ago•261 comments

The Last Contract: William T. Vollmann's Battle to Publish an Epic (2025)

https://www.metropolitanreview.org/p/the-last-contract
7•benbreen•6h ago•0 comments

The truth that haunts the Ramones: 'They sold more T-shirts than records'

https://english.elpais.com/culture/2026-03-17/the-uncomfortable-truth-that-will-always-haunt-the-...
120•c420•4d ago•60 comments

The Cassandra of 'The Machine'

https://www.thenewatlantis.com/publications/the-cassandra-of-the-machine
8•Hooke•6h ago•0 comments

Earthquake scientists reveal how overplowing weakens soil at experimental farm

https://www.washington.edu/news/2026/03/19/earthquake-scientists-reveal-how-overplowing-weakens-s...
164•Brajeshwar•20h ago•69 comments

Shell Tricks That Make Life Easier (and Save Your Sanity)

https://blog.hofstede.it/shell-tricks-that-actually-make-life-easier-and-save-your-sanity/
90•zdw•9h ago•38 comments

More precise elevation data for GraphHopper routing engine

https://www.graphhopper.com/blog/2026/03/23/more-precise-elevation-data-for-graphhopper/
48•karussell•2d ago•1 comments

Ashby (YC W19) Is Hiring Engineers Who Make Product Decisions

https://www.ashbyhq.com/careers?ashby_jid=c3c7125d-7883-4dff-a2bf-f5a55de4a364&utm_source=hn
1•abhikp•3h ago

My DIY FPGA board can run Quake II

https://blog.mikhe.ch/quake2-on-fpga/part4.html
159•sznio•3d ago•50 comments

Niche Museums

https://www.niche-museums.com/
6•bookofjoe•2d ago•1 comments

The EU still wants to scan your private messages and photos

https://fightchatcontrol.eu/?foo=bar
1181•MrBruh•13h ago•311 comments

90% of Claude-linked output going to GitHub repos w <2 stars

https://www.claudescode.dev/?window=since_launch
292•louiereederson•16h ago•176 comments

Supreme Court Sides with Cox in Copyright Fight over Pirated Music

https://www.nytimes.com/2026/03/25/us/politics/supreme-court-cox-music-copyright.html
349•oj2828•19h ago•269 comments

Show HN: Robust LLM Extractor for Websites in TypeScript

https://github.com/lightfeed/extractor
44•andrew_zhong•6h ago•33 comments

Show HN: Optio – Orchestrate AI coding agents in K8s to go from ticket to PR

https://github.com/jonwiggins/optio
54•jawiggins•17h ago•31 comments

Two studies in compiler optimisations

https://www.hmpcabral.com/2026/03/20/two-studies-in-compiler-optimisations/
82•hmpc•3d ago•7 comments

False claims in a widely-cited paper

https://statmodeling.stat.columbia.edu/2026/03/24/false-claims-in-a-published-no-corrections-no-c...
278•qsi•9h ago•110 comments

Maxell MXCP-P100 – wireless cassette player

https://maxell-usa.com/product/cassetteplayer/
23•ChrisArchitect•2d ago•11 comments

Thoughts on slowing the fuck down

https://mariozechner.at/posts/2026-03-25-thoughts-on-slowing-the-fuck-down/
867•jdkoeck•20h ago•391 comments

Quantization from the Ground Up

https://ngrok.com/blog/quantization
257•samwho•18h ago•47 comments

Government agencies buy commercial data about Americans in bulk

https://www.npr.org/2026/03/25/nx-s1-5752369/ice-surveillance-data-brokers-congress-anthropic
56•nuke-web3•4h ago•20 comments

Apple randomly closes bug reports unless you "verify" the bug remains unfixed

https://lapcatsoftware.com/articles/2026/3/11.html
409•zdw•15h ago•233 comments

Show HN: A plain-text cognitive architecture for Claude Code

https://lab.puga.com.br/cog/
101•marciopuga•10h ago•31 comments

Jury finds Meta liable in case over child sexual exploitation on its platforms

https://www.cnn.com/2026/03/24/tech/meta-new-mexico-trial-jury-deliberation
393•billfor•1d ago•484 comments

My astrophotography in the movie Project Hail Mary

https://rpastro.square.site/s/stories/phm
863•wallflower•3d ago•197 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?