frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Show HN: To Honor Sir Patrick Stewart, Enjoy the TNG Episode Guessing Game

https://tng.episodle.com/
130•francisofascii•5h ago•41 comments

Backdoor in Claude Code for VS Code extension on the Cursor Marketplace

https://phorion.io/blog/offical-claude-code-vsx-compromise/
843•_chall•21h ago•506 comments

Cloudflare Turnstile solver library (no headless browser required)

https://github.com/chris124567/cfsolve
132•costco•2d ago•36 comments

My favourite PowerMac is a Nintendo Wii

https://virtuallyfun.com/2026/10/29/my-favourite-powermac-is-a-nintendo-wii/
268•DHowett•11h ago•77 comments

Tell HN: Scribd Breached

86•x______________•2h ago•30 comments

Northflank Breached

https://status.northflank.com
393•js4ever•13h ago•292 comments

The $6.3B Binance hack was pulled off in just 20 minutes

https://www.wired.com/story/the-dollar63-billion-binance-hack-was-pulled-off-in-just-20-minutes/
381•domhudson•16h ago•260 comments

Breaking the open web won't stop the bad bots

https://www.techpolicy.press/breaking-the-open-web-wont-stop-the-bad-bots/
219•raybb•3d ago•101 comments

Flock camera searches fell 95% after a dispatcher's misconduct was caught

https://www.wkyc.com/article/news/investigations/flock-camera-searches-fall-95-percent-highland-h...
42•MilnerRoute•2h ago•6 comments

Show HN: A working Nintendo in ~1GB of Qwen weights

https://github.com/dbreunig/nesformer
217•dbreunig•12h ago•118 comments

The oldest ice disappears and the Stone Age emerges from it

https://www.sciencenorway.no/archaeology-climate-culture/the-oldest-ice-is-disappearing-the-stone...
114•dxs•8h ago•47 comments

Double Buffering with Cloudflare Queues

https://bellone.com/technical/double-buffering-with-cloudflare-queues
11•b_llc•2d ago•2 comments

sanstun: A sans-IO, parallel-friendly WireGuard implementation in Rust

https://www.firezone.dev/blog/introducing-sanstun
95•wh33zle•7h ago•17 comments

Infinite Mac: BeOS

https://blog.persistent.info/2026/10/infinite-mac-beos.html
127•ecliptik•9h ago•52 comments

OpenAI raises less than half of $30B target

https://www.wsj.com/tech/ai/openai-raises-less-than-half-of-30-billion-target-in-latest-round-91a...
42•timr•1h ago•13 comments

Florilegium: Procedural Flowers in LaTeX

https://github.com/kevinraymond/florilegium
234•nanna•13h ago•43 comments

Jules Verne's Lost Novel

https://blue-continuum.com/verne-paris
90•dnetesn•8h ago•19 comments

The federated code forge

https://tangled.org/blog/forge/
251•zlliang•13h ago•82 comments

Through Captain Jean-Luc Picard, Patrick Stewart taught us the measure of a man

https://www.bostonglobe.com/2026/10/29/metro/patrick-stewart-picard-star-trek-the-next-generation/
263•apress•8h ago•145 comments

Azure's Weakest Link – Five Full Cross-Tenant Compromises

https://www.binarysecurity.no/posts/2026/10/one-root-case
283•swq115•18h ago•56 comments

Trapped in the Technologist Factory

https://ideolalia.com/essays/trapped-in-the-technologist-factory.html
17•luu•2d ago•7 comments

Cisco gives engineer unlimited AI tokens to rewrite legacy code

https://fortune.com/2026/10/30/cisco-president-jeetu-patel-gen-z-27-year-old-unlimited-ai-tokens-...
139•taubek•14h ago•173 comments

Longitudinal Changes InWearable-Captured PhysiologyBefore Sudden Cardiac Death

https://www.jacc.org/doi/epdf/10.1016/j.jaccas.2026.110397
3•brandonb•2d ago•1 comments

Turning a solar power system into its own backup

https://arstechnica.com/science/2026/10/turning-a-solar-power-system-into-its-own-backup/
40•PaulHoule•1d ago•12 comments

Tree-mounted machines connect to web app to let users knock on wood remotely

https://www.designboom.com/technology/tree-mounted-machines-web-app-users-knock-on-wood-remotely/
75•surprisetalk•3d ago•32 comments

Building an AI-native engineering org

https://twitter.com/sgondala2/status/2115832070274723875
122•sgondala_ycapp•1d ago•164 comments

Show HN: I rebuilt Kubernetes for ESP32 microcontrollers

https://github.com/arterialist/kube32
27•Arterialist•1d ago•2 comments

Sleep framework: A new way for LLMs to retain knowledge in continual learning

https://research.google/blog/the-sleep-framework-a-new-way-for-llms-to-retain-knowledge-in-contin...
186•acossta•2d ago•20 comments

Wonderful Weather: Floods and Foreboding in 17th-Century Britain

https://publicdomainreview.org/essay/wonderful-weather/
14•Thevet•2d ago•0 comments

AI isn't replacing SREs, it's deskilling them

https://newsletter.signoz.io/p/ai-isnt-replacing-sres-its-deskilling
538•dorianniemiec•12h ago•404 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?