frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

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-...
553•ejohnso49•6h ago•282 comments

GitLab Critical Patch Release

https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-released/
155•artooro•3h ago•33 comments

No More Icons in Every Menu by Default

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

AWS rates PHP RCE as Important so Amazon Linux 2023 patch may take 20 days

https://github.com/amazonlinux/amazon-linux-2023/issues/1148
48•hayd•55m ago•10 comments

Compromised LiteLLM 1.107.0 on PyPI Installs a Credential Stealer and Backdoor

https://safedep.io/litellm-pypi-compromise-credential-stealer-backdoor/
366•abhisek•8h ago•120 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...
95•khalidkhair•1d ago•58 comments

Eight Bits of Trust: eMudhra's CA keys cracked in milliseconds

https://scotthelme.co.uk/eight-bits-of-trust-emudhras-ca-keys-cracked-in-milliseconds/
778•hkc•13h ago•384 comments

Google's Rust Style Guide

https://google.github.io/styleguide/rustguide.html
114•kaycebasques•2h ago•81 comments

Claude Duet

https://claude.com/product/claude-duet
219•kuberwastaken•2h ago•191 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
234•cbg0•4h ago•137 comments

DuckDB 2.0.0 LTS “Cinnamon Teal”

https://duckdb.org/2026/10/21/announcing-duckdb-200
332•nnx•8h ago•38 comments

Patch the Planet: global response coordination as agents uncover vulnerabilities

https://openai.com/index/coordinated-disclosure-of-critical-vulnerabilities/
210•nr378•8h ago•133 comments

EA is shutting down BioWare

https://www.theverge.com/games/1015647/ea-is-shutting-down-bioware
414•aaronbrethorst•4h ago•252 comments

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

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

OpenAI models are coming to Google Cloud

https://openai.com/index/openai-models-google-cloud/
192•armcat•9h ago•88 comments

New plastic pollution discovered: 'Plasticorals' coral rubble fused with plastic

https://www.oist.jp/news-center/news/2026/9/18/new-form-plastic-pollution-discovered-shores-vulne...
82•giuliomagnifico•5h ago•22 comments

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

https://apnews.com/article/oregon-waterfall-for-sale-lawmakers-996de63462d49ec3ad9bee1629fb9488
151•surprisetalk•6h ago•80 comments

PHP 8.2.35

https://github.com/php/php-src/releases/tag/php-8.2.35
933•tuyuri•8h ago•521 comments

Using thousands of AI agents to uncover new leads in biological data

https://openai.com/index/scaling-ai-research-for-complex-biological-data/
119•raahelb•8h ago•65 comments

A Place Among the Fiddlers

https://longreads.com/2026/10/01/galax-old-fiddlers-convention-music/
13•gmays•1d ago•0 comments

Potential third critical PHP CVE

https://elk.zone/m.webtoo.ls/@elise@katze.sh/117479383721672027
49•mpaepper•3h ago•16 comments

Canary Tokens

https://canarytokens.org/
92•wiradikusuma•3h ago•18 comments

Drupal is now light-years ahead of its reputation

https://dri.es/state-of-drupal-presentation-september-2026
104•scottfalconer•2d ago•107 comments

The bridge to agent-scale Git infrastructure

https://github.blog/engineering/architecture-optimization/the-bridge-to-agent-scale-git-infrastru...
45•Klaster_1•5h ago•11 comments

Your MCU likely escaped the eMudhra intermediate CA compromise

https://danielmangum.com/posts/mcu-emudhra-intermediate-ca-compromise/
47•hasheddan•6h ago•22 comments

9 Mothers (YC P26) Is Hiring in Austin, TX

https://9mothers.com/careers
1•ukd1•10h ago

Google staff resign in backlash over its AI contracts with military

https://www.bbc.com/news/articles/cmreyvepnv0po
73•saikatsg•2h ago•4 comments

Claude Duet

https://claude.com/resources/articles/claude-duet
26•zaevlad•2h ago•6 comments

CleanFrame: A quieter home screen for Samsung The Frame

https://github.com/nthnclrk/CleanFrame
3•ingve•59m ago•0 comments

Way to Play Super Mario 64: On Apple Vision Pro

https://www.pagetable.com/303
196•frizlab•2d ago•82 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?