frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

NPM packages from Red Hat have been compromised

https://github.com/RedHatInsights/javascript-clients/issues/492
497•kurmiashish•2h ago•254 comments

CS336: Language Modeling from Scratch

https://cs336.stanford.edu/
77•kristianpaul•1h ago•6 comments

Windows GOG DOS Games on M-Series Macs

https://f055.net/technology/windows-gog-dos-games-on-m-series-macs/
55•f055•2h ago•36 comments

Flipper Zero Zig Template

https://github.com/NishantJoshi00/flipper-template
54•Nars088•2h ago•3 comments

The Pirate Bay Remains Resilient, 20 Years After the Raid

https://torrentfreak.com/the-pirate-bay-remains-resilient-20-years-after-the-raid/
132•speckx•1h ago•37 comments

A 10 year old Xeon is all you need

https://point.free/blog/gemma-4-on-a-2016-xeon/
471•cafkafk•9h ago•211 comments

Sysadmining Like It's 2009

https://lambdacreate.com/posts/sysadmining-like-its-2009
41•yacin•2h ago•8 comments

Launch HN: Expanse (YC P26) – Unlock Wasted GPU Capacity

36•ismaeel_bashir•2h ago•3 comments

The Dirt That Refused to Die

https://www.quantamagazine.org/the-dirt-that-refused-to-die-20260601/
10•speckx•43m ago•0 comments

Linux Basics for Hackers

https://github.com/ahegazy0/linux-basics-for-hackers-notes
35•ibobev•2h ago•10 comments

Only 17% of all 64-bit Integers are products of two 32-bit integers

https://lemire.me/blog/2026/05/22/only-17-of-all-64-bit-integers-are-products-of-two-32-bit-integ...
97•sebg•3d ago•41 comments

I made my phone slow on purpose

https://vinewallapp.com/notes/i-made-my-phone-slow-on-purpose/
19•gcampos•3d ago•8 comments

"The Apple Boogie" 1987 Mac Promo Album Cassette Tape [video]

https://www.youtube.com/watch?v=chJHB-btMNI
18•1970-01-01•2d ago•2 comments

Tracing HTTP Requests with Go's net/HTTP/httptrace

https://blainsmith.com/articles/httptrace-with-go/
128•speckx•3d ago•8 comments

Radxa Dragon Q8B: A Laptop Cosplaying as an SBC?

https://bret.dk/radxa-dragon-q8b-a-laptop-cosplaying-as-an-sbc/
15•gainsurier•2h ago•10 comments

Nvidia Cosmos 3

https://developer.nvidia.com/blog/develop-physical-ai-reasoning-world-and-action-models-with-nvid...
76•tosh•2h ago•12 comments

Chuwi Minibook X

https://tylercipriani.com/blog/2026/05/28/chuwi-minibook-x/
356•thcipriani•16h ago•269 comments

Movwin: My (Unpublished) TUI Framework

https://movq.de/blog/postings/2026-05-29/0/POSTING-en.html
38•zdw•2d ago•5 comments

KDE at 30

https://kde.org/anniversaries/30/
41•Kye•1h ago•23 comments

Cloudflare Turnstile requiring fingerprintable WebGL

https://hacktivis.me/articles/cloudflare-turnstile-webgl-fingerprinting
751•HypnoticOcelot•1d ago•429 comments

Show HN: A CSS 3D Engine (no WebGL)

https://github.com/LayoutitStudio/polycss
11•rofko•1h ago•3 comments

Benchmarking SurrealDB 3.x vs. Postgres, Mongo, Neo4j and Redis (With Fsync)

https://surrealdb.com/blog/surrealdb-3-x-by-the-numbers
63•itsezc•3d ago•22 comments

You Must Fix Your Asserts (Zig)

https://kristoff.it/blog/fix-your-asserts/
19•signa11•3h ago•1 comments

No Raise, No Promotion: 1 in 4 White-Collar Workers Are Stalling Out

https://www.wsj.com/lifestyle/careers/white-collar-workers-career-nyu-study-a81a7d9c
119•charliebwrites•1h ago•104 comments

Decades of Effort Restore Steelhead and Salmon Passage on Alameda Creek

https://www.fisheries.noaa.gov/feature-story/decades-effort-restore-steelhead-and-salmon-passage-...
200•rawgabbit•2d ago•42 comments

Using Git's rerere feature to escape recurring conflict hell

https://gist.github.com/skipcloud/f1033afb4fa5681d69fa63458cc95928
55•ankitg12•8h ago•22 comments

The SLAX Scripting Language: An Alternate Syntax for XSLT

http://juniper.github.io/libslax/slax-manual.html
29•thefilmore•2d ago•10 comments

ChatGPT for Google Sheets exfiltrates workbooks

https://www.promptarmor.com/resources/gpt-for-google-sheets-data-exfiltration
298•hackerBanana•19h ago•109 comments

1-Bit Bonsai Image 4B Image Generation for Local Devices

https://prismml.com/news/bonsai-image-4b
438•modinfo•1d ago•185 comments

Dav2d

https://jbkempf.com/blog/2026/dav2d/
531•captain_bender•1d ago•193 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?