frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Show HN: HackerBooks – HackerTube, but for books mentioned on HN

https://hackerbooks.org
1496•roansh•20h ago•247 comments

Postgres 19 is late because so many more bugs are being found now

http://rhaas.blogspot.com/2026/10/postgres-19-is-late-and-its-ais-fault.html
551•soheilpro•2d ago•341 comments

Show HN: Wikihack – HackerTube, but for Wikipedia articles mentioned on HN

https://wikihack.netlify.app
250•aizk•7h ago•75 comments

Show HN: I've updated my Linux System Call website and API

https://syscall.sh/
46•guitmz•2h ago•21 comments

HackerTube: YouTube built from videos recommended by HN

https://karpathy.bearblog.dev/hacker-tube/
2640•karpathy•1d ago•582 comments

Supermarket freezers in Belgium and Sweden hit by suspected cyber-attack

https://www.bbc.com/news/articles/cq1kd1nee80eo
29•xqcgrek2•37m ago•20 comments

F/OSS Comics #13: BSD Unix, Part 3 – The Beginning of BSD Unix

https://fosscomics.com/posts/13.%20BSD%20Unix%20Part%203%20-%20The%20Beginning%20of%20BSD%20Unix/
150•joonehur•10h ago•16 comments

Bones may release proteins that slow aging and extend life span

https://www.science.org/content/article/bones-may-release-proteins-slow-aging-and-extend-life-span
136•EA-3167•10h ago•36 comments

Ask HN: Which TV do you recommend for privacy?

460•LecroJS•16h ago•589 comments

Mystery of 60-Second Fluctuations in Power Grids Solved

https://www.fz-juelich.de/en/news/archive/press-release/2026/mystery-of-60-second-fluctuations-in...
159•_Microft•2d ago•72 comments

The future in old computer magazines (1984–2004)

https://tomorrowasusual.substack.com/p/blast-from-the-past-the-future-in
25•tudell•1h ago•7 comments

Show HN: HackerHack – HackerBooks but for Posts Posted on HN

https://news.ycombinator.com/
56•mw888•5h ago•11 comments

Trigger.dev customer environment variables exposed

https://trigger.dev/blog/security-incident-nov-2026
104•anurag•11h ago•48 comments

From Charlemagne to the Kitchen Boy: Reading the Hamburg Rathaus

https://alsterrunde.com/from-charlemagne-to-the-kitchen-boy-reading-the-hamburg-rathaus/
44•mertbio•5h ago•5 comments

Nibnib: Image compression with extreme decompression speed

https://github.com/raphlinus/nibnib
154•raphlinus•3d ago•29 comments

Tips for more effective fuzz testing with AFL++

https://nullprogram.com/blog/2025/02/05/
128•luu•5d ago•25 comments

China's First Frontier AI Export Controls: Mofcom Announcement No. 48

https://labs.cloudsecurityalliance.org/research/csa-research-note-china-ai-export-controls-announ...
65•jonnybgood•4h ago•40 comments

Copper – A minimal low-level programming language with OOP and generics

https://tibleiz.net/copper/
177•bogdanoff_2•2d ago•97 comments

Show HN: OmniDiff – Opensource, super fast, content aware Git difftool, in Rust

https://github.com/ivankovic/omnidiff
268•FabCH•23h ago•75 comments

OccupySaaS

https://occupysaas.com/
334•misswaterfairy•12h ago•198 comments

The AI cost of JavaScript frameworks

https://nolanlawson.com/2026/10/28/the-ai-cost-of-javascript-frameworks/
393•luu•1d ago•301 comments

New 3D thermal invisibility cloak makes objects disappear from infrared cameras

https://www.sciencedaily.com/releases/2026/10/261025073051.htm
89•stevenalowe•3d ago•38 comments

Supermarket freezers across Europe hit by second suspected cyber-attack

https://www.theguardian.com/world/2026/nov/02/supermarket-freezers-across-europe-hit-by-second-su...
6•fergie•35m ago•4 comments

Proving and improving the Platonic Representation Hypothesis with JEPAs

https://arxiv.org/abs/2610.39302
146•Anon84•23h ago•71 comments

Show HN: Point your camera at a landscape to learn about its geology

https://outcrop.rocks/
219•headsupernova•3d ago•47 comments

One-minute frequency disturbances from synchronization in power systems

https://www.nature.com/articles/s41560-026-02144-0
165•croes•2d ago•53 comments

Mathematics has changed. Let's act like it

https://terrytao.wordpress.com/2026/11/01/mathematics-has-changed-lets-act-like-it/
327•smilelamp•17h ago•386 comments

Radiation Map of the World

https://radiaverse.com/
187•slater•4d ago•53 comments

Lenovo's 'encrypted' fingerprint USB is just an unencrypted SD card in a case

https://www.reddit.com/r/technology/comments/1xl2pr3/lenovos_encrypted_fingerprint_usb_drive_is_j...
512•entryleveljobsc•21h ago•167 comments

The She-Wolves of Jülich

https://www.historytoday.com/archive/history-matters/she-wolves-julich
35•Thevet•1d ago•6 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?