frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

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

https://hackerbooks.org
1171•roansh•14h ago•211 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
232•soheilpro•2d ago•150 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/
66•joonehur•4h ago•5 comments

HackerTube: YouTube built from videos recommended by HN

https://karpathy.bearblog.dev/hacker-tube/
2423•karpathy•1d ago•554 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...
69•_Microft•1d ago•23 comments

Trigger.dev customer environment variables exposed

https://trigger.dev/blog/security-incident-nov-2026
53•anurag•4h ago•18 comments

Ask HN: Which TV do you recommend for privacy?

248•LecroJS•10h ago•417 comments

Nibnib: Image compression with extreme decompression speed

https://github.com/raphlinus/nibnib
123•raphlinus•3d ago•21 comments

Tips for more effective fuzz testing with AFL++

https://nullprogram.com/blog/2025/02/05/
100•luu•4d ago•16 comments

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

https://tibleiz.net/copper/
154•bogdanoff_2•2d ago•82 comments

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

https://github.com/ivankovic/omnidiff
198•FabCH•17h ago•46 comments

OccupySaaS

https://occupysaas.com/
164•misswaterfairy•5h ago•109 comments

Keeping Up Appearances – The women taking over the funeral industry

https://lareviewofbooks.org/article/death-industry-mortuary-programs-women-andie-eisen-quarterly/
38•TMWNN•2d ago•20 comments

Proving and improving the Platonic Representation Hypothesis with JEPAs

https://arxiv.org/abs/2610.39302
124•Anon84•16h ago•66 comments

AI fan wikis riddled with errors are muddying the waters of games culture

https://www.eurogamer.net/ai-fan-wikis-errors-complicating-games-culture
59•rdmuser•4h ago•36 comments

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

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

The AI cost of JavaScript frameworks

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

Mathematics has changed. Let's act like it

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

One-minute frequency disturbances from synchronization in power systems

https://www.nature.com/articles/s41560-026-02144-0
137•croes•1d ago•45 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...
439•entryleveljobsc•15h ago•157 comments

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

https://outcrop.rocks/
180•headsupernova•3d ago•41 comments

Bidirectional charging during grid outages

https://www.jefftk.com/p/bidirectional-charging-during-grid-outages
95•luu•1d ago•144 comments

Radiation Map of the World

https://radiaverse.com/
147•slater•4d ago•47 comments

Show HN: I rebuilt my old canvas 3D library as a small WebGL 2 library – phoria2

https://kevs3d.co.uk/phoria2/
84•kevs3d•1d ago•14 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
7•EA-3167•4h ago•0 comments

The She-Wolves of Jülich

https://www.historytoday.com/archive/history-matters/she-wolves-julich
19•Thevet•1d ago•3 comments

Domain hacks with unusual Unicode characters (2018)

https://shkspr.mobi/blog/2018/11/domain-hacks-with-unusual-unicode-characters/
69•n_plus_1_acc•19h ago•49 comments

Novellas with Groff

https://movq.de/blog/postings/2026-10-31/0/POSTING-en.html
118•dverlaeckt80•16h ago•51 comments

Parchment Paper History: How We Got Paper Perfect for Baking (2019)

https://tedium.co/2019/11/21/nonstick-parchment-paper-history/
46•colinprince•2d ago•24 comments

Seoul Viosys begins production of rare-earth-free white light emitter

https://www.semiconductor-today.com/news_items/2026/oct/seoul-291026.shtml
155•gmays•13h ago•43 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?