frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Claude Fable 5.2 and Mythos 5.2

https://www.anthropic.com/claude-fable-and-mythos-5-2
177•lairv•8h ago•595 comments

USPS now offers official ZIP Code boundary polygons

https://postalpro.usps.com/zcb
494•munro•6h ago•259 comments

Fable 5.2 one-shotted my nephew's dream game

https://notesbylex.com/fable-5-2-one-shotted-my-nephews-dream-game
177•lexandstuff•3h ago•125 comments

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

https://e-means.github.io/
278•porridgeraisin•7h ago•20 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...
476•ocd•10h ago•261 comments

Foldable Flight: The Best Paper Airplanes

https://www.foldableflight.com
861•vismit2000•14h ago•140 comments

Horible public key tricks

https://maurycyz.com/projects/badcert/
35•Curiositry•2h ago•12 comments

Locating the source of a mysterious beep

https://simonwillison.net/2026/Nov/9/mysterious-beeps/
16•bigwheels•2h ago•6 comments

Exact – a new cross platform UI framework

https://github.com/expo/exact
52•vmg12•3h ago•24 comments

Semi-transparent, colored cadmium telluride photovoltaic panels in agrivoltaics

https://www.anthropocenemagazine.org/2026/10/magenta-solar-panels-may-be-agrivoltaics-cleverest-t...
284•speckx•12h ago•181 comments

Never Gonna Print You Up

https://dixken.de/blog/never-gonna-print-you-up
13•ta988•1d ago•0 comments

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

https://www.infineon.com/press-release/2026/infpr202611-028
103•sshah03•8h ago•62 comments

A primer on GPUs and kernel optimization

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

TPU 8tx and TPU 8i Max

https://blog.google/innovation-and-ai/infrastructure-and-cloud/global-network/tpu-8i-max-and-8tx/
214•_benx_•4h ago•63 comments

Muse Ember: Our smallest, most efficient model

https://research.meta.ai/blog/muse-ember
255•dvaplima•8h ago•105 comments

Google Gemini routes personal Drive files and emails to human annotators

https://github.com/thisisme6598/gemini_files/
442•gf74918•8h ago•102 comments

An Aggregate Is a Function, Not a Sum

https://alnovis.io/blog/aggregate-is-a-function
6•alnovis•4d ago•0 comments

Parking-app convenience fees in 312 U.S. cities (median $0.35 per session)

https://parkgraph.com/parking-app-fees
60•parkgraph•6h ago•35 comments

Claude Fable 5.2 scores 65 on Artificial Analysis, highest so far

https://artificialanalysis.ai/models/claude-fable-5-2
296•theanonymousone•6h ago•215 comments

Show HN: MeowDisplay Is iPhone Mirroring, but in Reverse

https://meowdisplay.app/
76•raiseCatError•7h ago•29 comments

CUI – Native UI components for C

https://yappologistic.github.io/CUI/
155•hilti•7h ago•82 comments

An ode to livelyness analysis; SSA to registers

https://xnacly.me/posts/2026/an-ode-to-livelyness-analysis/
33•xnacly•2d ago•0 comments

Y/N (YC S23) is hiring a growth lead to distribute superhuman A.I. storytelling

https://www.ycombinator.com/companies/yn/jobs/TjDn3YZ-founding-growth-marketer
1•gabrielbirnbaum•9h ago

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

https://www.watched.earth
236•a585gupt•8h ago•43 comments

What is malloc doing, anyway?

https://benmandrew.com/articles/what-is-malloc-doing-anyway
227•benmandrew•15h ago•62 comments

A renowned scientist, a deadly snakebite, and a diary that documented it (2025)

https://www.cbsnews.com/chicago/news/field-museum-karl-patterson-schmidt-deadly-snakebite-diary/
10•areoform•2d ago•5 comments

Show HN: Someone Was Here – Find out who used your Mac while you were away

https://someonewashere.app/
65•4onthefloor124•7h ago•25 comments

Deuterium's Impact on OLED Displays (2024)

https://www.oled-info.com/deuteriums-impact-oled-displays
33•zeristor•1d ago•12 comments

Possible 19th-century castaway camp found on Isla de los Estados

https://phys.org/news/2026-11-archaeologists-uncover-19th-century-castaway.html
20•titusblair•3d ago•3 comments

Magnets and Rare Earths

https://robodienst.com/learning-paths/magnets-and-rare-earths
17•Bluestein•2d ago•2 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?