frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

OpenLogi

https://openlogi.org/en
716•amatheus•8h ago•205 comments

Cerebras CS-4

https://www.cerebras.ai/cs4
287•sunils34•10h ago•201 comments

The Two Factions of C++

https://herecomesthemoon.net/2024/11/two-factions-of-cpp/
30•signa11•3d ago•17 comments

Being ambitious and being a dad

https://nicholascharriere.com/blog/being-ambitious-and-being-a-dad/
509•nichochar•2d ago•321 comments

Palomar: A registry of Lean verified mathematics

https://terrytao.wordpress.com/2026/08/18/palomar-a-registry-of-lean-verified-mathematics/
106•matt_d•7h ago•17 comments

Supersonic Trebuchet [video]

https://www.youtube.com/watch?v=Co57SfcT-h0
111•CharlesW•4d ago•39 comments

A 3D fruit fly on macOS desktop powered by the real FlyWire connectome

https://github.com/DenisSergeevitch/desktop-fly
285•phoenix120•12h ago•106 comments

Scientists stunned by children's lung recovery in ultra low emission zone

https://www.bbc.com/news/articles/c1l1r1zne1ro
270•dabinat•9h ago•202 comments

How does IKEA come up with names for its products?

https://www.ikea.com/se/en/customer-service/knowledge/articles/6f564c4d-2ccc-46de-b643-545a3948dc...
350•NaOH•16h ago•241 comments

Solo – a .so loader for static Linux binaries

https://github.com/pg83/solo
145•zX41ZdbW•10h ago•162 comments

λλ: A Programming Language for Silicon Photonics

https://dl.acm.org/doi/10.1145/3789240.3829151
25•matt_d•4h ago•6 comments

Where Human Sleep Went Wrong

https://nautil.us/where-human-sleep-went-wrong-1283797
63•XzetaU8•2h ago•48 comments

Activation Energy is a good model for a lot of things

https://homosabiens.substack.com/p/activation-energy-is-a-good-model
9•surprisetalk•4d ago•0 comments

The Vietnam Binh Chau (Chau Tan) Late Tang Wreck

https://www.koh-antique.com/client/tangwreck/tangwreck.html
41•teleforce•8h ago•3 comments

The Mojo language (by Modular, now Qualcomm) is now open-source

https://www.modular.com/blog/modcon-announcements
52•flaburgan•2h ago•17 comments

AI usage patterns in software teams

https://linear.app/data
142•giuliomagnifico•12h ago•82 comments

Finger: the 1971 social network that never died

https://en.andros.dev/blog/54572bc7/finger-the-1971-social-network-that-never-died/
219•andros•1d ago•69 comments

Show HN: Automatically detect and patch walking-dead states in Sierra games

https://github.com/katiahayati/lucasartsifier/
66•wkfauna•8h ago•23 comments

CUDA Shared Memory Swizzling

https://leimao.github.io/blog/CUDA-Shared-Memory-Swizzling/
51•jxmorris12•5d ago•2 comments

Turbovec – Google's TurboQuant for vector search in Rust

https://github.com/RyanCodrai/turbovec
252•fittingopposite•16h ago•31 comments

A 25-year-old video patent just expired, ending a legal headache for Linux

https://www.xda-developers.com/25-year-old-brazilian-video-patent-expired-legal-headache-linux/
195•theanonymousone•3d ago•83 comments

Meta's blockbuster trial draws parallels to big tobacco

https://www.economist.com/business/2026/08/18/metas-blockbuster-trial-draws-parallels-to-big-tobacco
238•newsomix9xl•8h ago•190 comments

Claude writing a macOS driver for my obscure HP printer built only for Windows

https://twitter.com/kuberwastaken/status/2089377982536388964
205•porridgeraisin•22h ago•162 comments

And then the men with guns tell you to do it anyway

https://shkspr.mobi/blog/2026/08/and-then-the-men-with-guns-tell-you-to-do-it-anyway/
324•_djo_•17h ago•208 comments

The Amazon tax

https://seths.blog/2026/08/the-amazon-tax/
1185•herbertl•21h ago•631 comments

Show HN: Interactive, animated architecture of any HuggingFace models

https://modelmap.cc
83•lizhaoliu•10h ago•9 comments

Looking for Missed Alarm Bugs in a Formal Verification Tool

https://blog.regehr.org/archives/2124
14•luu•5d ago•0 comments

Apple announces changes for apps in the European Union

https://www.apple.com/newsroom/2026/08/apple-announces-changes-for-apps-in-the-european-union/
202•newusertoday•18h ago•286 comments

Tiny satellite will use the dark side of the Moon as a shield

https://www.cam.ac.uk/research/news/tiny-satellite-will-use-the-dark-side-of-the-moon-to-eavesdro...
42•NordStreamYacht•9h ago•7 comments

Beware Management Consultants

https://about.iceland.co.uk/our-story/the-dark-ages/beware-management-consultants/
553•KolmogorovComp•15h ago•149 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?