frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

How I use LLMs to learn complex topics

https://laurentiugabriel.github.io/blog/articles/how-i-use-llms-to-learn/
432•laurentiurad•6h ago•253 comments

How We Pushed CDC into Postgres

https://www.snowflake.com/en/blog/engineering/postgres-to-snowflake-replication-mirroring/
21•craigkerstiens•1h ago•0 comments

Mea Culpa – Dark Hours

https://blog.terrygodier.com/2026/08/09/mea-culpa-dark-hours.html
563•satvikpendem•12h ago•254 comments

"The Persian MâR-Nâmeh Or, the Book for Taking Omens from Snakes" (1892)

https://publicdomainreview.org/collection/marnameh/
29•Thevet•2d ago•2 comments

New Zealand lost its music media, and what we're building to replace it

https://propelmusic.co.nz/articles/the-sound-went-quiet-nz-music-media
78•berghoffer•5h ago•44 comments

Ask HN: What are you working on? (August 2026)

174•david927•8h ago•657 comments

Taxi drivers rarely die of Alzheimer's

https://theconversation.com/taxi-drivers-rarely-die-of-alzheimers-how-complex-mental-maps-and-spa...
186•jader201•10h ago•143 comments

Picophysics: Single file physics for games on platforms like N64, PSX, DC

https://gitlab.com/Kazade/picophysics
14•klaussilveira•4d ago•5 comments

Tuxedo No. 2 – Cocktail recipes

https://tuxedono2.com
48•smartmic•5h ago•11 comments

Cool URIs Don't Change (1998)

https://www.w3.org/Provider/Style/URI
188•Klaster_1•11h ago•44 comments

Andrew Wiles on proving Fermat’s Last Theorem (1995) [video]

https://www.youtube.com/watch?v=GS7CxAtV5Ks
35•jackdoe•3d ago•24 comments

The tragedy of the commons, AI edition

https://www.economist.com/britain/2026/08/06/the-tragedy-of-the-commons-ai-edition
76•simonpure•6h ago•42 comments

Japanese court overturns Red RAW video patent

https://www.dpreview.com/news/panasonic-did-what-apple-sony-and-nikon-couldnt-overturn-a-red-raw-...
25•anigbrowl•1h ago•3 comments

Everything you do is being recorded

https://www.theatlantic.com/technology/2026/05/ai-wearable-surveillance-countermeasures/687203/
217•ike_usawa•14h ago•173 comments

Touring the Consensus, Six Months In

https://theconsensus.dev/blog/2026/08/05/touring-the-consensus-six-months-in.html
13•tosh•3d ago•0 comments

OpenChamber: An Agentic Development Environment

https://openchamber.dev/
109•hexomancer•8h ago•55 comments

The German Mittelstand

https://kieranvelasquez.substack.com/p/on-the-german-mittelstand
14•Michelangelo11•3d ago•0 comments

I made tinnitus my friend, then it disappeared [video]

https://mynoise.net/vlog.php?ep=20260803
83•gregsadetsky•7h ago•57 comments

How Golden Is Silence, Actually?

https://www.newyorker.com/magazine/2026/08/10/silence-kate-mcloughlin-book-review
41•tintinnabula•3d ago•21 comments

The Ambition Project

https://www.betonit.ai/p/the-ambition-project
6•herbertl•2h ago•0 comments

Windows 11's built-in Weather app wastes more than 1 GB of RAM

https://www.notebookcheck.net/Windows-11-s-built-in-Weather-app-wastes-more-than-1-GB-of-RAM.1364...
375•akyuu•11h ago•309 comments

Show HN: A Project Oberon System version running on RISC-V instead of RISC-5

https://github.com/rochus-keller/OberonSystem/tree/op2-rv32
105•Rochus•13h ago•16 comments

John C. Lilly on solid state intelligence and the elimination of man (1978)

https://kibotronics.net/unlisted/lilly-machines/
127•Kiboneu•12h ago•85 comments

Reviving a four year old reMarkable 2

https://oskrim.github.io/hardware/2026/08/09/remarkable-over-ssh.html
125•oskrim•14h ago•86 comments

To Recruit Teachers, School Districts Are Building Homes

https://www.nytimes.com/2026/07/28/business/affordable-housing-schools-teachers.html
41•mooreds•4h ago•30 comments

When Compilers Disagree About UTF‑8

https://nemanjatrifunovic.substack.com/p/when-compilers-disagree-about-utf8
36•rbanffy•4d ago•6 comments

The Hacker's Renaissance (2025)

https://phrack.org/issues/72/19#article
96•yu3zhou4•5h ago•69 comments

Show HN: Alphabet Soup, a multiplayer game, build the longest word to win

https://alphabetsoup.club
25•johnchinjew•5h ago•16 comments

The Alpha 21264 CPU: NT's Greatest RISC (1998)

https://halfhill.com/byte/1998-12_alpha.html
85•Lammy•16h ago•67 comments

Human vs. AI – Diff-based line-level provenance for text under agentic editing

https://github.com/eighttrigrams/us-vs-them
44•eighttrigrams•10h 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?