frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Internet Archive Switzerland

https://internetarchive.ch/
86•hggh•1h ago•13 comments

Forking the Web

https://dillo-browser.org/lab/web-fork/
37•wrxd•2h ago•40 comments

Google broke reCAPTCHA for de-googled Android users

https://reclaimthenet.org/google-broke-recaptcha-for-de-googled-android-users
1173•anonymousiam•18h ago•420 comments

A recent experience with ChatGPT 5.5 Pro

https://gowers.wordpress.com/2026/05/08/a-recent-experience-with-chatgpt-5-5-pro/
423•_alternator_•10h ago•268 comments

Using Claude Code: The unreasonable effectiveness of HTML

https://twitter.com/trq212/status/2052809885763747935
227•pretext•8h ago•133 comments

How LEDs are made (2014)

https://learn.sparkfun.com/tutorials/how-leds-are-made/all
12•smig0•2d ago•0 comments

OpenAI’s WebRTC problem

https://moq.dev/blog/webrtc-is-the-problem/
364•atgctg•1d ago•92 comments

Making Julia as Fast as C++ (2019)

https://flow.byu.edu/posts/julia-c++
30•d_tr•2d ago•15 comments

Mythical Man Month

https://martinfowler.com/bliki/MythicalManMonth.html
209•ingve•2d ago•139 comments

America's carpet capital: an empire and its toxic legacy

https://apnews.com/projects/pfas-forever-stained/
58•rawgabbit•2d ago•31 comments

Killswitch: Per-function short-circuit mitigation primitive

https://lwn.net/ml/all/20260507070547.2268452-1-sashal@kernel.org/
23•signa11•4h ago•5 comments

LLMs Corrupt Your Documents When You Delegate

https://arxiv.org/abs/2604.15597
31•rbanffy•4h ago•6 comments

David Attenborough's 100th Birthday

https://www.bbc.com/news/articles/cp3pww9g0p5o
711•defrost•1d ago•141 comments

Reviving the IBM Selectric Composer Fonts (2023)

https://www.kutilek.de/selectric/
19•tangus•2d ago•0 comments

What causes lightning? The answer keeps getting more interesting

https://www.quantamagazine.org/what-causes-lightning-the-answer-keeps-getting-more-interesting-20...
97•Tomte•2d ago•20 comments

Wi is Fi: Understanding Wi-Fi 4/5/6/6E/7/8 (802.11 n/AC/ax/be/bn)

https://www.wiisfi.com/
283•homebrewer•2d ago•71 comments

AI is breaking two vulnerability cultures

https://www.jefftk.com/p/ai-is-breaking-two-vulnerability-cultures
358•speckx•19h ago•142 comments

AWS North Virginia data center outage – resolved

https://www.cnbc.com/2026/05/08/aws-outage-data-center-fanduel-coinbase.html
234•christhecaribou•1d ago•162 comments

Cartoon Network Flash Games

https://www.webdesignmuseum.org/flash-game-exhibitions/cartoon-network-flash-games
362•willmeyers•21h ago•110 comments

The React2Shell Story

https://lachlan.nz/blog/the-react2shell-story/
166•mufeedvh•20h ago•17 comments

An Introduction to Meshtastic

https://meshtastic.org/docs/introduction/
467•ColinWright•1d ago•162 comments

Teaching Claude Why

https://www.anthropic.com/research/teaching-claude-why
197•pretext•19h ago•91 comments

You gave me a u32. I gave you root. (io_uring ZCRX freelist LPE)

https://ze3tar.github.io/post-zcrx.html
194•MrBruh•17h ago•112 comments

Can LLMs model real-world systems in TLA+?

https://www.sigops.org/2026/can-llms-model-real-world-systems-in-tla/
98•mad•21h ago•26 comments

Serving a website on a Raspberry Pi Zero running in RAM

https://btxx.org/posts/memory/
229•xngbuilds•22h ago•92 comments

Roadside Attraction

https://theoffingmag.com/essay/roadside-attraction/
30•aways•17h ago•3 comments

Light without electricity? Glowing algae could make it possible

https://www.colorado.edu/today/2026/05/06/light-without-electricity-glowing-algae-could-make-it-p...
87•geox•2d ago•25 comments

US Government releases first batch of UAP documents and videos

https://www.war.gov/UFO/
310•david-gpu•1d ago•457 comments

The soul of maintaining a new machine

https://books.worksinprogress.co/book/maintenance-of-everything/communities-of-practice/the-soul-...
70•akkartik•3d ago•5 comments

All means are fair except solving the problem

https://yosefk.com/blog/all-means-are-fair-except-solving-the-problem.html
70•akkartik•2d ago•48 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?