frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

C++: The Documentary

https://herbsutter.com/2026/06/04/c-the-documentary-released-today/
148•ingve•5h ago•75 comments

Changing How We Develop Ladybird

https://ladybird.org/posts/changing-how-we-develop-ladybird/
160•EdwinHoksberg•2h ago•89 comments

Entanglement Builds Space-Time. Now "Magic" Gives It Gravity

https://www.quantamagazine.org/entanglement-builds-space-time-now-magic-gives-it-gravity-20260603/
10•rbanffy•1h ago•3 comments

Meta enables ADB on deprecated Portal devices [video]

https://fb.watch/HxPu0fSyeH/
224•jenders•8h ago•81 comments

Fine-tuning an LLM to write docs like it's 1995

https://passo.uno/fine-tuning-docs-llm/
59•taubek•3h ago•17 comments

The IsUpMap lets you check the status of over 100 major sites at once

https://isupmap.com/
52•mikelgan•4h ago•24 comments

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

https://github.com/anthropics/defending-code-reference-harness
416•binyu•13h ago•119 comments

databow: a Rust CLI to query any database with an ADBC driver

https://columnar.tech/blog/introducing-databow//
13•hckshr•2d ago•0 comments

Do transformers need three projections? Systematic study of QKV variants

https://arxiv.org/abs/2606.04032
167•Anon84•10h ago•34 comments

Tracing a powerful GNSS interference source over Europe

https://arxiv.org/abs/2606.03673
14•mimorigasaka•1h ago•3 comments

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

https://github.com/alibaba/open-code-review
179•geoffbp•9h ago•48 comments

Leap in DNA synthesis slashes time to build new genetic sequences

https://spectrum.ieee.org/faster-dna-synthesis-sidewinder
24•natalcleft•15h ago•7 comments

I'm skeptical about efforts to revolutionize schooling

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

ESP32 Bit Pirate, a Hardware Hacking Tool with WebCLI That Speaks Every Protocol

https://github.com/geo-tp/ESP32-Bit-Pirate
19•geotp•2h ago•13 comments

Watching a Z80 from an RP2350

https://emalliab.wordpress.com/2026/05/26/watching-a-z80-from-an-rp2350/
20•ibobev•2d ago•1 comments

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

https://tiki.li/blog/blqsort
174•birdculture•2d ago•52 comments

WiFi Time

https://mitxela.com/projects/wifi_time
71•surprisetalk•2d ago•4 comments

Delacroix's Entry of the Crusaders into Constantinople Restored

https://www.louvre.fr/en/explore/life-at-the-museum/delacroix-s-entry-of-the-crusaders-into-const...
31•rawgabbit•6h ago•11 comments

Go Experiments Explained

https://www.alexedwards.net/blog/go-experiments-explained
34•ingve•4d ago•11 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...
556•tristanj•10h ago•268 comments

Magenta RealTime 2: Open and Local Live Music Models

https://magenta.withgoogle.com/magenta-realtime-2
35•selvan•5h ago•6 comments

Linear Cosine Palettes(2025)

https://blog.djnavarro.net/posts/2025-09-14_cosine-palettes/
21•num42•6h ago•0 comments

There's no escaping it: an exploration of ANSI codes

https://blog.safia.rocks/2025/12/22/ansi-codes/
5•ankitg12•2h ago•3 comments

Samurai City

https://worksinprogress.co/issue/samurai-city/
166•zdw•3d ago•33 comments

Queen bees emerge from special wax chambers

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

Retro-Tech Parenting

https://havenweb.org/2026/05/28/retro-tech.html
298•mawise•17h ago•205 comments

VoidZero Is Joining Cloudflare

https://blog.cloudflare.com/voidzero-joins-cloudflare/
637•coloneltcb•20h ago•277 comments

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

https://github.com/huawei-csl/KVarN
133•theanonymousone•18h ago•13 comments

Azure Linux 4.0 is Microsoft's first general-purpose Linux

https://www.boxofcables.dev/azure-linux-4-0-is-microsofts-first-general-purpose-linux/
110•haydenbarnes•6h ago•91 comments

WSL 2 is getting faster Windows file system access

https://www.boxofcables.dev/wsl2-per-device-swiotlb-pools-for-virtiofs-and-virtioproxy/
143•haydenbarnes•14h ago•105 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?