frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Credit Card Rewards Became a $9.2B Wealth Transfer

https://www.library.hbs.edu/working-knowledge/how-credit-card-rewards-became-multibillion-dollar-...
35•conbrian•30m ago•13 comments

iCloud+ Hide My Email addresses will remain on icloud.com

https://developer.apple.com/news/?id=1ptvdtcm
505•K7PJP•13h ago•150 comments

Quantum battery upends the rules of charging

https://www.bbc.com/future/article/20260824-this-quantum-battery-charges-faster-the-larger-it-gets
33•reconnecting•1h ago•27 comments

MS Paint and Photos inivisibly watermark even locally generated output with GUID

https://xusheng.dev/posts/reversing/mspaint_invisible_watermark/main/
744•ComputerGuru•20h ago•355 comments

Xiaomi: New CPU matches Apple cores single threaded, much faster multithreaded

https://twitter.com/lemire/status/2091894299289874926
901•tosh•20h ago•649 comments

How Universities Should Prepare Founders

https://paulgraham.com/prepare.html
155•gmays•10h ago•185 comments

SiFive's First Server Platform

https://chipsandcheese.com/p/sifives-first-server-platform
69•geerlingguy•9h ago•16 comments

How Europe is killing makers and micro-entrepreneurs

https://lectronz.com/u/lectronz/articles/how-europe-is-killing-makers-and-micro-entrepreneurs
1440•l-one-lone•23h ago•908 comments

The entire city of San Francisco as a video game

https://sf.thijs.gg/
505•centrosphere•19h ago•146 comments

Moon (2024)

https://ciechanow.ski/moon/
212•simonebrunozzi•14h ago•36 comments

What's new in Emacs 31.1

https://www.masteringemacs.org/article/whats-new-in-emacs-311
175•geospeck•23h ago•35 comments

Bookshelf – Self-hosted eBook library that runs on object storage

https://github.com/murerkinn/bookshelf
117•arbayi•13h ago•44 comments

Headlong: A Microharness for Persistent Agents

https://www.laude.org/updates/headlong-a-microharness-for-persistent-agents
81•lbw1215•8h ago•31 comments

Where did all the public bathrooms go?

https://daily.jstor.org/where-did-all-the-public-bathrooms-go/
265•herbertl•19h ago•577 comments

Nostr is an inclusive communication commons

https://nostr.org/
165•Bluestein•2d ago•107 comments

Vintage Artificial Intelligence: Before It Got Awkward

https://blog.archive.org/2026/08/16/vintage-artificial-intelligence-before-it-got-awkward/
116•signor_bosco•15h ago•22 comments

Training AI to Paint with Code

https://surya.website/rling-qwen-to-paint-with-code
118•Tiberium•1d ago•13 comments

Peppermint oil reduces blood pressure by 8.48 mmHg in small study

https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0344538
176•brandonb•21h ago•83 comments

Screen viewing time from age 1 to 8 years and subsequent academic performance

https://link.springer.com/article/10.1007/s12519-026-01046-1
41•Markoff•2h ago•35 comments

Show HN: I wrote a BASIC interpreter that boots on UEFI machines

https://tarjan.itch.io/thoreaubasic
79•Gorsefound•1d ago•26 comments

Crafting QR Codes: A deep dive into QR code art (2024)

https://kylezhe.ng/writes/crafting-qr-codes
99•subset•21h ago•7 comments

Walgit – a Git server that is one binary in front of an object store

https://github.com/tobi/walgit
108•matallo•21h ago•35 comments

Jabber/XMPP: 25 Years of Digital Independence

https://gultsch.de/posts/25-years-of-digital-independence/
237•inputmice•20h ago•140 comments

LLMs could control their host machines by exploiting inference engines

https://boydkane.com/essays/llms-could-control-their-host-machines-by-exploiting-inference-engines
162•zdw•17h ago•76 comments

Why some US restaurants are banning tips

https://www.bbc.com/news/articles/c4g36yze692o
145•rock_artist•1h ago•246 comments

I were 17, I'd learn how to build LLMs from scratch

https://twitter.com/paulg/status/2091544343589060625
561•bilsbie•1d ago•641 comments

Was modern art a CIA psy-op? (2020)

https://daily.jstor.org/was-modern-art-really-a-cia-psy-op/
99•neom•10h ago•166 comments

SeL4 security proofs now complete on AArch64

https://proofcraft.systems/news-2026/#2026-08-21
192•snvzz•1d ago•47 comments

Oceans hit highest temperature on record

https://www.bbc.com/news/articles/c62m4gpnp78o
605•tcp_handshaker•16h ago•475 comments

Show HN: PicoMQ – Durable Streams over HTTP, on object storage

https://picomq.com/
137•adesh_nalpet•19h ago•23 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?