frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Pi 1.0

https://earendil.com/posts/pi-1-0/
1390•sergiotapia•16h ago•442 comments

Shimano Bicycle Museum Review

https://inrng.com/2026/10/shimano-bicycle-museum/
144•pietroppeter•6h ago•24 comments

Several vulnerabilities have been discovered in the Linux kernel

https://lwn.net/Articles/1097401/
362•luispa•12h ago•266 comments

Show HN: Audionaut – an open-source cross-platform multitrack audio editor

https://github.com/kvoltmer/Audionaut
32•vltmrkls•4h ago•9 comments

Clef: Open-weight decision models, and new RL fine-tuning platform

https://blog.cloudflare.com/clef-decision-models/
538•jasondavies•19h ago•189 comments

SvelteKit 3

https://svelte.dev/blog/sveltekit-3-is-here
311•sampsn•15h ago•123 comments

DeepSeek Harness Desktop for macOS and Windows

https://www.deepseek.com/en/harness/
262•Kuyawa•8h ago•131 comments

Pi Durable

https://earendil.com/posts/pi-durable/
411•paulsmith•16h ago•51 comments

Why media fans want to escape algorithms with CDs, DVDs and vinyl

https://www.theguardian.com/media/2026/oct/02/physical-media-fans-streaming-algorithms-cds-dvds-v...
42•beardyw•1h ago•40 comments

Ask HN: Who is hiring? (October 2026)

213•whoishiring•21h ago•210 comments

Git 3.0's upcoming SHA-256 default will be a costly mistake

https://blog.gitbutler.com/git-3-sha-256
410•chmaynard•19h ago•387 comments

Automatic Transmission – a data-privacy study of connected vehicles

https://automatictransmission.khoury.northeastern.edu/index.html
201•rafaelc•15h ago•176 comments

StreetComplete on iOS is now in public beta

https://github.com/streetcomplete/StreetComplete/issues/5421
574•Snowly•1d ago•155 comments

Frog and Toad and the Increasingly Capable Machines

https://www.frogandtoad.ai/
225•supermdguy•13h ago•50 comments

Turbo Haskell

https://comonad.com/reader/2026/turbo-haskell/
116•pjmlp•22h ago•25 comments

How Singapore's government-run dating service works

https://www.singapore-samizdat.com/p/how-singapores-government-run-dating-service-firstdate-works
189•danielfoster•10h ago•170 comments

Using Opus 5.5 to discover a new eyewitness record of the dodo

https://resobscura.substack.com/p/using-opus-55-to-discover-a-new-eyewitness
163•benbreen•15h ago•45 comments

RIP, vector database

https://turbopuffer.com/blog/rip-vector-database
343•razin•20h ago•90 comments

Various Projects Find Hidden SDR Capabilities in ESP32 Microcontrollers

https://www.rtl-sdr.com/various-projects-independently-find-hidden-sdr-capabilities-in-esp32-micr...
242•nkw•21h ago•44 comments

CSS Bed: Classless CSS themes to use as starting points in web development

https://www.cssbed.com
120•sea-gold•14h ago•31 comments

Vote on which of Hacker News' challenges for AI have been met

https://stoppels.ch/goalposts/
156•stabbles•18h ago•189 comments

ArXiv's Updated Rate Limit Policy

https://blog.arxiv.org/2026/10/01/updated-rate-limit-policy/
127•50kIters•15h ago•61 comments

Show HN: Janus – Go binary that runs GGUF models via Vulkan on AMD/Intel/Nvidia

https://github.com/Vibra-Ingenn/Janus
80•Maverick617•15h ago•14 comments

Cloudflare K2: serverless event streams

https://blog.cloudflare.com/cloudflare-k2-streams/
251•elffjs•22h ago•95 comments

Oxygen-deprived underwater zones may not be “dead zones” but clue to early life

https://agupubs.onlinelibrary.wiley.com/doi/10.1029/2026AV002570
107•gumby•17h ago•15 comments

How to speed up the Rust compiler in September 2026

https://nnethercote.github.io/2026/09/30/how-to-speed-up-the-rust-compiler-in-september-2026.html
260•trickypr•23h ago•143 comments

Context Language Models

https://arxiv.org/abs/2609.37725
150•emersonmacro•21h ago•39 comments

Butterflies use optical illusions to dodge predators

https://www.essex.ac.uk/news/2026/09/30/butterflies-use-optical-illusions-to-dodge-predators
56•gmays•12h ago•11 comments

RacketCon Is Saturday

https://con.racket-lang.org/
151•spdegabrielle•21h ago•40 comments

GPT-Synopsys: Frontier Intelligence to Revolutionize Chip Design

https://news.synopsys.com/2026-09-30-OpenAI-and-Synopsys-Announce-GPT-Synopsys-Frontier-Intellige...
180•giuliomagnifico•1d ago•108 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?