frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Why do AI company logos look like buttholes?

https://velvetshark.com/ai-company-logos-that-look-like-buttholes
244•miniBill•1h ago•73 comments

LG monitors silently install software through Windows Update without consent

https://videocardz.com/newz/lg-monitors-silently-install-software-through-windows-update-without-...
207•baranul•2h ago•105 comments

Regressive JPEGs

https://maurycyz.com/projects/bad_jpeg/
444•vitaut•9h ago•45 comments

Fable 5 vs. GPT-5.6 Sol on an NP-Hard Problem: Does /goal help?

https://charlesazam.com/blog/fable-5-gpt-5-6-sol-goal/
17•couAUIA•1h ago•7 comments

AWS: Inaccurate Estimated Billing Data – $1.7 billion

1221•nprateem•1d ago•716 comments

The Computer at the Bottom of a Canal

https://negroniventurestudios.com/2026/07/18/the-computer-at-the-bottom-of-a-canal/
36•Kudos•4h ago•6 comments

Qubes OS Security in the Public Record

https://arxiv.org/abs/2607.14587
32•sciences44•3h ago•3 comments

Thanks HN for 15 years of support and helping me find my life's work

662•nicholasjbs•19h ago•76 comments

Reviving a 15-year-old netbook with Arch Linux

https://parksb.github.io/en/article/41.html
140•parksb•3d ago•90 comments

First atmosphere found on Earth-like planet in habitable zone of distant star

https://www.bbc.com/news/articles/cy4kdd1e0ejo
473•neversaydie•22h ago•279 comments

What AI did to stackoverflow in a graph

https://data.stackexchange.com/stackoverflow/query/1953768#graph
66•secretslol•1h ago•78 comments

The Zilog Z80 has turned 50

https://goliath32.com/blog/z80.html
242•st_goliath•16h ago•95 comments

In-toto: A framework to secure the integrity of software supply chains

https://in-toto.io/
47•Erenay09•1d ago•5 comments

Waldi: A quiet place to write, and to be read

https://github.com/waaldev/waldi
23•waaldev•6d ago•10 comments

Show HN: IKEA Complexity Index

https://ikea.greg.technology/
81•gregsadetsky•8h ago•41 comments

TP-Link Kasa cameras leaked home GPS via unauthenticated UDP for 6 years

https://github.com/BadChemical/IoT-Vulnerability-Research-Public/blob/main/TP-Link_Kasa_EC71/Kasa...
154•BadChemical•14h ago•53 comments

Learning a few things about running SQLite

https://jvns.ca/blog/2026/07/17/learning-about-running-sqlite/
273•surprisetalk•18h ago•73 comments

Kimi K3, and what we can still learn from the pelican benchmark

https://simonwillison.net/2026/Jul/16/kimi-k3/
360•droidjj•22h ago•189 comments

Porting nanochat to a TPU: what carries over from PyTorch, and what breaks

https://github.com/tucan9389/nanochat-jax/discussions/1
50•tucan9389•3d ago•9 comments

I started a “dirt notebook”

https://pinewind.bearblog.dev/i-started-a-dirt-notebook/
80•herbertl•11h ago•69 comments

Responsive Design Calculator

https://www.redblobgames.com/blog/2026-07-11-responsive-design-calculator/
4•ingve•4d ago•0 comments

Steam Machine: Between 12k and 15k Units Sold per week

https://boilingsteam.com/steam-machine-between-10k-and-15k-sold-per-week/
20•ekianjo•1h ago•3 comments

Revisiting Yliluoma's ordered dither algorithm

https://30fps.net/pages/revisiting-yliluoma-2/
12•ibobev•4d ago•1 comments

Stenchill: 3D Printable Solder Paste Stencil Generator

https://www.stenchill.com/en/
63•radeeyate•11h ago•18 comments

Static search trees: 40x faster than binary search (2024)

https://curiouscoding.nl/posts/static-search-tree/
148•lalitmaganti•16h ago•9 comments

Vāgdhenu: A Sanskrit Chanting TTS System

https://prathosh.in/vagdhenu/
191•subinalex•4d ago•47 comments

Battery packs: Let's talk about crates, baby

https://smallcultfollowing.com/babysteps/blog/2026/07/15/battery-packs/
34•MeetingsBrowser•1d ago•17 comments

DrDroid (YC W23) Is Hiring

https://www.ycombinator.com/companies/drdroid/jobs/w45QcNV-product-engineer-assignment-mandatory
1•TheBengaluruGuy•11h ago

An Update on Igalia's Layer Based SVG Engine in WebKit (Reducing Layer Overhead)

https://blogs.igalia.com/nzimmermann/posts/2026-07-14-lbse-conditional-layers/
58•bkardell•3d ago•4 comments

Painting the sides of railroad rails white to reduce derailment

https://www.up.com/news/safety/Tracking-Rail-Heat-260608
115•zdw•16h ago•68 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?