frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

RamenHaus

https://ramen.haus/
54•oler•1h ago•15 comments

AI doesn't generate working products, that's still your job

https://weeraman.com/the-prototype-isnt-the-product/
32•smckk•1h ago•13 comments

Elevators

https://john.fun/elevators
1298•Jrh0203•18h ago•315 comments

Flint: A Visualization Language for the AI Era

https://microsoft.github.io/flint-chart/
119•vinhnx•7h ago•37 comments

Solid Queue 1.6.0 now supports fiber workers

https://github.com/rails/solid_queue/releases/tag/v1.6.0
12•earcar•2h ago•0 comments

qm – Multiplayer agent harness for work

https://github.com/yc-software/qm
572•tosh•15h ago•117 comments

How to Exist

https://www.raptitude.com/2026/07/how-to-exist/
196•walterbell•9h ago•111 comments

The development pipeline is a production system

https://sundry.jerryorr.com/2026/07/31/development-pipeline-is-a-production-system
82•firefoxd•6h ago•33 comments

Software for One

https://www.ajwaxman.com/writing/software-for-one
110•awaxman11•2d ago•94 comments

G'mic 4.0: Squaring the Pixel, Easier

https://gmic.eu/gmic40/
20•dtschump•2d ago•2 comments

AWS Secrets Manager Terraform: Least-Privilege Access

https://blog.victorsilva.com.uy/aws-secrets-manager-terraform-least-privilege/
5•meysamazad•3d ago•0 comments

Attention Decode on AMD MI450 GPUs: A Gluon Kernel Optimization Guide

https://rocm.blogs.amd.com/software-tools-optimization/gluon-attention-decode-mi450/README.html
36•matt_d•4d ago•0 comments

A tiny holdout building in the middle of Macy’s is back in view

https://ephemeralnewyork.wordpress.com/2026/07/27/hidden-by-billboards-for-over-100-years-the-tin...
25•donohoe•3d ago•9 comments

Google fixed more Chrome bugs in June than over the past two years, thanks to AI

https://blog.google/security/chrome-stronger-with-every-update/
518•Garbage•1d ago•531 comments

Ten Ways NAS Is Getting Enshitified

https://nascompares.com/2026/07/31/the-10-ways-nas-is-getting-enshitified/
87•giuliomagnifico•4h ago•80 comments

The Absurdity of Albert Camus

https://www.historytoday.com/archive/portrait-author-historian/absurdity-albert-camus
121•apollinaire•1d ago•54 comments

Ten advances in mathematics and theoretical computer science

https://openai.com/index/ten-advances-in-mathematics/
88•milkshakes•2h ago•76 comments

How to Do Great Work

https://paulgraham.com/greatwork.html
4•tosh•1h ago•1 comments

Run Kimi K3 using 29 GB of RAM at 0.50 tok/s

https://github.com/sqliteai/waste
248•marcobambini•19h ago•104 comments

Getting 25 Gbps Thunderbolt Ethernet on My Mac Studio

https://www.jeffgeerling.com/blog/2026/getting-25g-ethernet-mac-thunderbolt/
191•speckx•17h ago•95 comments

June in Servo: real world compat, media queries, SharedWorker, and more

https://servo.org/blog/2026/07/31/june-in-servo/
149•iamnothere•15h ago•49 comments

Progressive Web Components

https://arielsalminen.com/2026/progressive-web-components/
152•hosteur•23h ago•32 comments

Big Food vs. the People

https://www.lighthousereports.com/investigation/big-food-vs-the-people/
229•jruohonen•17h ago•145 comments

Increasing the lifespan of a bulb makes it worse in every other way

https://maurycyz.com/misc/tungsten/
87•tonyg•22h ago•85 comments

Golang proposal: container/: generic collection types

https://github.com/golang/go/issues/80590
154•jabits•15h ago•126 comments

Long Range Wi-Fi – Pushing 2.4 GHz Wi-Fi to the limits (2019)

https://www.phidgets.com/?view=articles&article=LongRangeWifi
54•rzk•3d ago•32 comments

A week in Matrix

https://piegames.de/dumps/a-week-in-matrix/
72•Kesseki•8h ago•40 comments

Loops (YC W22) Is Hiring a Product Educator

https://www.ycombinator.com/companies/loops/jobs/zqUnwqB-product-educator-technical-content-creator
1•chrisfrantz•12h ago

The most official water costs $120k a gallon

https://signoregalilei.com/2026/07/26/the-most-official-water-costs-120000-a-gallon/
187•surprisetalk•18h ago•148 comments

Demystifying DRAM Read Disturbance: RowHammer and RowPress Phenomena

https://arxiv.org/abs/2607.28233
51•Jimmc414•13h ago•28 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?