frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Elevators

https://john.fun/elevators
887•Jrh0203•10h ago•222 comments

qm – Multiplayer agent harness for work

https://github.com/yc-software/qm
467•tosh•8h ago•100 comments

Twenty-five years ago it was cryptography, today it's model weights

https://weeraman.com/because-we-can/
170•aweeraman•3d ago•67 comments

The Absurdity of Albert Camus

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

Progressive Web Components

https://arielsalminen.com/2026/progressive-web-components/
91•hosteur•16h ago•14 comments

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

https://servo.org/blog/2026/07/31/june-in-servo/
105•iamnothere•7h ago•32 comments

How to Exist

https://www.raptitude.com/2026/07/how-to-exist/
12•walterbell•1h ago•1 comments

Big Food vs. the People

https://www.lighthousereports.com/investigation/big-food-vs-the-people/
193•jruohonen•10h ago•132 comments

Getting 25 Gbps Thunderbolt Ethernet on My Mac Studio

https://www.jeffgeerling.com/blog/2026/getting-25g-ethernet-mac-thunderbolt/
142•speckx•9h ago•84 comments

Tailscale didn't stop the Hugging Face intrusion

https://tailscale.com/blog/hugging-face-intrusion
464•bluehatbrit•7h ago•175 comments

Demystifying DRAM Read Disturbance: RowHammer and RowPress Phenomena

https://arxiv.org/abs/2607.28233
35•Jimmc414•5h ago•17 comments

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

https://github.com/sqliteai/waste
159•marcobambini•11h ago•62 comments

Let's make the worst Htmx

https://zserge.com/posts/worst-htmx-ever/
67•RebelPotato•20h ago•20 comments

Golang proposal: container/: generic collection types

https://github.com/golang/go/issues/80590
124•jabits•7h ago•77 comments

How JPEG works: Interactively explore JPEG's lossy compression methods

https://cgjennings.ca/articles/jpeg-compression/
112•at1as•4d ago•13 comments

Loops (YC W22) Is Hiring a Product Educator

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

The most official water costs $120k a gallon

https://signoregalilei.com/2026/07/26/the-most-official-water-costs-120000-a-gallon/
139•surprisetalk•11h ago•123 comments

A past and future of trade secrets

https://www.cabinetmagazine.org/issues/70/kofen.php
15•Hooke•1d ago•3 comments

The First Transatlantic Telegraph Cable Was a Bold, Beautiful Failure

https://spectrum.ieee.org/the-first-transatlantic-telegraph-cable-was-a-bold-beautiful-failure
19•sparsesignal•2d ago•3 comments

Show HN: I worked on a new browser for 2 years, today it passed Acid 3

https://code.intellios.ai/cwbrowser/
34•coolwulf•4h ago•11 comments

Termixer (TUI DJ Mixer)

https://github.com/l00sed/termixer
54•l00sed•7h ago•35 comments

Authorize, don't authenticate

https://blog.marcua.net/2026/07/31/authorize-dont-authenticate.html
56•marcua•11h ago•14 comments

Predictive Speculative KV Replication for Bursty LLM Inference

https://jwlabs.vercel.app/post/biting-the-bullet
29•shreybirmiwal•6h ago•2 comments

Dubious research tied to Red Bull has shaped energy drink policy

https://www.theexamination.org/articles/red-bull-funded-research-energy-drinks-alcohol
118•Jimmc414•10h ago•181 comments

Is AI reasoning right for the wrong reasons?

https://www.quantamagazine.org/is-ai-reasoning-right-for-the-wrong-reasons-20260731/
121•retupmoc01•10h ago•153 comments

Algorithms on billion-scale graph using 10GB RAM: I love DataFusion

https://semyonsinchenko.github.io/ssinchenko/post/datafusion-graphs-cc-2/
103•speckx•10h ago•32 comments

Using the railway network as a flatbed scanner [video]

https://media.ccc.de/v/emf2026-74-1-using-the-railway-network-as-a-flatbed-scanner
52•Jimmc414•7h ago•25 comments

Everyone is building LLM routers, we deprecated ours

https://manifest.build/blog/why-we-deprecated-our-llm-router/
95•brunaxLorax•8h ago•51 comments

Severance

https://lcamtuf.substack.com/p/severance
209•surprisetalk•8h ago•69 comments

How far can you push the range of Wi-Fi connectivity in an ideal environment?

https://www.phidgets.com/?view=articles&article=LongRangeWifi
6•rzk•3d ago•3 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?