frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

`123456' password used in Danish CPR data breach

https://cphpost.dk/2026-10-10/news/round-up/123456-password-used-in-massive-danish-cpr-data-breach/
139•baal80spam•2h ago•86 comments

Talorys – A self-hosted personal AI agent on Cloudflare's free tier

https://github.com/rociiu/talorys
34•rociiu•1h ago•11 comments

Apple/macOS silently removed from official Unix registry

https://www.opengroup.org//openbrand/register/
23•john_alan•1h ago•10 comments

REA Reverse – Engineer Anything

https://rea.tools/
476•modinfo•11h ago•193 comments

Telegram Desktop vulnerability allowed any user's file to be stolen

https://beaksec.github.io/posts/telegram-desktop-one-click-account-takeover/
217•g-b-r•9h ago•105 comments

Cloudflare acquires Deno

https://deno.com/blog/cloudflare
1261•ilreb•23h ago•638 comments

Triple-A Minesweeper

https://minesweeper.mikelacher.com/
1052•robin_reala•20h ago•203 comments

Eye of Sauron: Long-Range Hidden Spy Camera Detection (2024)

https://www.usenix.org/conference/usenixsecurity24/presentation/zhang-qibo
182•ortusdux•2d ago•42 comments

Noto means "no tofu": fixing dotted circles in Myanmar text

https://www.datocms.com/blog/handling-less-common-scripts
13•steffoz•3d ago•5 comments

Cube Type – Isometric Typography Generator

https://typeincube.com/
24•eustoria•1d ago•3 comments

Can you use autoregressive diffusion to generate market data?

https://blog.janestreet.com/can-you-use-autoregressive-diffusion-to-generate-market-data/
105•jsomers•21h ago•37 comments

Show HN: Carrier-Explode: iPhone, Pixel and Galaxy carrier settings decoded

https://carrierexplode.com/
342•simplyalec•18h ago•42 comments

WSL3 Performance is about 5-60% faster than WSL2 depending on the workload

https://tonym.us/wsl2-vs-wsl3-benchmarks.html
77•tonymet•2d ago•51 comments

Compiling Rust to readable C with Eurydice

https://lwn.net/Articles/1055211/
92•peter_d_sherman•12h ago•26 comments

How to head into VR without wearing a headset

https://www.kyushu-u.ac.jp/en/researches/view/414/
40•Betelbuddy•3d ago•20 comments

C for Rust Programmers

https://bd103.dev/blog/2026-10-07-c-for-rust-programmers/
9•xyproto•1d ago•2 comments

Computers Cannot Make Decisions

https://wiki.cateat.fish/art:computers_cannot_make_decisions
123•heavensteeth•6h ago•101 comments

Typesafe AI raises $870M at $7.5B

https://typesafe.ai/blog/series-ai
382•tosh•19h ago•292 comments

Clinical trial of a prion disease drug candidate begins enrolling participants

https://www.broadinstitute.org/news/clinical-trial-prion-disease-drug-candidate-begins-enrolling-...
84•luu•12h ago•19 comments

Food processing influences metabolism and brain activity

https://news.vt.edu/articles/2026/10/research_fralinbiomed_upfhutelin.html
58•gmays•6h ago•44 comments

Pointing AI at archives found a forgotten meteorite, lost rhinos, and more

https://jessewaites.com/blog/post/i-pointed-ai-at-400-years-of-archives/
153•piratebroadcast•1d ago•79 comments

What mathematicians should know about the Lean Theorem Prover: reliability & AI

https://terrytao.wordpress.com/2026/10/09/what-mathematicians-should-know-about-the-lean-theorem-...
135•matt_d•18h ago•28 comments

Scam American companies are using to manipulate ingredient lists

https://twitter.com/WallStreetApes/status/2108594998656807078
137•bilsbie•18h ago•150 comments

Show HN: Proton Drive for Linux

https://oss.lsantos.dev/proton-drive-linux-fs/
93•khaosdoctor•2d ago•34 comments

'Wallace and Gromit,' 90% Alone

https://animationobsessive.substack.com/p/wallace-and-gromit-90-alone
230•vinhnx•22h ago•33 comments

The role of cat eye narrowing movements in cat–human communication (2020)

https://www.nature.com/articles/s41598-020-73426-0
94•bushwart•3d ago•40 comments

Our $445M Series D

https://oxide.computer/blog/our-445m-series-d
667•ahlCVA•23h ago•300 comments

Sorry, I'm in a meeting

https://iminafleeting.com/
928•splintersio•1d ago•260 comments

YouTuber Says Cops Visited Him After He Built a Flock-Style Camera to Track Cops

https://gizmodo.com/youtuber-says-cops-paid-him-a-visit-after-he-built-flock-style-camera-to-trac...
598•gumby•15h ago•323 comments

100+ reactions to 100+ solutions

https://proofsandprompts.com/2026/10/08/100-reactions-to-100-solutions/
79•jacobedawson•23h ago•77 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?