frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Amazon saves millions by replacing Sonnet 4.6 with Strands Decider

https://strandsagents.com/blog/amazon-saves-millions-replacing-sonnet-with-strands-decider/
242•aloukissas•3h ago•80 comments

Claude Fable 5.2 and Mythos 5.2

https://www.anthropic.com/claude-fable-and-mythos-5-2
556•lairv•15h ago•780 comments

USPS now offers official ZIP Code boundary polygons

https://postalpro.usps.com/zcb
614•munro•13h ago•309 comments

Your TV can see through walls

https://maurycyz.com/projects/fading/
88•Curiositry•3h ago•27 comments

Locating the source of a mysterious beep

https://simonwillison.net/2026/Nov/9/mysterious-beeps/
172•bigwheels•9h ago•77 comments

Queens Public library under ransomware attack e-borrowing suspended

https://connect.queenslibrary.org/
5•rustyhancock•15m ago•1 comments

E-means: Outperforming k-means in one-tenth the epochs

https://e-means.github.io/
396•porridgeraisin•14h ago•37 comments

Payments Canada announces launch of Canada's Real-Time Rail (RTR) payment system

https://www.payments.ca/canada-launches-real-time-rail-bringing-247-payment-infrastructure-nation...
529•ocd•17h ago•284 comments

Foldable Flight: The Best Paper Airplanes

https://www.foldableflight.com
1009•vismit2000•21h ago•149 comments

Horible public key tricks

https://maurycyz.com/projects/badcert/
158•Curiositry•9h ago•47 comments

Ultorg: The User Interface for Relational Databases

https://www.ultorg.com/
60•Ivoah•5h ago•17 comments

Fireworks AI security breach impacts Notion and their customers

https://www.notion.com/help/security-incident-involving-a-third-party-ai-vendor
19•werrett•2h ago•4 comments

ClickHouse Acquires Xata

https://xata.io/blog/xata-is-joining-clickhouse
18•mebcitto•3h ago•2 comments

How hard is it to check for whitespace?

https://serce.me/posts/2026-10-30-how-hard-is-it-to-check-for-whitespace
8•theanonymousone•3d ago•0 comments

A failed experiment in laptop cooling

https://kevinboone.me/failed_cooling.html
33•andsoitis•2d ago•30 comments

Semi-transparent, colored cadmium telluride photovoltaic panels in agrivoltaics

https://www.anthropocenemagazine.org/2026/10/magenta-solar-panels-may-be-agrivoltaics-cleverest-t...
312•speckx•18h ago•207 comments

Formalizing CPython

https://broyojo.com/python-formalization/
64•carnevalem•7h ago•26 comments

M John Harrison becomes first science fiction author to win the Booker prize

https://www.theguardian.com/books/2026/nov/09/m-john-harrison-the-end-of-everything-wins-2026-boo...
39•sorokod•1h ago•14 comments

CoreWeave bond yield tops 16% as AI credit stress rises

https://www.cnbc.com/2026/11/06/coreweave-bond-yield-tops-16percent-as-ai-credit-stress-rises.html
141•lxm•6h ago•101 comments

The first 300-millimeter power silicon carbide (SiC) wafer

https://www.infineon.com/press-release/2026/infpr202611-028
137•sshah03•14h ago•72 comments

A primer on GPUs and kernel optimization

https://www.nabo.dev/blogs/kernel-primer
146•nomi_uw•4d ago•14 comments

Show HN: Every satellite that passed over any place this week, and its photos

https://www.watched.earth
342•a585gupt•15h ago•60 comments

Google Gemini routes personal Drive files and emails to human annotators

https://github.com/thisisme6598/gemini_files/
588•gf74918•14h ago•128 comments

Muse Ember: Our smallest, most efficient model

https://research.meta.ai/blog/muse-ember
297•dvaplima•15h ago•122 comments

Fable 5.2 one-shotted my nephew's dream game

https://notesbylex.com/fable-5-2-one-shotted-my-nephews-dream-game
386•lexandstuff•10h ago•267 comments

On Being an Engineer in 2026

https://twitter.com/shaharglazner/status/2119796029256032278
101•talboren•18h ago•145 comments

Never Gonna Print You Up

https://dixken.de/blog/never-gonna-print-you-up
41•ta988•2d ago•2 comments

Time for AVIF everywhere?

https://www.michaelponders.com/2026/11/isnt-it-time-for-avif-everywhere.html
74•speckx•2d ago•58 comments

Show HN: MeowDisplay Is iPhone Mirroring, but in Reverse

https://meowdisplay.app/
98•raiseCatError•14h ago•37 comments

S.t.a.l.k.e.r. Call of Pripyat in WASM and WebGPU

https://stalker-online.xyz/
4•roman01la•2h ago•0 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?