frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Defeating a 40-year-old copy protection dongle

https://dmitrybrant.com/2026/02/01/defeating-a-40-year-old-copy-protection-dongle
201•zdw•3h ago•59 comments

Show HN: NanoClaw – “Clawdbot” in 500 lines of TS with Apple container isolation

https://github.com/gavrielc/nanoclaw
130•jimminyx•2h ago•39 comments

Apple I Advertisement (1976)

http://apple1.chez.com/Apple1project/Gallery/Gallery.htm
171•janandonly•7h ago•109 comments

My thousand dollar iPhone can't do math

https://journal.rafaelcosta.me/my-thousand-dollar-iphone-cant-do-math/
116•rafaelcosta•4h ago•50 comments

Netbird – Open Source Zero Trust Networking

https://netbird.io/
637•l1am0•15h ago•241 comments

Adventure Game Studio: OSS software for creating adventure games

https://www.adventuregamestudio.co.uk/
260•doener•11h ago•49 comments

Treasures found on HS2 route stored in secret warehouse

https://www.bbc.com/news/articles/c93v21q5xdvo
9•breve•2h ago•1 comments

I taught my neighbor to keep the volume down

https://idiallo.com/blog/teaching-my-neighbor-to-keep-the-volume-down
499•firefoxd•6h ago•195 comments

Efficient String Compression for Modern Database Systems

https://cedardb.com/blog/string_compression/
76•jandrewrogers•2d ago•11 comments

Typechecking is undecidable when 'type' is a type (1989) [pdf]

https://dspace.mit.edu/bitstream/handle/1721.1/149366/MIT-LCS-TR-458.pdf?sequence=6
53•zem•2d ago•28 comments

Founding is a snowball

https://blog.bawolf.com/p/founding-is-a-snowball
23•bryantwolf•3d ago•6 comments

Time Machine-style Backups with rsync (2018)

https://samuelhewitt.com/blog/2018-06-05-time-machine-style-backups-with-rsync
5•accrual•1h ago•0 comments

Troublemaker: The fierce, unruly life of Jessica Mitford

https://www.lrb.co.uk/the-paper/v48/n02/rosemary-hill/one-of-the-worst-things
6•against•4d ago•1 comments

What I learned building an opinionated and minimal coding agent

https://mariozechner.at/posts/2025-11-30-pi-coding-agent/
344•SatvikBeri•15h ago•145 comments

MicroPythonOS graphical operating system delivers Android-like user experience

https://www.cnx-software.com/2026/01/29/micropythonos-graphical-operating-system-delivers-android...
172•mikece•3d ago•50 comments

Two kinds of AI users are emerging. The gap between them is astonishing

https://martinalderson.com/posts/two-kinds-of-ai-users-are-emerging/
3•martinald•1h ago•0 comments

Building Your Own Efficient uint128 in C++

https://solidean.com/blog/2026/building-your-own-u128/
15•PaulHoule•4h ago•0 comments

Clearspace (YC W23) Is Hiring an Applied Researcher (ML)

https://www.ycombinator.com/companies/clearspace/jobs/GOWiDwp-research-engineer-at-clearspace
1•anteloper•6h ago

A Crisis comes to Wordle: Reusing old words

https://forkingmad.blog/wordle-crisis/
43•cyanbane•7h ago•51 comments

TIL: Apple Broke Time Machine Again on Tahoe

https://taoofmac.com/space/til/2026/02/01/1630
170•rcarmo•5h ago•94 comments

Reliable 25 Gigabit Ethernet via Thunderbolt

https://kohlschuetter.github.io/blog/posts/2026/01/27/tb25/
205•kohlschuetter•5d ago•103 comments

Amiga Unix (Amix)

https://www.amigaunix.com/doku.php/home
109•donatj•14h ago•39 comments

Show HN: ÆTHRA – Writing Music as Code

59•CzaxTanmay•2d ago•14 comments

FOSDEM 2026 – Open-Source Conference in Brussels – Day#1 Recap

https://gyptazy.com/blog/fosdem-2026-opensource-conference-brussels/
177•yannick2k•14h ago•105 comments

MRI scans show exercise can make the brain look younger

https://www.sciencedaily.com/releases/2026/01/260121034130.htm
57•amichail•3h ago•13 comments

Towards a science of scaling agent systems: When and why agent systems work

https://research.google/blog/towards-a-science-of-scaling-agent-systems-when-and-why-agent-system...
37•gmays•7h ago•16 comments

The Book of PF, 4th edition

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

1-Click RCE to steal your Moltbot data and keys

https://depthfirst.com/post/1-click-rce-to-steal-your-moltbot-data-and-keys
146•arwt•5h ago•65 comments

VisualJJ – Jujutsu in Visual Studio Code

https://www.visualjj.com/
148•demail•4d ago•66 comments

English professors double down on requiring printed copies of readings

https://yaledailynews.com/articles/english-professors-double-down-on-requiring-printed-copies-of-...
106•cmsefton•9h ago•149 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?