frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

When Code is Free, Why is Claude is an Electron app?

https://www.dbreunig.com/2026/02/21/why-is-claude-an-electron-app.html
132•dbreunig•1h ago•66 comments

EDuke32 – Duke Nukem 3D (Open-Source)

https://www.eduke32.com/
109•reconnecting•3h ago•35 comments

Parse, Don't Validate and Type-Driven Design in Rust

https://www.harudagondi.space/blog/parse-dont-validate-and-type-driven-design-in-rust/
92•todsacerdoti•3h ago•32 comments

Password managers less secure than promised

https://ethz.ch/en/news-and-events/eth-news/news/2026/02/password-managers-less-secure-than-promi...
35•mono-bob•1h ago•26 comments

Evidence of the bouba-kiki effect in naïve baby chicks

https://www.science.org/doi/10.1126/science.adq7188
16•suddenlybananas•1h ago•4 comments

I verified my LinkedIn identity. Here's what I handed over

https://thelocalstack.eu/posts/linkedin-identity-verification-privacy/
1091•ColinWright•16h ago•391 comments

Toyota Mirai hydrogen car depreciation: 65% value loss in a year

https://carbuzz.com/toyota-mirai-massive-depreciation-one-year/
61•iancmceachern•5h ago•143 comments

zclaw: personal AI assistant in under 888 KB, running on an ESP32

https://github.com/tnm/zclaw
49•tosh•10h ago•31 comments

I Don't Like Magic

https://adactio.com/journal/22399
84•edent•3d ago•64 comments

How far back in time can you understand English?

https://www.deadlanguagesociety.com/p/how-far-back-in-time-understand-english
281•spzb•3d ago•175 comments

Inputlag.science – Repository of knowledge about input lag in gaming

https://inputlag.science
49•akyuu•3h ago•8 comments

Show HN: Llama 3.1 70B on a single RTX 3090 via NVMe-to-GPU bypassing the CPU

https://github.com/xaskasdf/ntransformer
15•xaskasdf•2h ago•1 comments

CXMT has been offering DDR4 chips at about half the prevailing market rate

https://www.koreaherald.com/article/10679206
123•phront•8h ago•99 comments

Canvas_ity: A tiny, single-header <canvas>-like 2D rasterizer for C++

https://github.com/a-e-k/canvas_ity
39•PaulHoule•4h ago•16 comments

What not to write on your security clearance form (1988)

https://milk.com/wall-o-shame/security_clearance.html
346•wizardforhire•6h ago•139 comments

Claws are now a new layer on top of LLM agents

https://twitter.com/karpathy/status/2024987174077432126
151•Cyphase•22h ago•587 comments

MeshTNC is a tool for turning consumer grade LoRa radios into KISS TNC compatib

https://github.com/datapartyjs/MeshTNC
16•todsacerdoti•2h ago•5 comments

Cloudflare outage on February 20, 2026

https://blog.cloudflare.com/cloudflare-outage-february-20-2026/
128•nomaxx117•4h ago•93 comments

The Software Development Lifecycle Is Dead

https://boristane.com/blog/the-software-development-lifecycle-is-dead/
38•zenon_paradox•4h ago•34 comments

Acme Weather

https://acmeweather.com/blog/introducing-acme-weather
160•cryptoz•15h ago•101 comments

Permacomputing

https://wiki.xxiivv.com/site/permacomputing.html
71•tosh•4d ago•17 comments

Be wary of Bluesky

https://kevinak.se/blog/be-wary-of-bluesky
202•kevinak•23h ago•141 comments

Uncovering insiders and alpha on Polymarket with AI

https://twitter.com/peterjliu/status/2024901585806225723
111•somerandomness•1d ago•105 comments

AI uBlock Blacklist

https://github.com/alvi-se/ai-ublock-blacklist
203•rdmuser•15h ago•89 comments

Show HN: Iron-Wolf – Wolfenstein 3D source port in Rust

https://github.com/Ragnaroek/iron-wolf
50•ragnaroekX•7h ago•18 comments

Padlet (YC W13) Is Hiring in San Francisco and Singapore

https://padlet.jobs
1•coffeebite•11h ago

Happy Zelda's 40th first LLM running on N64 hardware (4MB RAM, 93MHz)

https://github.com/sophiaeagent-beep/n64llm-legend-of-Elya
3•AutoJanitor•1h ago•0 comments

Personal Statement of a CIA Analyst

https://antipolygraph.org/statements/statement-038.shtml
107•grubbs•5h ago•64 comments

A solver for Semantle

https://victoriaritvo.com/blog/semantle-solver/
46•evakhoury•3d ago•13 comments

Online Pebble Development

https://cloudpebble.repebble.com/
5•teekert•2h ago•3 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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