frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

mitmproxy adds --emudhra option

https://github.com/mitmproxy/mitmproxy/commit/169234499088fc2c414644a67efaed3d64ae2e3b
327•ahlCVA•4h ago•86 comments

Epic vs. Apple AU:Court Orders Alt App Stores,Sideloading and 3rd Party Payments

https://www.judgments.fedcourt.gov.au/judgments/Judgments/fca/single/2026/2026fca1552
105•Mayzie•2h ago•57 comments

The recently proposed o(n log n) integer multiplication algorithm [pdf]

https://web.maths.unsw.edu.au/~davidharvey/research/subnlogn.pdf
48•craigcitro•1h ago•27 comments

There isn't an easy exploit for this PHP vulnerability

https://eliastaylor.com/noexploit/
271•zkldi•5h ago•134 comments

Security Disclosure

https://blog.railway.com/p/security-disclosure-wednesday-october-21st
367•passenger•6h ago•211 comments

Rust Style Guide

https://google.github.io/styleguide/rustguide.html
244•kaycebasques•9h ago•132 comments

GitLab critical patch release

https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/
274•artooro•9h ago•67 comments

Compromised LiteLLM 1.107.0 on PyPI Installs a Credential Stealer and Backdoor

https://safedep.io/litellm-pypi-compromise-credential-stealer-backdoor/
460•abhisek•14h ago•156 comments

Using LLM for confidence scoring is a bad idea

https://rumple.github.io/blog/2026/10/20/asking-llm-for-confidence.html
28•jimauthors•23h ago•17 comments

Chain of Thought for Humans

https://www.boristhebrave.com/2026/10/18/chain-of-thought-for-humans/
52•ibobev•2d ago•24 comments

LLM Agents Play Pokemon Showdown

https://olivergrabner.com/research/pokemon/
17•grabnero•2h ago•10 comments

Show HN: Omnara – Open-source alternative to Claude Managed Agents

https://github.com/omnara-ai/omnara
43•kmansm27•11h ago•12 comments

Beyond the &

https://lwn.net/Articles/1096028/
27•PaulHoule•1d ago•0 comments

Meta ordered to pay $25B penalty in New Mexico Cambridge Analytica case

https://www.cnbc.com/2026/10/21/meta-new-mexico-cambridge-analytica-penalty.html
436•cbg0•10h ago•279 comments

Postgres recovery_prefetch can cause outages

https://ardentperf.com/2026/10/20/postgres-recovery_prefetch-considered-harmful-and-causing-outages/
11•plaur782•5h ago•0 comments

Code is clay now

https://www.albertodenia.com/writing/code-is-clay-now
123•albertodenia•2d ago•61 comments

PingCap TiDB Leaks

https://fulcrumsec.vg/pingcap/
260•swyx•1d ago•37 comments

Tiny possum and glider thought extinct for 6000 years found in remote West Papua

https://www.bbc.com/news/articles/cp814l80pw2o
167•bryanrasmussen•1d ago•30 comments

No more icons in every menu by default

https://blog.jim-nielsen.com/2026/icons-in-every-menu/
217•riffraff•1d ago•152 comments

Today's PHP security release, and how we're strengthening security

https://thephp.foundation/blog/2026/10/21/todays-php-security-release-and-how-were-strengthening-...
698•ejohnso49•12h ago•343 comments

Clockwork Mechanics, Maintenance, and Metaphors in the Late Middle Ages

https://www.jhiblog.org/2026/10/19/clockwork-metaphors/
4•benbreen•2d ago•0 comments

OpenAI models are coming to Google Cloud

https://openai.com/index/openai-models-google-cloud/
258•armcat•15h ago•107 comments

Show HN: Can you tell an AI's real 30-day memory from a fabricated one?

https://kairos-experiment.com/distinguish.html
8•gcolella•2d ago•1 comments

DuckDB 2.0.0 LTS “Cinnamon Teal”

https://duckdb.org/2026/10/21/announcing-duckdb-200
384•nnx•14h ago•49 comments

Why Windows 11 still ships with Windows 95's memory manager hidden inside it

https://www.windowslatest.com/2026/10/19/why-windows-11-still-ships-with-windows-95s-memory-manag...
154•khalidkhair•2d ago•101 comments

Patch the Planet: global response coordination as agents uncover vulnerabilities

https://openai.com/index/coordinated-disclosure-of-critical-vulnerabilities/
243•nr378•14h ago•164 comments

EA is shutting down BioWare

https://www.theverge.com/games/1015647/ea-is-shutting-down-bioware
574•aaronbrethorst•10h ago•348 comments

Oregon lawmakers approve money to buy an iconic waterfall listed on Redfin

https://apnews.com/article/oregon-waterfall-for-sale-lawmakers-996de63462d49ec3ad9bee1629fb9488
175•surprisetalk•13h ago•89 comments

Launch HN: Alter (YC S25) – Access control for multi-user agents

https://alterauth.com/
56•simfinii•21h ago•24 comments

PHP 8.2.35

https://github.com/php/php-src/releases/tag/php-8.2.35
984•tuyuri•14h ago•535 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?