frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

We All Depend on Open Source. We Will Defend It Together

https://akrites.org/letter/
277•dhruv3006•7h ago•135 comments

Om Malik has died

https://om.co/2026/06/24/1966-2026/
993•minimaxir•16h ago•121 comments

An entire Herculaneum scroll has been read for the first time

https://scrollprize.org/firstscroll
1387•verditelabs•21h ago•291 comments

Libre Barcode Project

https://graphicore.github.io/librebarcode/
196•luu•9h ago•33 comments

Bipartite Matching Is in NC

https://scottaaronson.blog/?p=9851
23•amichail•3d ago•0 comments

Framework's 10G Ethernet module exposes USB-C's complexity

https://www.jeffgeerling.com/blog/2026/framework-10g-ethernet-module-usb-c-complexity/
222•Alupis•11h ago•114 comments

What happened after 2k people tried to hack my AI assistant

https://www.fernandoi.cl/posts/hackmyclaw/
217•cuchoi•10h ago•81 comments

Captcha proves you're human. HATCHA proves you're not

https://github.com/mondaycom/HATCHA
47•backlit4034•45m ago•47 comments

22-year-old Mozart's handwritten notebook unearthed in 'major discovery'

https://www.classicfm.com/composers/mozart/handwritten-notebook-discovered-major-paris/
99•thunderbong•5d ago•21 comments

The 'papers, please' era of the internet will decimate your privacy

https://expression.fire.org/p/the-papers-please-era-of-the-internet
823•bilsbie•15h ago•379 comments

The Garbage Collection Handbook: The Art of Automatic Memory Management (2nd Ed) (2023)

https://gchandbook.org/
171•teleforce•13h ago•31 comments

A game where you're an OS and have to manage processes, memory and I/O events

https://github.com/plbrault/youre-the-os
254•exploraz•3d ago•49 comments

Show HN: WebBase-III – dBASE III rebuilt in the browser with its own interpreter

https://github.com/DDecoene/WebBaseIII
7•ddecoene•2d ago•1 comments

IBM debuts sub-1 nanometer chip technology

https://newsroom.ibm.com/2026-06-25-ibm-debuts-worlds-first-sub-1-nanometer-chip-technology
340•porridgeraisin•21h ago•184 comments

Oxide computer 3D rack guided tour

https://explorer.oxide.computer/
401•darthcloud•3d ago•163 comments

Microbubbles in Medicine

https://worksinprogress.co/issue/microbubbles/
15•Jimmc414•4d ago•1 comments

Show HN: OpenKnowledge – open source AI-first alternative to Obsidian/Notion

https://github.com/inkeep/open-knowledge
300•engomez•20h ago•149 comments

Hey Nico, you didn't vibe code your data room but stole it from Papermark

https://twitter.com/mfts0/status/2070080422482977095
415•mmunj•1d ago•170 comments

Show HN: Chess-Inspired Roguelike

https://princechazz.com
338•cowboy_henk•5d ago•111 comments

Un-0: Generating Images with Coupled Oscillators

https://unconv.ai/blog/introducing-un-0-generating-images-with-coupled-oscillators/
159•babelfish•16h ago•39 comments

An oral history of Bank Python (2021)

https://calpaterson.com/bank-python.html
137•tosh•16h ago•50 comments

Apple raises prices of MacBooks, iPads

https://www.reuters.com/world/asia-pacific/apple-raises-prices-macbooks-ipads-memory-costs-skyroc...
753•virgildotcodes•23h ago•1091 comments

Zig's new bitCast semantics and LLVM back end improvements

https://ziglang.org/devlog/2026/#2026-06-25
249•kouosi•22h ago•125 comments

OS9Map

https://yllan.org/software/OS9Map/
238•LaSombra•21h ago•46 comments

The Doorman's Fallacy in action

https://rozumem.xyz/posts/17
139•rozumem•16h ago•196 comments

Record type inference for dummies

http://haskellforall.com/2026/06/record-type-inference-for-dummies
53•g0xA52A2A•2d ago•2 comments

Parallel Parentheses Matching

https://williamdue.github.io/blog/parallel-parentheses-matching
102•Athas•16h ago•13 comments

The last Romans are still around

https://signoregalilei.com/2026/06/20/the-last-romans-are-still-around/
110•surprisetalk•3d ago•149 comments

Doing a masters while working in Spain

https://jan-herlyn.com/blog/doing-a-masters-while-working/
63•MHard•4d ago•44 comments

You can't unit test for taste

https://dev.karltryggvason.com/you-cant-unit-test-for-taste/
289•kalli•2d ago•129 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?