frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

More Tailscale tricks for your jailbroken Kindle

https://tailscale.com/blog/jailbroken-kindle-proxy-tun-modes
126•Error6571•3h ago•32 comments

User Interfaces of the Demo Scene

https://www.datagubbe.se/scenegui/
117•zdw•3h ago•15 comments

Codex Security

https://github.com/openai/codex-security
479•bakigul•11h ago•156 comments

Show HN: I was tired of opening 2 tabs for every HN link, so I made a userscript

https://github.com/twalichiewicz/HNewhere
283•twalichiewicz•9h ago•71 comments

Cracking Windows Open: Porting RADV to Win32

https://www.collabora.com/news-and-blog/news-and-events/cracking-windows-open-porting-radv-to-win...
34•zdw•3h ago•7 comments

LearnVector – Andrew Ng's AI company building one‑to‑one learning experiences

https://learnvector.ai/
164•ajhai•6h ago•94 comments

Transformer Transformer: A Unified Model for Motion-Conditioned Robot Co-Design

https://transformer-transformer.github.io/
44•ilreb•4h ago•1 comments

Substack writers, you need a website

https://elizabethtai.com/2026/06/10/substack-writers-you-need-a-website/
512•speckx•15h ago•251 comments

Half-Life ported to Mac OS 9

https://mac-classic.com/news/half-life-ported-to-mac-os-9/
216•freediver•11h ago•104 comments

ReFrame – The EPaper Camera

https://reframe.camera/
103•phil294•8h ago•20 comments

Truth is not a direction: a Tarski attack on LLM probes

https://abeljansma.nl/2026/07/10/truth-is-not-a-direction.html
82•abelaer•1d ago•33 comments

Kimi K3 Architecture Overview and Notes

https://sebastianraschka.com/blog/2026/kimi-k3-architecture-notes.html
398•ModelForge•16h ago•71 comments

Teach yourself programming in ten years (1998)

https://www.norvig.com/21-days.html
118•vinhnx•2d ago•58 comments

Hubble: Open-source notetaking app for you and your agents

https://www.hubble.md/
100•handfuloflight•7h ago•29 comments

Steel Bank Common Lisp version 2.6.7

https://sbcl.org/all-news.html?2.6.7
226•tmtvl•14h ago•95 comments

Mag Computer: A Mag History of RAM (1960–2025)

https://magworld.pw/episodes/computer/
19•evakhoury•4d ago•2 comments

Delayed Gratification – Proud to Be 'Last to Breaking News'

https://www.slow-journalism.com/
288•speerer•16h ago•161 comments

Multiple Mouse Cursors in Wayland

https://blinry.org/multi-seat-wayland/
109•marvinborner•7h ago•71 comments

Log is non-monotonic in PHP and Lua

https://purplesyringa.moe/blog/log-is-non-monotonic-in-php-and-lua/
42•ibobev•5d ago•23 comments

Fixing a bug with byte order marks

https://alexwlchan.net/2026/byte-order-marks/
3•surprisetalk•5d ago•0 comments

Beyond Greece and Rome

https://aeon.co/essays/uncovering-a-global-ancient-history-beyond-greece-and-rome
28•diodorus•1d ago•25 comments

60 Years Ago, a Submerged Submarine Circled the Globe for the First Time (2020)

https://www.popularmechanics.com/military/weapons/a32009109/operation-sandblast-sumbarine-circumn...
9•baud147258•1d ago•3 comments

Hooray for the Sockets Interface

https://blog.apnic.net/2026/07/28/hooray-for-the-sockets-interface/
25•jruohonen•5h ago•16 comments

The iPhone Upgrade Program is being replaced by Apple Upgrade

https://www.apple.com/shop/iphone/iphone-upgrade-program
169•lkurtz•14h ago•317 comments

Zig's Incremental Compilation Internals

https://mlugg.co.uk/posts/incremental-compilation-internals/
227•garyhtou•16h ago•159 comments

Interview with Boris Cherny [video]

https://www.youtube.com/watch?v=qyPCVqFUyDo
52•knighthacker•1d ago•60 comments

Una GPS smart watch – Repairable, USB-C charging, developer-friendly

https://unawatch.com/
190•pimterry•17h ago•125 comments

Now is the time to give LLMs access to the ACM digital library

https://cacm.acm.org/opinion/now-is-the-time-to-give-llms-access-to-the-acm-digital-library/
149•rbanffy•17h ago•120 comments

Discovering Cryptographic Weaknesses with Claude

https://www.anthropic.com/research/discovering-cryptographic-weaknesses
211•gslin•14h ago•149 comments

Lightweight Spring Boot Monitoring Without Prometheus and Grafana

https://pvrlabs.xyz/articles/lightweight-spring-boot-monitoring.html
26•ejboy•7h ago•3 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?