frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Async Rust never left the MVP state

https://tweedegolf.nl/en/blog/237/async-rust-never-left-the-mvp-state
239•pjmlp•5h ago•121 comments

Should I Run Plain Docker Compose in Production in 2026?

https://distr.sh/blog/running-docker-in-production/
107•pmig•4d ago•77 comments

Bun is being ported from Zig to Rust

https://github.com/oven-sh/bun/commit/46d3bc29f270fa881dd5730ef1549e88407701a5
581•SergeAx•11h ago•409 comments

When everyone has AI and the company still learns nothing

https://www.robert-glaser.de/when-everyone-has-ai-and-the-company-still-learns-nothing/
69•youngbrioche•3h ago•40 comments

Empty Screenings – Finds AMC movie screenings with few or no tickets sold

https://walzr.com/empty-screenings
186•MrBuddyCasino•7h ago•153 comments

Lessons for Agentic Coding: What should we do when code is cheap?

https://www.dbreunig.com/2026/05/04/10-lessons-for-agentic-coding.html
108•ingve•5h ago•84 comments

Hand Drawn QR Codes (2025)

https://sethmlarson.dev/hand-drawn-qr-codes
142•jollyjerry•8h ago•25 comments

Google Chrome silently installs a 4 GB AI model on your device without consent

https://www.thatprivacyguy.com/blog/chrome-silent-nano-install/
393•john-doe•4h ago•396 comments

sRGB profile comparison

https://ninedegreesbelow.com/photography/srgb-profile-comparison.html
6•Retr0id•2d ago•0 comments

How OpenAI delivers low-latency voice AI at scale

https://openai.com/index/delivering-low-latency-voice-ai-at-scale/
421•Sean-Der•16h ago•133 comments

Farewell to a Giant of Botany

https://nautil.us/farewell-to-a-giant-of-botany-1280409
48•Brajeshwar•2d ago•1 comments

CVE-2026-31431: Copy Fail vs. rootless containers

https://www.dragonsreach.it/2026/05/04/cve-2026-31431-copy-fail-rootless-containers/
125•averi•8h ago•60 comments

Train Your Own LLM from Scratch

https://github.com/angelos-p/llm-from-scratch
296•kristianpaul•8h ago•32 comments

Mouse Pointer as a Mere Mortal

https://unsung.aresluna.org/mouse-pointer-as-a-mere-mortal/
43•zdw•2d ago•13 comments

Agent Skills

https://addyosmani.com/blog/agent-skills/
285•BOOSTERHIDROGEN•14h ago•139 comments

Today I've made the difficult decision to reduce the size of Coinbase by ~14%

https://twitter.com/brian_armstrong/status/2051616759145185723
20•adrianmsmith•20m ago•16 comments

The Frog for Whom the Bell Tolls

https://sethmlarson.dev/the-frog-for-whom-the-bell-tolls
22•anujbans•5h ago•7 comments

How Many Children Learned Mathematics from Kiselev's Textbooks?

https://valeman.medium.com/how-many-children-learned-mathematics-from-kiselevs-textbooks-ff4efcea...
36•ibobev•22h ago•5 comments

Why I Created phpc.tv

https://afilina.com/why-phpc-tv
30•luu•1d ago•5 comments

Does Employment Slow Cognitive Decline? Evidence from Labor Market Shocks

https://www.nber.org/papers/w35117
309•littlexsparkee•20h ago•295 comments

Setting up server monitoring for a Rails app on Hatchbox

https://blog.appsignal.com/2026/04/30/setting-up-server-monitoring-for-a-rails-app-on-hatchbox.html
8•andreigaspar•1d ago•1 comments

Securing a DoD contractor: Finding a multi-tenant authorization vulnerability

https://www.strix.ai/blog/how-strix-found-zero-auth-vulnerability-dod-backed-startup
202•bearsyankees•18h ago•87 comments

2-D Mathematical Curves

https://www.2dcurves.com/
46•the-mitr•8h ago•3 comments

Redis array: short story of a long development process

https://antirez.com/news/164
291•antirez•22h ago•105 comments

Biscuit

https://github.com/yattsu/biscuit
65•unixfg•9h ago•4 comments

Formatting a 25M-line codebase overnight

https://stripe.dev/blog/formatting-an-entire-25-million-line-codebase-overnight-the-rubyfmt-story
183•r00k•16h ago•91 comments

When networking doesn't work

https://www.os2museum.com/wp/when-networking-doesnt-work/
74•kencausey•15h ago•11 comments

pgxbackup: Continuity Support for pgBackRest

https://thebuild.com/blog/2026/05/01/pgxbackup-continuity-support-for-pgbackrest/
61•Wingy•2d ago•10 comments

Talking to strangers at the gym

https://thienantran.com/talking-to-35-strangers-at-the-gym/
1393•thitran•1d ago•665 comments

Kids bypass age verification with fake moustaches

https://www.theregister.com/2026/05/04/uk_online_safety_act_age_checks_subvert/
139•dreadsword•7h ago•105 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•11mo ago

Comments

balloob•11mo 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•11mo ago
Discussion for the other article in the series:

https://news.ycombinator.com/item?id=44011381

tomhow•11mo ago
Comments moved thither. Thanks!
pabs3•11mo ago
They are two different articles, I don't think that was correct.
tomhow•11mo 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•11mo ago
Thanks for the response, guess that makes sense.
pabs3•11mo 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?