frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

What I run on my $10 USD OpenStick homelab

https://blog.bosscher.ch/posts/openstick/
447•LaurensBER•10h ago•96 comments

Claude Code's "Don't Ask Again" exposes passwords in 1,122 public GitHub files

https://apiiro.com/blog/coding-agents-leaking-secrets-github-dont-ask-again
266•shmulc•8h ago•172 comments

ZapFast: A fast, native WhatsApp client in Rust and egui

https://github.com/crmne/zapfast
18•handfuloflight•2h ago•6 comments

Making any integer with four 2s (2025)

https://eli.thegreenplace.net/2025/making-any-integer-with-four-2s/
82•germanrabbit•6h ago•23 comments

GitHub New pull request overview page in public preview

https://github.blog/changelog/2026-11-05-new-pull-request-overview-page-in-public-preview/
98•xiaoyu2006•5h ago•66 comments

Goodbye Claude, Hello Pi

https://caleb.software/posts/claude-to-pi.html
9•karagenit•1h ago•9 comments

Uranium cubes reveal why the German nuclear project failed

https://arstechnica.com/science/2026/11/uranium-cubes-reveal-why-the-german-nuclear-project-failed/
93•rbanffy•2d ago•53 comments

Need for Speed Underground 2 online in the browser

https://nfsu2.xyz/
867•fluxusars•19h ago•238 comments

Amsterdam School

https://architecture-history.org/schools/AMSTERDAM%20SCHOOL.html
12•bondarchuk•4d ago•1 comments

MaxxBench – "Nice DeepSWE score. But is it true?"

https://maxxbench.unlap.ai/research/why-maxxbench/
240•antiuniverse•11h ago•67 comments

Show HN: Coldframe, a honeypot that poses as a supermarket fridge controller

https://github.com/hedgerow-dev/coldframe
207•hedgerow-dev•11h ago•44 comments

Every Mac comes with an (undocumented) family member classifier

https://8rank.ai/game/apple-intelligence-personal-knowledge-graph
647•infwhispers•19h ago•362 comments

Commodore PET – The Worlds First Personal Computer

https://www.commodore.ca/commodore-products/commodore-pet-the-worlds-first-personal-computer/
33•andsoitis•5h ago•10 comments

I Use Development-Driven Specs, Not Spec-Driven Development

https://github.com/waywardgeek/ensemble
3•WaywardGeek•57m ago•1 comments

The end of Microsoft Research's AI Frontiers group

https://hunch.net/?p=13764006
425•srean•10h ago•252 comments

Every Windows 11 app should kill Electron, and Discord just showed why

https://www.windowslatest.com/2026/11/06/every-windows-11-app-should-kill-electron-and-discord-ju...
260•thunderbong•17h ago•230 comments

Turning every radio into a radar

https://tiaminetworks.com/turning-every-radio-into-a-radar/
44•hasley•4d ago•9 comments

Apple’s grey list: Words and phrases your iPhone won’t help you spell

https://www.theguardian.com/technology/2026/nov/06/struggling-to-spell-male-chauvinist-pig-apple-...
407•user_7832•11h ago•266 comments

Five memorable books about programming (2008)

https://prog21.dadgum.com/19.html
97•andsoitis•11h ago•62 comments

The $8 Linux Computer (2022)

http://thelittleengineerthatcould.blogspot.com/2022/12/the-8-linux-computer.html
211•zenincognito•14h ago•87 comments

IRA Velinsky – Commodore's Industrial Designer

https://www.commodore.ca/commodore-history/ira-velinsky-commodores-amazing-industrial-designer/
23•erickhill•6h ago•1 comments

Consumer brain wave headsets threaten privacy

https://www.science.org/content/article/wearable-device-makers-are-harvesting-brain-data-train-ai...
6•maxall4•2h ago•0 comments

Study solved a 150-year-old mystery into the identity of the extinct giant crane

https://www.bournemouth.ac.uk/news/2026-10-28/study-has-solved-150-year-old-mystery-identity-exti...
20•gmays•4d ago•0 comments

GeoWorks, Microsoft Windows' Upstart '90s Competitor (2016)

https://www.atlasobscura.com/articles/the-history-of-geoworks-microsoft-windows-upstart-90s-compe...
51•andsoitis•10h ago•20 comments

Show HN: Where Were We

https://wherewerewe.app/
34•zkiihne•7h ago•14 comments

Retro Song Bird: Plug in any Game Boy cartridge to hear the soundtrack

https://www.retrosongbird.com/
52•hentrep•13h ago•16 comments

Every processor die anyone has photographed and given away

https://sheets.works/data-viz/cpu-dies
97•user_7832•12h ago•18 comments

Asahi Linux Progress Linux 7.3

https://asahilinux.org/2026/11/progress-report-7-3/
347•ackyshake•23h ago•296 comments

Text.js: Build full-stack React apps that render inside console.log

https://textjs.org/
89•nateb2022•3d ago•48 comments

Running a law firm on Free software

https://decoded.legal/blog/2026/11/running-a-law-firm-on-free-software-2026-edition/
248•DeepLogin•19h ago•123 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?