frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Residential proxies detected on White House network

https://layer3intel.com/blog/residential-proxies-white-house-network
356•Rasbora•1h ago•100 comments

Insects don't swarm at LED lights

https://www.birdsoutsidemywindow.org/2026/11/03/insects-dont-swarm-at-led-lights/
108•speckx•2h ago•62 comments

Ripple-65B Preview: U.S. Open-Weight SOTA on Agentic Coding

https://www.ricursive.com/ripple
163•Philpax•3h ago•58 comments

AI is forcing us to pay off 40 years of technical debt

https://spectrum.ieee.org/ai-in-cybersecurity-php2shell-vulnerability
977•pseudolus•10h ago•593 comments

A new Go API for JSON

https://go.dev/blog/jsonv2
174•olexsmir•4h ago•71 comments

Qualcomm Cloud AI 100 Ultra – 150W AI Accelerator Card with 128GB at 548GB/s

https://www.qualcomm.com/data-center/products/cloud-ai-100-ultra
63•peter_d_sherman•2h ago•30 comments

Progress on provable inference for large language models

https://www.anthropic.com/research/provable-inference
151•ltononro•5h ago•75 comments

Hacking the Xbox 360 Hypervisor Part 3: Bad Update Improvements

https://icode4.coffee/?p=1746
7•muricula•31m ago•1 comments

Nvidia RTX Spark encrypted firmware slows inference speed to 35% on Linux

https://www.mindstudio.ai/blog/linux-nvidia-rtx-spark-laptop
568•novaRom•13h ago•263 comments

Show HN: After a decade of reversing, I got co-op working in DOS Wing Commander

https://fireflyk64.github.io/wcmulti/
66•daniel_rh•3h ago•4 comments

Conductor Is Joining Meta

https://www.conductor.build/announcement
61•kenrose•4h ago•111 comments

Launch HN: Kino AI (YC S23) – AI media manager and video editor

56•lukeigel•5h ago•24 comments

OpenAI to acquire Pierre Computer Company

https://openai.com/index/openai-to-acquire-pierre/
139•itunpredictable•7h ago•49 comments

Tencent Hy4

https://hy.tencent.ai/research/hy4
156•Philpax•8h ago•47 comments

AMD expects to outsell Intel in Q4 for the first time in history

https://www.tomshardware.com/pc-components/cpus/amd-expects-to-outsell-intel-in-q4-for-the-first-...
413•rbanffy•6h ago•133 comments

Ask HN: What Cryptography book do you recommend for reading with 10 year olds?

19•mike_richards•1d ago•22 comments

Ask HN: What your experience with the monthly "who wants to be hired" thread?

15•newswangerd•15m ago•3 comments

Verification Is Not Knowledge: Science needs more than answers

https://blog.cosmos-institute.org/p/verification-is-not-knowledge
213•ersinesen•13h ago•125 comments

North Korean fake job interview led to $6.3B Binance heist

https://www.theregister.com/security/2026/11/03/north-korean-fake-job-interview-led-to-63b-binanc...
532•smalltech•8h ago•317 comments

Incident with Pull Requests, Git Operations and Issues

https://www.githubstatus.com/incidents/smtdswd1h2w4
242•kevcampb•12h ago•121 comments

Show HN: The DNA of DOOM – How code structure survives across 44 ports

https://squid-protocol.github.io/gitgalaxy/museum-of-code/doom-dna/
5•joe-esquibel•2d ago•5 comments

Tell HN: Gemini trains on chat history, even for subscribers (personal accounts)

592•jameslk•12h ago•150 comments

Kimi K3.1 Pro model weights are out

https://huggingface.co/moonshotai/Kimi-K3.1-Pro
300•abrarthought•7h ago•79 comments

Show HN: I built a tool that prices a prebuilt PC part by part

https://pcdealcheck.com/
82•adlep•7h ago•57 comments

If you're on Replit Pro, you have until November 8 to opt out of arbitration

https://readthediff.substack.com/p/replit-pro-arbitration-opt-out-november-8
35•MiguelSosa•1h ago•1 comments

Guerrilla bike lanes: San Francisco makes illicit infrastructure permanent (2016)

https://99percentinvisible.org/article/guerrilla-bike-lanes-san-francisco-makes-illicit-infrastru...
229•zenincognito•7h ago•164 comments

Evergreen: A Provably Safe Systems Language

https://evergreenlang.net
93•jordan_bonecut•7h ago•80 comments

From wild to mild: Friendly foxes show changes in brain region

https://news.cornell.edu/stories/2026/11/wild-mild-friendly-foxes-show-changes-brain-region
24•gmays•4h ago•2 comments

Benchfmt.rs: Bringing Go's benchmarking and benchstat workflow to Rust

https://www.bwplotka.dev/2026/rust-microbenchmarks-benchstat/
26•witcher•4h ago•4 comments

Everything is an AI scam now

https://www.davidralphlewis.co.uk/posts/everything-is-an-ai-scam-now/
89•speckx•1h ago•24 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?