frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Agent memory needs its OpenTelemetry moment

https://www.lorekit.io/blog/open-agent-memory-format
47•mthines•2h ago•31 comments

Goodbye Claude, Hello Pi

https://caleb.software/posts/claude-to-pi.html
343•karagenit•7h ago•204 comments

GitHub Down Again?

https://github.com/torvalds/linux
84•ridowk•1h ago•68 comments

Clj.rs – a Clojure dialect implemented in Rust

https://clj.rs/
68•simonpure•3d ago•8 comments

What I run on my $10 USD OpenStick homelab

https://blog.bosscher.ch/posts/openstick/
596•LaurensBER•16h ago•112 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
411•shmulc•14h ago•277 comments

New typeface using intricate designs from Shakespeare's First Folio (2023)

https://www.itsnicethat.com/news/typeland-shakespeares-globe-amifer-folio-graphic-design-090323
9•bryanrasmussen•3d ago•4 comments

WaveDudeNext 2D Wave Simulator

https://github.com/graealex/WaveDudeNext
16•sweetdingoes•3h ago•3 comments

Kirlian Photography: Building Your Own Equipment

https://imagesco.com/articles/kirlian/kirlian-photography.html
52•joebig•6h ago•9 comments

Finding Xanadu: Inside a JRPG classic translation 15 years in the making

https://readonlymemo.com/legend-of-xanadu-pc-engine-fan-translation-interview-making-of/
22•speckx•2d ago•0 comments

I'm Rewriting IBM SPSS Statistics in 100% Safe Rust, Alone

https://github.com/kobaltgit/StatCraft
11•kobaltGIT•2h ago•6 comments

Earliest evidence of cannabis use found in ancient Siberian tomb

https://www.cnn.com/2026/11/05/science/ancient-cannabis-siberia-scli-intl
4•mooreds•2d ago•0 comments

Need for Speed Underground 2 online in the browser

https://nfsu2.xyz/
1000•fluxusars•1d ago•253 comments

Making any integer with four 2s (2025)

https://eli.thegreenplace.net/2025/making-any-integer-with-four-2s/
151•germanrabbit•12h ago•37 comments

Consumer brain wave headsets threaten privacy

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

ISponsorBlockTV: SponsorBlock client for all YouTube TV clients

https://github.com/dmunozv04/isponsorblocktv
46•xnx•7h ago•10 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/
145•rbanffy•3d ago•93 comments

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

https://maxxbench.unlap.ai/research/why-maxxbench/
325•antiuniverse•17h ago•84 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/
147•xiaoyu2006•11h ago•94 comments

Every Mac comes with an (undocumented) family member classifier

https://8rank.ai/game/apple-intelligence-personal-knowledge-graph
739•infwhispers•1d ago•393 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...
338•thunderbong•23h ago•317 comments

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

https://github.com/hedgerow-dev/coldframe
245•hedgerow-dev•17h ago•59 comments

Amsterdam School

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

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

https://github.com/crmne/zapfast
81•handfuloflight•9h ago•55 comments

The end of Microsoft Research's AI Frontiers group

https://hunch.net/?p=13764006
464•srean•17h ago•277 comments

The $8 Linux Computer (2022)

http://thelittleengineerthatcould.blogspot.com/2022/12/the-8-linux-computer.html
240•zenincognito•21h ago•92 comments

Commodore PET – The Worlds First Personal Computer

https://www.commodore.ca/commodore-products/commodore-pet-the-worlds-first-personal-computer/
57•andsoitis•11h ago•19 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-...
473•user_7832•18h ago•301 comments

Every processor die anyone has photographed and given away

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

Asahi Linux Progress Linux 7.3

https://asahilinux.org/2026/11/progress-report-7-3/
386•ackyshake•1d ago•335 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?