frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

AlphaProof Code

https://deepmind.google/blog/introducing-alphaproof-code/
314•ilreb•3h ago•113 comments

NetBSD 11 desktop on a Raspberry Pi 4

https://neongd.com/articles/netbsd11-rpi4.gmi
54•jaypatelani•2d ago•11 comments

Amazon saves millions by replacing Sonnet 4.6 with Strands Decider

https://strandsagents.com/blog/amazon-saves-millions-replacing-sonnet-with-strands-decider/
514•aloukissas•9h ago•185 comments

The Hardest Tarball?

https://stoppels.ch/2026/11/07/the-hardest-tarball.html
20•thatslast•33m ago•1 comments

Claude Fable 5.2 and Mythos 5.2

https://www.anthropic.com/claude-fable-and-mythos-5-2
769•lairv•21h ago•908 comments

Queens Public library under ransomware attack e-borrowing suspended

https://connect.queenslibrary.org/
110•rustyhancock•6h ago•79 comments

Show HN: A 15 MB self-hosted Netflix and Spotify for your media server

https://github.com/HolyArrs/HolyArrs
116•CoderLuii•3h ago•56 comments

Taking another shot at the cheap IP camera, part 2

https://ericswpark.com/blog/2026/2026-11-09-ip-camera-pt2/
22•ericswpark•1d ago•8 comments

Here comes the sun[light]:An ambient Daylight Clock with time and space controls

https://hannahilea.com/blog/daylight-clock/
20•evakhoury•19h ago•0 comments

Show HN: Ghanaian street games you can play in the browser

https://www.ghanastreetgames.com/
59•samuelaidoo45•2d ago•9 comments

USPS now offers official ZIP Code boundary polygons

https://postalpro.usps.com/zcb
690•munro•19h ago•353 comments

Simon Winchester, Author of 'The Professor and the Madman,' Has Died

https://www.nytimes.com/2026/11/04/obituaries/simon-winchester-dead.html
36•benbreen•2d ago•10 comments

Ableton Live 13

https://www.ableton.com/en/live/
114•phaser•2h ago•120 comments

'C:\> FORMAT C:' – relax, it's just a screen saver

https://fakedos.com/
48•TheIncredibleCh•5h ago•34 comments

Let over Lambda–50 Years of Lisp (2008)

https://letoverlambda.com/
23•theanonymousone•2h ago•3 comments

Your TV can see through walls (2025)

https://maurycyz.com/projects/fading/
220•Curiositry•10h ago•96 comments

Fireworks AI security breach impacts Notion and their customers

https://www.notion.com/help/security-incident-involving-a-third-party-ai-vendor
116•werrett•8h ago•40 comments

Anthropic launches roadshow for proposed initial public offering

https://www.anthropic.com/news/roadshow-launch
19•davidbarker•3h ago•20 comments

Building an Order RISC-V CPU from scratch

https://prawns.dev/blogs/specula
5•random__duck•4d ago•2 comments

Foldable Flight: The Best Paper Airplanes

https://www.foldableflight.com
1123•vismit2000•1d ago•158 comments

Billion Watts in the Speaker [video]

https://www.youtube.com/watch?v=PHOcTXYaMfg
69•Element_•2d ago•34 comments

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

https://e-means.github.io/
459•porridgeraisin•20h ago•62 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...
563•ocd•23h ago•324 comments

Locating the source of a mysterious beep

https://simonwillison.net/2026/Nov/9/mysterious-beeps/
265•bigwheels•15h ago•135 comments

How hard is it to check for whitespace?

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

Horible public key tricks

https://maurycyz.com/projects/badcert/
215•Curiositry•15h ago•73 comments

Ultorg: The User Interface for Relational Databases

https://www.ultorg.com/
116•Ivoah•11h ago•39 comments

What's new in the .NET 11 runtime

https://learn.microsoft.com/en-us/dotnet/core/whats-new/dotnet-11/runtime
61•stevefan1999•3h ago•19 comments

ClickHouse Acquires Xata

https://xata.io/blog/xata-is-joining-clickhouse
79•mebcitto•9h ago•7 comments

Semi-transparent, colored cadmium telluride photovoltaic panels in agrivoltaics

https://www.anthropocenemagazine.org/2026/10/magenta-solar-panels-may-be-agrivoltaics-cleverest-t...
339•speckx•1d ago•228 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?