frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Ruff v0.16.0 – Significant new updates – 413 default rules up from 59

https://astral.sh/blog/ruff-v0.16.0
80•vismit2000•2h ago•38 comments

Elevated Errors for Opus 5

https://status.claude.com/incidents/zftg3gqkmv18
28•TimCTRL•2h ago•28 comments

GrapheneOS protections against data extraction from locked devices

https://discuss.grapheneos.org/d/40700-grapheneos-protections-against-data-extraction-from-locked...
110•Cider9986•5h ago•49 comments

A shell colon does nothing. Use it anyway

https://refp.se/articles/your-shell-and-the-magic-colon
227•olexsmir•21h ago•90 comments

An ESP32 based plane radar for my desk

https://blog.ktz.me/esp32-plane-radar/
167•alexktz•8h ago•35 comments

The new rules of context engineering for Claude 5 generation models

https://claude.com/blog/the-new-rules-of-context-engineering-for-claude-5-generation-models
350•mellosouls•14h ago•242 comments

DeepSeek pause fundraise after comments on compute gap to US leaked (transcript) [pdf]

https://github.com/demo-zexuan/liang-wenfeng-investor-meeting-2026-7-22/blob/master/%E6%A2%81%E6%...
171•oliculipolicula•11h ago•120 comments

Show HN: I mapped every US golf course

https://golfcoursebrowser.com/
142•rickmf•9h ago•79 comments

Inflect-Micro-v2: complete voice in 9.36M parameters

https://huggingface.co/owensong/Inflect-Micro-v2
144•nateb2022•10h ago•11 comments

Overloaded Overloading

https://powerfulpython.com/blog/overloaded-overloading/
19•redsymbol•3d ago•5 comments

Stinkpot: SQLite-backed shell history

https://tangled.org/oppi.li/stinkpot
73•nerdypepper•1d ago•22 comments

Cloudflare's new AI traffic options for customers

https://blog.cloudflare.com/content-independence-day-ai-options/
133•alphabetatango•12h ago•108 comments

Alien World Chemistry Found Inside Meteorite That Struck New Jersey Home

https://www.seti.org/news/alien-world-chemistry-found-inside-meteorite/
79•spzx•9h ago•22 comments

Rethinking Legal Education in the AI Era

https://www.law.uchicago.edu/news/ai-strategy-statement
82•jjwiseman•2d ago•47 comments

Running a 28.9M parameter LLM on an $8 microcontroller

https://github.com/slvDev/esp32-ai
203•boveyking•16h ago•47 comments

Some more things about Django I've been enjoying

https://jvns.ca/blog/2026/07/21/more-nice-django-things/
52•surprisetalk•4d ago•24 comments

Git rebase -I is not that scary

https://cachebag.sh/journal/interactive-rebasing/
76•vinhnx•10h ago•89 comments

Systemd Linger

https://etbe.coker.com.au/2026/07/24/systemd-linger/
3•edward•1h ago•0 comments

German Peasants' War

https://en.wikipedia.org/wiki/German_Peasants%27_War
3•constantius•3d ago•2 comments

Pip install Postgres – no Docker/Brew/apt

https://github.com/leontrolski/postgresql-testing
9•leontrolski•2d ago•3 comments

DskDitto: Ultra-fast, parallel duplicate-file detector

https://github.com/jdefrancesco/dskDitto
25•ingve•4d ago•4 comments

What is happening to jobs? Separating AI hype from reality

https://siepr.stanford.edu/publications/policy-brief/what-really-happening-jobs-separating-ai-hyp...
107•pod_krad•12h ago•125 comments

LLM Usage in Debian: Three Proposals

https://www.debian.org/vote/2026/vote_002
167•zdw•15h ago•151 comments

JetZero

https://www.jetzero.aero
210•lisper•8h ago•173 comments

Clinical failure rates over the decades: yikes

https://www.science.org/content/blog-post/clinical-failure-rates-over-decades-yikes
108•EA-3167•12h ago•86 comments

No Stack Overflow, No Autocomplete: What Coding Felt Like in the 80s

https://comuniq.xyz/post?t=1439
16•01-_-•1h ago•11 comments

SIMD for Collision

https://box2d.org/posts/2026/07/simd-for-collision/
102•birdculture•3d ago•27 comments

Systems and Delays

https://martin.janiczek.cz/2026/07/24/systems-and-delays.html
64•vinhnx•10h ago•14 comments

Show HN: I made some transistor animations

https://brandonli.net/semisim/animations
191•stunningllama•1d ago•24 comments

GM Backs Sodium Ion Batteries for U.S. Grid Storage

https://spectrum.ieee.org/sodium-ion-battery-peak-energy
182•rbanffy•13h ago•82 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?