frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

USB Cheat Sheet

https://fabiensanglard.net/usbcheat/index.html
54•gwerbret•1h ago•11 comments

The Free Universal Construction Kit

https://fffff.at/free-universal-construction-kit/
233•robinhouston•3d ago•41 comments

1-Bit Hokusai's "The Great Wave" (2023)

https://www.hypertalking.com/2023/05/08/1-bit-pixel-art-of-hokusais-the-great-wave-off-kanagawa/
499•stephen-hill•3d ago•85 comments

Using coding assistance tools to revive projects you never were going to finish

https://blog.matthewbrunelle.com/its-ok-to-use-coding-assistance-tools-to-revive-the-projects-you...
133•speckx•7h ago•92 comments

The Joy of Folding Bikes

https://blog.korny.info/2026/04/19/the-joy-of-folding-bikes
54•pavel_lishin•3d ago•25 comments

Trump fires all 24 members of the U.S. National Science Foundation

https://www.science.org/content/article/trump-fires-nsf-s-oversight-board
136•skullone•56m ago•31 comments

New 10 GbE USB adapters are cooler, smaller, cheaper

https://www.jeffgeerling.com/blog/2026/new-10-gbe-usb-adapters-cooler-smaller-cheaper/
529•calcifer•17h ago•306 comments

Mine, an IDE for Coalton and Common Lisp

https://coalton-lang.github.io/mine/
50•varjag•5h ago•11 comments

Simulacrum of Knowledge Work

https://blog.happyfellow.dev/simulacrum-of-knowledge-work/
69•thehappyfellow•6h ago•29 comments

Desmond Morris has died

https://www.bbc.com/news/articles/c51y797v200o
88•martey•5d ago•14 comments

How Hard Is It to Open a File?

https://blog.sebastianwick.net/posts/how-hard-is-it-to-open-a-file/
34•ffin•1d ago•5 comments

Show HN: Kloak, A secret manager that keeps K8s workload away from secrets

https://getkloak.io/
34•neo2006•4h ago•33 comments

Martin Galway's music source files from 1980's Commodore 64 games

https://github.com/MartinGalway/C64_music
155•ingve•12h ago•20 comments

What async promised and what it delivered

https://causality.blog/essays/what-async-promised/
129•zdw•3d ago•134 comments

GPT‑5.5 Bio Bug Bounty

https://openai.com/index/gpt-5-5-bio-bug-bounty/
121•Murfalo•9h ago•93 comments

Discret 11, the French TV encryption of the 80s

https://fabiensanglard.net/discret11/
141•adunk•12h ago•23 comments

Lute: A Standalone Runtime for Luau

https://lute.luau.org/
50•vrn-sn•3d ago•7 comments

Which one is more important: more parameters or more computation? (2021)

https://parl.ai/projects/params_vs_compute/
41•jxmorris12•1d ago•7 comments

Math Is Hard

http://miod.online.fr/software/openbsd/stories/vaxfp.html
5•signa11•2d ago•0 comments

A web-based RDP client built with Go WebAssembly and grdp

https://github.com/nakagami/grdpwasm
102•mariuz•12h ago•41 comments

Hokusai and Tesselations

https://dl.ndl.go.jp/pid/1899550/1/11/
85•srean•6h ago•13 comments

America's Geothermal Breakthrough Could Unlock a 150-Gigawatt Energy Revolution

https://oilprice.com/Alternative-Energy/Geothermal-Energy/Americas-Geothermal-Breakthrough-Could-...
46•sleepyguy•3h ago•41 comments

Insights into firewood use by early Middle Pleistocene hominins

https://www.sciencedirect.com/science/article/pii/S0277379126001824
45•wslh•3d ago•19 comments

Only one side will be the true successor to MS-DOS – Windows 2.x

https://blisscast.wordpress.com/2026/04/21/windows-2-gui-wonderland-12a/
67•keepamovin•12h ago•53 comments

Plain text has been around for decades and it’s here to stay

https://unsung.aresluna.org/plain-text-has-been-around-for-decades-and-its-here-to-stay/
264•rbanffy•22h ago•131 comments

Replace IBM Quantum back end with /dev/urandom

https://github.com/yuvadm/quantumslop/blob/25ad2e76ae58baa96f6219742459407db9dd17f5/URANDOM_DEMO.md
329•pigeons•22h ago•44 comments

Lambda Calculus Benchmark for AI

https://victortaelin.github.io/lambench/
128•marvinborner•12h ago•38 comments

Sabotaging projects by overthinking, scope creep, and structural diffing

https://kevinlynagh.com/newsletter/2026_04_overthinking/
511•alcazar•1d ago•130 comments

Commenting and approving pull requests

https://www.jakeworth.com/posts/on-commenting-and-approving-pull-requests/
76•jwworth•2d ago•64 comments

North American Millets Alliance(2023)

https://milletsalliance.org/
9•num42•5h ago•2 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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