frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Deterministic Fully-Static Whole-Binary Translation Without Heuristics

https://arxiv.org/abs/2605.08419
67•matt_d•1h ago•9 comments

Restore full BambuNetwork support for Bambu Lab printers

https://github.com/FULU-Foundation/OrcaSlicer-bambulab
320•Murfalo•8h ago•134 comments

Googlebook

https://googlebook.google/
708•tambourine_man•12h ago•1184 comments

The vi family

https://lpar.ATH0.com/posts/2026/05/the-vi-family/
78•hggh•6d ago•25 comments

Show HN: Needle: We Distilled Gemini Tool Calling into a 26M Model

https://github.com/cactus-compute/needle
377•HenryNdubuaku•12h ago•133 comments

Kraftwerk's radical 1976 track

https://www.bbc.com/culture/article/20260511-kraftwerks-radical-1976-track-radioactivity-became-a...
110•tcp_handshaker•6h ago•45 comments

How to make your text look futuristic (2016)

https://typesetinthefuture.com/2016/02/18/futuristic/
288•_vaporwave_•9h ago•34 comments

My graduation cap runs Rust

https://ericswpark.com/blog/2026/2026-05-12-my-graduation-cap-runs-rust/
125•ericswpark•6h ago•30 comments

CERT is releasing six CVEs for serious security vulnerabilities in dnsmasq

https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2026q2/018471.html
281•chizhik-pyzhik•11h ago•129 comments

Why senior developers fail to communicate their expertise

https://www.nair.sh/guides-and-opinions/communicating-your-expertise/why-senior-developers-fail-t...
485•nilirl•14h ago•209 comments

When "idle" isn't idle: how a Linux kernel optimization became a QUIC bug

https://blog.cloudflare.com/quic-death-spiral-fix/
62•sbulaev•6h ago•2 comments

Traceway: MIT-licensed observability stack you can self-host in ~90s

https://github.com/tracewayapp/traceway
52•sebakubisz•1d ago•3 comments

Referer Reality

https://www.robinsloan.com/lab/referer/
27•tobr•2d ago•6 comments

Rendering the Sky, Sunsets, and Planets

https://blog.maximeheckel.com/posts/on-rendering-the-sky-sunsets-and-planets/
445•ibobev•16h ago•38 comments

Quack: The DuckDB Client-Server Protocol

https://duckdb.org/2026/05/12/quack-remote-protocol
245•aduffy•12h ago•52 comments

Tell NYT, Atlantic, USA Today to keep Wayback Machine

https://www.savethearchive.com/newsleaders/
280•doener•6h ago•79 comments

Scrcpy v4.0

https://github.com/Genymobile/scrcpy/releases/tag/v4.0
104•xnx•9h ago•18 comments

Zero-native – Build native desktop apps with web UI

https://zero-native.dev
21•gedy•4h ago•16 comments

The Future of Obsidian Plugins

https://obsidian.md/blog/future-of-plugins/
342•xz18r•14h ago•135 comments

Reimagining the mouse pointer for the AI era

https://deepmind.google/blog/ai-pointer/
177•devhouse•12h ago•145 comments

Fc, a lossless compressor for floating-point streams

https://github.com/xtellect/fc
45•enduku•2d ago•9 comments

Up in Smoke

https://thebaffler.com/odds-and-ends/the-profession-that-does-not-exist-symposium
5•NaOH•2d ago•0 comments

Lanzaboote – NixOS Secure Boot

https://x86.lol/generic/2022/11/26/lanzaboote.html
71•evilmonkey19•3d ago•6 comments

Show HN: Agentic interface for mainframes and COBOL

https://www.hypercubic.ai/hopper
67•sai18•12h ago•39 comments

Launch HN: Voker (YC S24) – Analytics for AI Agents

https://voker.ai
49•ttpost•14h ago•19 comments

Bambu Lab is abusing the open source social contract

https://www.jeffgeerling.com/blog/2026/bambu-lab-abusing-open-source-social-contract/
1181•rubenbe•15h ago•378 comments

Foucault's Order of Things Explained with Trading Cards [video]

https://www.youtube.com/watch?v=1TbHYjGvS68
27•surprisetalk•1d ago•19 comments

When life gives you lemons, write better error messages

https://wix-ux.com/when-life-gives-you-lemons-write-better-error-messages-46c5223e1a2f
135•luispa•4d ago•50 comments

EFF to 4th Circuit: Electronic Device Searches at the Border Require a Warrant

https://www.eff.org/deeplinks/2026/05/eff-fourth-circuit-electronic-device-searches-border-requir...
173•hn_acker•8h ago•30 comments

We tested super-resolution pre-filter for LPR OCR. It did nothing

https://www.wink.co/documentation/Neural-Super-Resolution-Pre-Filter-LPR-2026
4•xmichael909•1h ago•1 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

tomhow•12mo ago
Comments moved thither. Thanks!
pabs3•12mo 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?