frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

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

https://expression.fire.org/p/the-papers-please-era-of-the-internet
190•bilsbie•1h ago•68 comments

An entire Herculaneum scroll has been read for the first time

https://scrollprize.org/firstscroll
838•verditelabs•7h ago•195 comments

Un-0: Generating Images with Coupled Oscillators

https://unconv.ai/blog/introducing-un-0-generating-images-with-coupled-oscillators/
74•babelfish•2h ago•9 comments

Oxide computer 3D rack guided tour

https://explorer.oxide.computer/
260•darthcloud•3d ago•109 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
41•exploraz•2d ago•11 comments

IBM debuts sub-1 nanometer chip technology

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

An oral history of Bank Python (2021)

https://calpaterson.com/bank-python.html
44•tosh•3h ago•10 comments

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

https://github.com/inkeep/open-knowledge
160•engomez•7h ago•77 comments

Om Malik has died

https://om.co/2026/06/24/1966-2026/
247•minimaxir•2h ago•23 comments

Parallel Parentheses Matching

https://williamdue.github.io/blog/parallel-parentheses-matching
35•Athas•3h ago•6 comments

Migrating from Proxmox to NixOS and Incus

https://www.nijho.lt/post/proxmox-to-nixos/
23•wasting_time•2h ago•5 comments

Show HN: Chess-Inspired Roguelike

https://princechazz.com
185•cowboy_henk•4d ago•66 comments

Zig's new bitCast semantics and LLVM back end improvements

https://ziglang.org/devlog/2026/#2026-06-25
202•kouosi•9h ago•79 comments

OS9Map

https://yllan.org/software/OS9Map/
163•LaSombra•8h ago•23 comments

Apple raises prices of MacBooks, iPads

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

The annotated PyTorch training loop

https://idlemachines.co.uk/essays/pytorch-training-loop
49•smaddrellmander•2d ago•9 comments

GloriousEggroll's Proton has been rebased on Proton 11

https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/GE-Proton11-1
45•d3Xt3r•1d ago•12 comments

You can't unit test for taste

https://dev.karltryggvason.com/you-cant-unit-test-for-taste/
234•kalli•1d ago•113 comments

Besimple AI (YC P25) Is Hiring

https://www.ycombinator.com/companies/besimple-ai/jobs/yWfhhOR-strategic-projects-lead-audio-data
1•yzhong94•6h ago

OpenAI Leans Toward Waiting Until Next Year for IPO

https://www.nytimes.com/2026/06/25/technology/openai-ipo-artificial-intelligence.html
74•mfiguiere•2h ago•47 comments

Advanced Nintendo Entertainment System (ANES) – NES Modded to Use 2 PPUs

https://github.com/decrazyo/anes
90•zdw•2d ago•30 comments

Military branches restore flu shot requirement after virus swept through base

https://arstechnica.com/health/2026/06/military-branches-restore-flu-shot-requirement-after-virus...
25•tzs•1h ago•7 comments

RRB-Trees: Efficient Immutable Vectors (2012) [pdf]

https://infoscience.epfl.ch/server/api/core/bitstreams/e5d662ea-1e8d-4dda-b917-8cbb8bb40bf9/content
29•azhenley•1d ago•7 comments

Show HN: I made Google Trends for Hacker News by indexing 18 years of comments

https://hackernewstrends.com
623•ytkimirti•9h ago•143 comments

Political bias in AI: Where the AI models stand

https://trakkr.ai/bias
100•mektrik•10h ago•198 comments

The disappearance of Japan's animators

https://economist.com/interactive/1843/2026/06/19/the-strange-disappearance-of-japans-animators
129•andsoitis•4d ago•103 comments

Tw-fade: pure CSS scroll-driven edge masking

https://pete.design/tw-fade
80•petekp•3d ago•30 comments

I built a GPU back end for Emacs

https://en.andros.dev/blog/4b707a03/how-i-built-a-gpu-backend-for-emacs/
167•andros•2d ago•83 comments

CAD vs. CAD Tournament

https://www.tootalltoby.com/Tournaments/
4•dgellow•4d ago•0 comments

How physicists track and trap the elusive neutrino

https://www.quantamagazine.org/how-physicists-track-and-trap-the-elusive-neutrino-20260624/
48•ibobev•8h ago•25 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?