frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

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

https://spectrum.ieee.org/ai-in-cybersecurity-php2shell-vulnerability
451•pseudolus•3h ago•314 comments

Guerrilla Bike Lanes: San Francisco Makes Illicit Infrastructure Permanent

https://99percentinvisible.org/article/guerrilla-bike-lanes-san-francisco-makes-illicit-infrastru...
36•zenincognito•45m ago•3 comments

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

https://www.mindstudio.ai/blog/linux-nvidia-rtx-spark-laptop
356•novaRom•7h ago•176 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...
155•smalltech•1h ago•86 comments

Verification Is Not Knowledge: Science needs more than answers

https://blog.cosmos-institute.org/p/verification-is-not-knowledge
148•ersinesen•6h ago•90 comments

Incident with Pull Requests, Git Operations and Issues

https://www.githubstatus.com/incidents/smtdswd1h2w4
184•kevcampb•5h ago•92 comments

Evergreen: A Provably Safe Systems Language

https://evergreenlang.net
5•jordan_bonecut•21m ago•1 comments

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

345•jameslk•5h ago•93 comments

Adding Window Functions to a Spreadsheet

https://www.getgrist.com/blog/running-totals-you-dont-have-to-chase/
8•reedciccio•25m ago•1 comments

Jelly Sheet

https://mrdoob.github.io/codevember-2026/01/
356•memalign•12h ago•91 comments

Debian apt security update (man-in-the-middle)

https://lists.debian.org/debian-security-announce/2026/msg00526.html?pow_referer=
32•SG-•42m ago•3 comments

Letting users trust their own MCP clients, without opening a phishing hole

https://streamvessel.com/blog/mcp-trusted-redirect-uris
3•isalexlog•15m ago•0 comments

Kitty 0.50

https://sw.kovidgoyal.net/kitty/changelog/#
272•porridgeraisin•6h ago•172 comments

Show HN: Codemap – one-page interactive map of any Go repository

https://github.com/peterretief/codemap
3•peter_retief•28m ago•0 comments

Jailbreaking my car's navigation system just so I can change the time

https://blog.nns.ee/2026/11/02/renault-hack/
900•xx_ns•1d ago•337 comments

Stringman, an $800 open-source room scale gripper robot

https://neufangled.com/
707•nharada•22h ago•217 comments

US voters roundly reject data centers in ballot measures

https://www.semafor.com/article/11/04/2026/us-voters-roundly-reject-data-centers-in-ballot-measures
182•justonepost2•1h ago•273 comments

Coffee's new status symbol is a machine without plastic

https://www.cnn.com/2026/11/02/food/coffee-machine-plastic-free
11•thunderbong•26m ago•5 comments

Jaron Lanier on parallels between AI and social media

https://www.youtube.com/watch?v=WxaRn8kX2eI
29•musha68k•1h ago•1 comments

The lost malloc()

https://napcakes.nekoweb.org/posts/malloc/
109•matt_d•8h ago•42 comments

The Internals of PostgreSQL

https://www.interdb.jp/pg/index.html
331•ibobev•17h ago•24 comments

Mocktastic: A Meshtastic Node on Arduino

https://github.com/Vapmuz/Mocktastic
6•kimi•1h ago•0 comments

Synaptics Appears to Use Legal Threats to Block Open-Source DisplayLink Driver

https://www.phoronix.com/news/Synaptics-Blocks-Vino-Driver
98•snvzz•4h ago•34 comments

Show HN: HackerTV – HN's most-recommended Youtube videos as 24/7 TV channels

https://hackertv.org
409•dsalzman•1d ago•76 comments

Giant canyon on Mars is still tectonically active

https://lamont.columbia.edu/news/giant-canyon-mars-still-tectonically-active-today
126•gmays•14h ago•27 comments

Fujifilm to boost tape production 5x as AI fuels archiving demand

https://arstechnica.com/gadgets/2026/10/fujifilm-to-boost-tape-production-5x-as-ai-fuels-archivin...
517•bookofjoe•2d ago•220 comments

Show HN: Uncracked City, detective game where you question LLM suspects that lie

https://uncracked.city
101•passkey1510•18h ago•51 comments

Geoffrey Hinton: it might turn out we were better off without AI

https://www.theguardian.com/uk-news/2026/nov/03/ai-godfather-geoffrey-hinton-better-off-without-ai
245•alkyon•5h ago•198 comments

Distinct cellular and genetic differences in colorectal cancer in young patients

https://www.dana-farber.org/newsroom/news-releases/2026/study-reveals-distinct-cellular-and-genet...
105•gmays•12h ago•43 comments

Pierre Computer is being acquired by OpenAI

https://twitter.com/pierrecomputer/status/2117999036175188183
12•itunpredictable•25m ago•3 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?