frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

A recent experience with ChatGPT 5.5 Pro

https://gowers.wordpress.com/2026/05/08/a-recent-experience-with-chatgpt-5-5-pro/
164•_alternator_•4h ago•65 comments

Using Claude Code: The unreasonable effectiveness of HTML

https://twitter.com/trq212/status/2052809885763747935
75•pretext•2h ago•29 comments

Google broke reCAPTCHA for de-googled Android users

https://reclaimthenet.org/google-broke-recaptcha-for-de-googled-android-users
884•anonymousiam•12h ago•295 comments

OpenAI's WebRTC problem

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

Mythical Man Month

https://martinfowler.com/bliki/MythicalManMonth.html
111•ingve•1d ago•84 comments

I Will Never Use AI to Code

https://antman-does-software.com/i-will-never-use-ai-to-code-or-write
33•ishanz•46m ago•17 comments

AI is breaking two vulnerability cultures

https://www.jefftk.com/p/ai-is-breaking-two-vulnerability-cultures
310•speckx•13h ago•128 comments

David Attenborough's 100th Birthday

https://www.bbc.com/news/articles/cp3pww9g0p5o
574•defrost•18h ago•111 comments

The React2Shell Story

https://lachlan.nz/blog/the-react2shell-story/
117•mufeedvh•14h ago•5 comments

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

https://www.wiisfi.com/
179•homebrewer•2d ago•50 comments

AWS North Virginia data center outage – recovery to take hours

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

What Causes Lightning? The Answer Keeps Getting More Interesting

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

EU calls VPNs "a loophole that needs closing" in age verification push

https://cyberinsider.com/eu-calls-vpns-a-loophole-that-needs-closing-in-age-verification-push/
46•muse900•1h ago•14 comments

Cartoon Network Flash Games

https://www.webdesignmuseum.org/flash-game-exhibitions/cartoon-network-flash-games
324•willmeyers•14h ago•104 comments

Bitter Lessons from the ISSpresso

https://mceglowski.substack.com/p/bitter-lessons-from-the-isspresso
83•zdw•2d ago•21 comments

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

https://ze3tar.github.io/post-zcrx.html
173•MrBruh•11h ago•96 comments

PortalVR Motion – use any VR content in 2D with 3D tracked Joy-Cons

https://portalvr.io/motion
13•gfodor•2d ago•1 comments

Can LLMs model real-world systems in TLA+?

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

An Introduction to Meshtastic

https://meshtastic.org/docs/introduction/
413•ColinWright•19h ago•155 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...
54•geox•2d ago•17 comments

Teaching Claude Why

https://www.anthropic.com/research/teaching-claude-why
145•pretext•13h ago•73 comments

The Soul of Maintaining a New Machine

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

Serving a website on a Raspberry Pi Zero running in RAM

https://btxx.org/posts/memory/
211•xngbuilds•15h ago•89 comments

All means are fair except solving the problem

https://yosefk.com/blog/all-means-are-fair-except-solving-the-problem.html
49•akkartik•2d ago•43 comments

Mojo 1.0 Beta

https://mojolang.org/
332•sbt567•1d ago•211 comments

Mux (YC W16) Is Hiring

https://www.mux.com/jobs
1•mmcclure•9h ago

Over 97% of the 'Linux' Foundation's Budget Goes Not to Linux

https://techrights.org/n/2026/05/08/Over_97_of_the_Linux_Foundation_s_Budget_Goes_Not_to_Linux.shtml
92•esaym•3h ago•40 comments

When is your birthday? The math behind hash collisions

https://0xkrt26.github.io/math_behind_security/2026/05/08/birthday-problem.html
40•denismenace•10h ago•7 comments

US Government releases first batch of UAP documents and videos

https://www.war.gov/UFO/
273•david-gpu•18h ago•424 comments

Meta Shuts Down End-to-End Encryption for Instagram Messaging

https://www.pcmag.com/news/meta-shuts-down-end-to-end-encryption-for-instagram-dms-messaging
238•tcp_handshaker•9h ago•150 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?