frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Building from zero after addiction, prison, and a felony

https://gavinray97.github.io/blog/building-from-zero-after-addiction-prison-felony
156•gavinray•2h ago•45 comments

How's Linear so fast? A technical breakdown

https://performance.dev/how-is-linear-so-fast-a-technical-breakdown
158•howToTestFE•2h ago•89 comments

The architecture of the internet creates risks for democracy

https://www.science.org/doi/10.1126/science.aei2409
31•Anon84•56m ago•23 comments

Making peace with your unlived dreams (2023)

https://nik.art/making-peace-with-your-unlived-dreams/
78•herbertl•3h ago•27 comments

Silurus/ooxml: Pixel-faithful Office documents, rendered in the browser

https://github.com/yukiyokotani/office-open-xml-viewer
78•maxloh•4h ago•27 comments

Powering up a module from the IBM 604: an electronic calculator from 1948

https://www.righto.com/2026/06/ibm-604-thyraton-tube-module.html
55•elpocko•4h ago•17 comments

What is the purpose of the lost+found folder in Linux and Unix? (2014)

https://unix.stackexchange.com/questions/18154/what-is-the-purpose-of-the-lostfound-folder-in-lin...
88•tosh•2d ago•37 comments

My automated doubt development process

https://www.alexself.dev/blog/automated-doubt
25•aself101•3h ago•11 comments

Cloning a Sennheiser BA2015 battery pack

https://blog.brixit.nl/cloning-a-sennheiser-ba2015-accu-pack/
88•zdw•1d ago•14 comments

Flock license plate reader wrongly linked a San Diego man to a violent crime

https://timesofsandiego.com/crime/2026/06/07/a-flock-license-plate-reader-linked-a-san-diego-man-...
22•loteck•32m ago•3 comments

If LLMs Have Human-Like Attributes, Then So Does Age of Empires II

https://arxiv.org/abs/2605.31514
18•ketchup32613•2h ago•9 comments

Do we fear the serializable isolation level more than we fear subtle bugs?

https://blog.ydb.tech/do-we-fear-the-serializable-isolation-level-more-than-we-fear-subtle-bugs-5...
10•b-man•4d ago•1 comments

The 29th International Obfuscated C Code Contest (IOCCC) 2025 Winners

https://www.ioccc.org/2025/
345•matt_d•15h ago•82 comments

Leiden Declaration on Artificial Intelligence and Mathematics

https://www.lms.ac.uk/news/leiden-declaration-on-ai-and-mathematics
41•_____k•2h ago•1 comments

Proliferate (YC S25) is hiring to building open source Codex

https://www.ycombinator.com/companies/proliferate/jobs/L3copvK-founding-engineer
1•pablo24602•4h ago

Show HN: Lathe – Use LLMs to learn a new domain, not skip past it

https://github.com/devenjarvis/lathe
195•devenjarvis•10h ago•40 comments

Backrest – a web UI and orchestrator for restic backup

https://github.com/garethgeorge/backrest
58•flexagoon•5d ago•5 comments

The complete IPv4 address space, mapped

https://worldip.io/
18•theanonymousone•3h ago•6 comments

A visual introduction to kernel functions

https://kelvinpaschal.com/blog/kernel-functions/
16•Kelvinidan•2d ago•0 comments

Anthropic, please ship an official Claude Desktop for Linux

https://github.com/anthropics/claude-code/issues/65697
388•predkambrij•8h ago•221 comments

Podman 6: machine usability improvements (2025)

https://blog.podman.io/2025/10/podman-6-machine-usability-improvements/
80•daesorin•7h ago•5 comments

You'll never guess who made the first wireless telephone

https://signoregalilei.com/2026/05/31/youll-never-guess-who-made-the-first-wireless-telephone/
47•surprisetalk•3d ago•9 comments

Win16 Memory Management

http://www.os2museum.com/wp/win16-memory-management/
124•supermatou•2d ago•61 comments

Public Domain Image Archive

https://pdimagearchive.org/
229•davidbarker•21h ago•32 comments

sqlite: A CGo-free port of SQLite/SQLite3

https://gitlab.com/cznic/sqlite
32•tosh•7h ago•22 comments

The Secret Life of Circuits with lcamtuf / Michał Zalewski (Audio Interview)

https://theamphour.com/725-the-secret-life-of-circuits-with-lcamtuf-michal-zalewski/
57•ChrisGammell•3d ago•5 comments

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

https://blog.safia.rocks/2025/12/22/ansi-codes/
24•ankitg12•2d ago•7 comments

Speculative KV coding: losslessly compressing KV cache by up to ~4×

https://fergusfinn.com/blog/kv-entropy-coder/
135•kkm•3d ago•28 comments

The curious case of low-protein diets

https://knowablemagazine.org/content/article/living-world/2026/low-protein-diet-animals-live-longer
33•curmudgeon22•2h ago•12 comments

Show HN: Kyushu – A self-hostable WASM sandbox for JavaScript workers

https://kyushu.dev/
68•le_chuck•13h ago•28 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?