frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Netbird a German Tailscale alternative (P2P WireGuard-based overlay network)

https://netbird.io/
187•l1am0•2h ago•46 comments

What I learned building an opinionated and minimal coding agent

https://mariozechner.at/posts/2025-11-30-pi-coding-agent/
62•SatvikBeri•2h ago•21 comments

The Book of PF, 4th edition

https://nostarch.com/book-of-pf-4th-edition
83•0x54MUR41•4h ago•17 comments

Mobile carriers can get your GPS location

https://an.dywa.ng/carrier-gnss.html
699•cbeuw•18h ago•417 comments

How to Scale a System from 0 to 10M+ Users

https://blog.algomaster.io/p/scaling-a-system-from-0-to-10-million-users
3•olayiwoladekoya•25m ago•1 comments

Reliable 25 Gigabit Ethernet via Thunderbolt

https://kohlschuetter.github.io/blog/posts/2026/01/27/tb25/
30•kohlschuetter•4d ago•14 comments

The history of C# and TypeScript with Anders Hejlsberg | GitHub

https://www.youtube.com/watch?v=uMqx8NNT4xY
82•doppp•4d ago•47 comments

VisualJJ – Jujutsu in Visual Studio Code

https://www.visualjj.com/
19•demail•3d ago•0 comments

In praise of –dry-run

https://henrikwarne.com/2026/01/31/in-praise-of-dry-run/
187•ingve•15h ago•102 comments

pg_tracing: Distributed Tracing for PostgreSQL

https://github.com/DataDog/pg_tracing
75•tanelpoder•3d ago•11 comments

List animals until failure

https://rose.systems/animalist/
172•l1n•10h ago•97 comments

Cells use 'bioelectricity' to coordinate and make group decisions

https://www.quantamagazine.org/cells-use-bioelectricity-to-coordinate-and-make-group-decisions-20...
75•marojejian•12h ago•28 comments

Generative AI and Wikipedia editing: What we learned in 2025

https://wikiedu.org/blog/2026/01/29/generative-ai-and-wikipedia-editing-what-we-learned-in-2025/
166•ColinWright•14h ago•65 comments

Coffee as a staining agent substitute in electron microscopy

https://phys.org/news/2026-01-coffee-agent-substitute-electron-microscopy.html
20•PaulHoule•2d ago•9 comments

Opentrees.org (2024)

https://opentrees.org/#pos=1/-37.8/145
92•surprisetalk•4d ago•9 comments

Drawings of the elements of CMS detector, in the style of Leonardo da Vinci

https://cds.cern.ch/record/1157741/
34•nill0•3d ago•6 comments

Outsourcing thinking

https://erikjohannes.no/posts/20260130-outsourcing-thinking/index.html
163•todsacerdoti•14h ago•150 comments

Sometimes Your Job Is to Stay the Hell Out of the Way

https://randsinrepose.com/archives/sometimes-your-job-is-to-stay-the-hell-out-of-the-way/
76•ohjeez•4d ago•63 comments

Scientist who helped eradicate smallpox dies at age 89

https://www.scientificamerican.com/article/smallpox-eradication-champion-william-foege-dies-at-89/
237•CrossVR•4d ago•65 comments

Show HN: Moltbook – A social network for moltbots (clawdbots) to hang out

https://www.moltbook.com/
227•schlichtm•3d ago•834 comments

EV-1 for Lease (1996)

https://www.loe.org/shows/shows.html?programID=96-P13-00047#feature4
38•1970-01-01•2d ago•9 comments

Nvidia's 10-year effort to make the Shield TV the most updated Android device

https://arstechnica.com/gadgets/2026/01/inside-nvidias-10-year-effort-to-make-the-shield-tv-the-m...
170•qmr•20h ago•143 comments

Sparse File LRU Cache

http://ternarysearch.blogspot.com/2026/01/sparse-file-lru-cache.html
34•paladin314159•11h ago•6 comments

Finland looks to introduce Australia-style ban on social media

https://yle.fi/a/74-20207494
641•Teever•18h ago•456 comments

Nintendo DS code editor and scriptable game engine

https://crl.io/ds-game-engine/
140•Antibabelic•17h ago•34 comments

Apple Platform Security (Jan 2026) [pdf]

https://help.apple.com/pdf/security/en_US/apple-platform-security-guide.pdf
185•pieterr•19h ago•129 comments

Data Processing Benchmark Featuring Rust, Go, Swift, Zig, Julia etc.

https://github.com/zupat/related_post_gen
107•behnamoh•15h ago•59 comments

Show HN: Minimal – Open-Source Community driven Hardened Container Images

https://github.com/rtvkiz/minimal
94•ritvikarya98•16h ago•27 comments

Nonograms: a practical guide with interactive examples

https://lab174.com/blog/202601-nonograms/
44•merelysounds•4d ago•16 comments

CPython Internals Explained

https://github.com/zpoint/CPython-Internals
204•yufiz•4d ago•49 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

tomhow•8mo ago
Comments moved thither. Thanks!
pabs3•8mo ago
They are two different articles, I don't think that was correct.
tomhow•8mo 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•8mo ago
Thanks for the response, guess that makes sense.
pabs3•8mo 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?