frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Meta’s new commercial terms will allow the scraping of news sites: experts

https://www.niemanlab.org/2026/10/metas-new-commercial-terms-will-allow-the-scraping-of-news-site...
277•0in•9h ago•101 comments

Muse Spark Open

https://research.meta.ai/blog/muse-spark-open
801•bigwheels•15h ago•400 comments

New York City's iconic horse-drawn carriages expected to take their last trot

https://www.cnn.com/2026/10/13/us/nyc-horse-carriage-ban
35•1659447091•2d ago•21 comments

Woman who rescued injured crow keeps getting 'thank-you gifts' from birds [video]

https://www.youtube.com/watch?v=sjNpfz4UzqU
270•johnnyApplePRNG•3d ago•75 comments

The insider trading you're allowed to do

https://coached.com/essays/the-insider-trading-youre-allowed-to-do/
16•rohanm93•2h ago•5 comments

RPKI now protects 70% of internet routes

https://ipinfo.io/blog/rpki-protects-70-internet-routes
150•emot•8h ago•42 comments

The Folders Programming Language

https://danieltemkin.com/esolangs/folders
46•gurst•4h ago•7 comments

Neural networks are clean

https://already-clean.goodfire.com/
679•themgt•17h ago•248 comments

What I self-host

https://viceconsole.fyi/blog/2026/10/10/what-i-self-host/
473•BrunoBernardino•12h ago•295 comments

'500-hour' Order of the Sinking Star is as complex and exhausting as it sounds

https://www.polygon.com/order-of-the-sinking-star-impressions/
138•cvoss•2d ago•83 comments

Two-Stack Sliding-Window Aggregation

https://orlp.net/blog/two-stack-sliding-window-aggregation/
7•surprisetalk•2d ago•0 comments

New Withings Users Must Pay $99/Year for Apple Health Syncing

https://support.withings.com/hc/en-us/community/posts/51887047154577-Unacceptable-Apple-Health-Sy...
283•johnbehnke•13h ago•182 comments

Wayland desktop for Linux with skeuomorphic design

https://github.com/fyzugx/DEsk
604•FinalDestiny•19h ago•236 comments

Apple routed a graphite pipe through the iPhone Duo's hinge to dissipate heat

https://www.pcmag.com/news/apple-routed-a-graphite-pipe-through-the-iphone-duos-hinge
133•giuliomagnifico•3d ago•94 comments

Jev meets the Trolley Problem

https://zachlandes.com/trolley-problem/
448•zlandes86•16h ago•192 comments

BIPM decides to stop adding leap seconds to UTC

https://www.bipm.org/en/cgpm-2026/resolution-5
174•gliffie•17h ago•80 comments

Any window from your Mac, on your iPhone and iPad

https://github.com/Saffsanity/sill
141•chanana•7h ago•33 comments

Last rites for Gentoo's Chromium package

https://lwn.net/Articles/1097760/
53•signa11•4h ago•40 comments

The Economic Complexity of the Western Roman Empire

https://www.michelecoscia.com/?p=2613
6•mikk14•1d ago•0 comments

Someone on Torrent Sites Kept Fucking with My Sonarr

https://thereallo.dev/blog/someone-on-torrent-sites-kept-fucking-with-my-sonarr-setup
339•speckx•13h ago•151 comments

Celebrating 70 Years of Fortran

https://fortran-lang.org/news/2026/09-15-Fortran-birthday/
273•rbanffy•18h ago•111 comments

Krea 3 – An image model built for editing at scale

https://www.krea.ai/krea-3
307•dvrp•17h ago•97 comments

Comparing Chromium Development at Google and Igalia

https://lwn.net/Articles/1094721/
44•signa11•7h ago•15 comments

Thank You, Deno

https://www.vlt.io/blog/competition-keeps-javascript-moving
74•jcbhmr•8h ago•12 comments

Why I Wrote PGP (1991, revised 1999)

https://philzimmermann.com/EN/essays/WhyIWrotePGP.html
156•GaryBluto•1d ago•54 comments

Libreboot 26.10 "Ominous Olive" released with UEFI, Chromebook support

https://libreboot.org/news/libreboot2610.html
288•iamnothere•20h ago•173 comments

Delta’s Biscoff cookies were supposed to be temporary

https://www.seriouseats.com/biscoff-history-12168161
219•mhb•2d ago•171 comments

Major ICQ security hole (1998)

https://opennet.ru/base/maillist/169.txt.html
84•sysoleg•2d ago•48 comments

Using AI to reverse engineer hardware

https://blogs.gnome.org/uraeus/2026/10/15/aiandreverseengineerhardware/
189•ErenayDev•18h ago•172 comments

BeBox is a Haiku application that emulates Be Inc.'s BeBox

https://github.com/johnrash/bebox
59•rguiscard•9h ago•15 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?