frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Meta enables ADB on deprecated Portal devices [video]

https://fb.watch/HxPu0fSyeH/
102•jenders•2h ago•20 comments

Do transformers need three projections? Systematic study of QKV variants

https://arxiv.org/abs/2606.04032
111•Anon84•4h ago•19 comments

Anthropic's open-source framework for AI-powered vulnerability discovery

https://github.com/anthropics/defending-code-reference-harness
297•binyu•7h ago•96 comments

Open Code Review – An AI-powered code review CLI tool

https://github.com/alibaba/open-code-review
68•geoffbp•3h ago•16 comments

VoidZero Is Joining Cloudflare

https://blog.cloudflare.com/voidzero-joins-cloudflare/
586•coloneltcb•14h ago•259 comments

When AI Builds Itself: Our progress toward recursive self-improvement

https://www.anthropic.com/institute/recursive-self-improvement
362•meetpateltech•10h ago•474 comments

I'm skeptical about efforts to revolutionize schooling

https://www.scotthyoung.com/blog/2026/05/27/revolutionize-schooling/
88•andrewstuart•2d ago•142 comments

Reverse-Engineered Userspace Driver for Asus ZenVision Lid OLED on Linux"

https://github.com/tarpediem/zenvision-linux
31•berlianta•2d ago•3 comments

Branchless Quicksort faster than std:sort and pdqsort with C and C++ API

https://tiki.li/blog/blqsort
106•birdculture•2d ago•18 comments

Ian's Secure Shoelace Knot

https://www.fieggen.com/shoelace/secureknot.htm
525•mooreds•16h ago•199 comments

Queen bees emerge from special wax chambers

https://cen.acs.org/materials/biobased-materials/queen-bees-special-wax/104/web/2026/06
51•gmays•5h ago•6 comments

South Korean Forums Will Need to Scan Every Images with AI Censorship Tools

https://discuss.privacyguides.net/t/south-korean-online-communities-will-need-to-scan-every-image...
21•Cider9986•3h ago•11 comments

Samurai City

https://worksinprogress.co/issue/samurai-city/
117•zdw•2d ago•21 comments

KVarN: Native vLLM backend for KV-cache quantization by Huawei

https://github.com/huawei-csl/KVarN
117•theanonymousone•12h ago•12 comments

SpaceX, Other Mega IPOs Denied Fast Index Entry by S&P

https://www.bloomberg.com/news/articles/2026-06-04/s-p-dow-jones-keeps-megacap-ipo-rules-as-is-af...
151•tristanj•4h ago•60 comments

Retro-Tech Parenting

https://havenweb.org/2026/05/28/retro-tech.html
263•mawise•11h ago•178 comments

Show HN: Mercek – A Desktop IDE for AWS ECS

https://www.mercek.dev/
32•utibeumanah•6h ago•7 comments

Castor: CERN Advanced STORage Manager

https://castor.web.cern.ch/content/home.html
44•naves•7h ago•19 comments

IPv6 zones in URLs are a mistake

https://xeiaso.net/notes/2026/ipv6-zones-go-url/
98•xena•5h ago•75 comments

JLink JTAG Access on the Pinecil

https://danielmangum.com/posts/jlink-jtag-pinecil/
42•hasheddan•2d ago•8 comments

Making Debian or Fedora persistent live images

https://sigwait.org/~alex/blog/2026/05/28/smdBC8.html
65•henry_flower•3d ago•6 comments

Show HN: Uruky (EU-based Kagi alternative) now has Image Search and URL Rewrites

https://uruky.com/?il=en
213•BrunoBernardino•18h ago•195 comments

Latent Agents: A Post-Training Procedure for Internalized Multi-Agent Debate

https://arxiv.org/abs/2604.24881
16•PaulHoule•4h ago•0 comments

I made a kernel 2.2x faster. It made my training loop 3x slower

https://kyrieblunders.bearblog.dev/making-dr-grpo-go-brrr/
6•vishal-padia•2d ago•0 comments

Meta's ships facial recognition on smart glasses

https://www.buchodi.com/meta-glasses-facial-recognition/
248•buchodi•7h ago•209 comments

Zettascale (YC S24) Is Hiring Founding FPGA Engineers

https://www.ycombinator.com/companies/zettascale/jobs/O9S1vqO-founding-engineer-fpga-rtl-asic-arc...
1•el_al•10h ago

Semantic reification: how to generate UB-free code with arbitrary control flow?

https://github.com/connglli/Reify
8•zsu•1d ago•1 comments

WSL 2 is getting faster Windows file system access

https://www.boxofcables.dev/wsl2-per-device-swiotlb-pools-for-virtiofs-and-virtioproxy/
84•haydenbarnes•7h ago•62 comments

External Clock Generation on RTX 50 Series

https://www.xtremesystems.us/post/external-clock-generation-on-rtx-50-series
17•mfro•1d ago•2 comments

Gaussian Point Splatting

https://momentsingraphics.de/Siggraph2026.html
180•ibobev•16h ago•66 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?