frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Kagi added a setting for removing paywalled links from search results

https://kagi.com/changelog#11296
99•speckx•32m ago•33 comments

DeepSeek-v4-flash-vision-exp

https://api-docs.deepseek.com/guides/vision/
272•dares2573•3h ago•76 comments

AI companies destroy physical books – let's scan rare books before it's too late

https://annas-archive.pk/blog/physical-destruction.html
340•darccio•4h ago•260 comments

Grand jury declines to indict Ohio man charged with destroying Flock camera

https://san.com/cc/grand-jury-declines-to-indict-ohio-man-charged-with-destroying-flock-camera/
179•throw7•1h ago•65 comments

TigerBeetle Core System Architecture: Deconstructing Performance Engineering

https://ixuvo.com/blog/tigerbeetle-core-system-architecture-performance-engineering
77•ksec•2h ago•31 comments

Small, native web tricks worth remembering

https://htmlcat.net/
152•marcomezzavilla•4h ago•35 comments

Kodak's "Pre-Invented" Lunar Orbiter Camera; Or, the Fate of SAMOS Readout

https://invertingvision.com/2026/08/10/kodaks-pre-invented-lunar-orbiter-camera-or-the-fate-of-sa...
7•cainxinth•36m ago•0 comments

Radiation damage to Hubble has been 4.3 years out of phase with the Solar cycle

https://arxiv.org/abs/2608.18214
17•pppone•54m ago•4 comments

I'm Becoming AI-Blind

https://cymerys.com/w/im-becoming-ai-blind
45•rcymerys•2h ago•38 comments

Kino: A high-performance Ractor web server for Ruby 4.0

https://github.com/yaroslav/kino
39•ksec•3h ago•7 comments

The Lost Treasure of Sid Meier's Pirates

https://remapradio.com/articles/the-lost-treasure-of-sid-meiers-pirates/
188•spankibalt•7h ago•106 comments

What Happens When the Cost of Intelligence Drops 100x

https://catalystneuro.com/blog/cost-of-intelligence-drops-100x/
9•bkd9•1h ago•3 comments

Rama 0.4: System proxy and PAC support

https://plabayo.tech/blog/rama-0-4
5•gdcbe•38m ago•2 comments

What We Lost When Search Stopped Making Us Think

https://blog.8ball.space/what-we-lost-when-search/
3•speckx•13m ago•0 comments

We are living in a version of the future out of J.G. Ballard or William Gibson

https://precastreinforced.co.uk/2026/08/16/new-worlds/
6•speckx•1h ago•0 comments

Flat Chair by Sara Paculdo

https://www.toxel.com/tech/2026/08/07/flat-chair-by-sara-paculdo/
84•surprisetalk•4d ago•26 comments

Convite

https://www.guidavid.com/writing/convite
6•gdss•1h ago•0 comments

DuckDB V2 PEG-based SQL parser

https://duckdb.org/2026/08/20/duckdb-20-peg-parser
8•karma_daemon•1h ago•0 comments

We Rebuilt the Linux MicroVM Stack on Apple Silicon

https://encore.dev/blog/firecracker-apple-silicon
123•signa11•7h ago•67 comments

Nvidia AVO scores 100% on the ARC-AGI-3 interactive reasoning benchmark

https://twitter.com/NVIDIAAI/status/2090786258981466231
28•dsrtslnd23•1h ago•9 comments

The August 17 outage

https://github.blog/news-insights/company-news/the-august-17-outage-and-the-work-ahead/
602•0xedb•19h ago•692 comments

I accidentally logged phone calls to military bases

https://lina.sh/blog/hijacking-e164-arpa
11•gavide•1h ago•0 comments

I like 'em thick: an apology to my English teachers

https://www.experimental-history.com/p/i-like-em-thick
812•Ariarule•2d ago•327 comments

HTML Can Do That

https://chrisburnell.com/html-can-do-that/
933•encyclopedism•1d ago•210 comments

Yes/No/Cancel causes Aspirin sales to soar

https://martin.kleppmann.com/2007/07/19/yes-no-cancel-causes-aspirin-sales-to-soar.html
4•ankitg12•1h ago•1 comments

AI;DR or Don't be a meat proxy

https://theaspiringnerd.com/aidr-or-dont-be-a-meat-proxy/
5•speckx•2h ago•0 comments

The road to ACID transactions in Cassandra 6

https://theconsensus.dev/p/2026/08/16/transactions-in-cassandra.html
5•eatonphil•2h ago•0 comments

Malicious Rust crate Arrayref runs a build-time payload

https://safedep.io/arrayref-proc-macro1-rust-build-time-malware/
531•abhisek•1d ago•463 comments

Micron announces $10B research hub in Boise

https://investors.micron.com/news/press-release/2026/Micron-Unveils-Micron-Research-Labs-a-U-S--B...
89•osnium123•10h ago•33 comments

The Mystery of Dark Oxygen

https://www.newyorker.com/science/elements/the-mystery-of-dark-oxygen
39•rbanffy•5d ago•11 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?