frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Bleached corals thrive within days when touching healthy neighbour

https://www.nature.com/articles/d41586-026-03266-x
270•alkyon•1d ago•57 comments

Dam removals are bringing fish back across the northeastern United States

https://www.smithsonianmag.com/science-nature/dam-removals-are-bringing-fish-back-across-the-nort...
158•sohkamyung•1d ago•45 comments

Retired Penn professor arrested for blocking Uber Eats robot

https://www.phillyvoice.com/philly-woman-arrested-uber-eats-robot-protest/?l
34•johnnyApplePRNG•30m ago•24 comments

Furifont, a Japanese font that shows furigana

https://furifont.antfu.me/
234•plaguna•2d ago•49 comments

DeepSeek-v4.1-Flash-1017

https://huggingface.co/deepseek-ai/DeepSeek-V4.1-Flash-1017
669•theykk•15h ago•562 comments

The Commodore 64 hardware simulator: break chips and pins, see the results

https://github.com/antirez/c64-hw-simulator
129•antirez•2d ago•22 comments

Pele – Mermaid diagrams as themeable SVG

https://pele.run/
195•dchest•8h ago•22 comments

Making chicken transparent using Dorito dust

https://chillphysicsenjoyer.substack.com/p/making-chicken-transparent-using
242•crescit_eundo•10h ago•64 comments

Types of types: Haskell's Kind system

https://thunk.blog/posts/types-of-types-haskell-kind-system/
26•Thom2503•3d ago•16 comments

Gold is now the top U.S. export

https://www.numismaticnews.net/gold-now-top-u-s-export
196•iamnothere•6h ago•110 comments

Source code of the Estonian online voting system

https://github.com/valimised/ivxv
145•theanonymousone•20h ago•128 comments

Chrome and Edge are removing XSLT: what breaks and what does not

https://doctor-seo.net/en/blog/news/chrome-edge-removing-xslt/
68•croes•3h ago•70 comments

Show HN: High-quality duck audio synthesizer

https://celphase.github.io/duck-pond/
71•celphase•10h ago•22 comments

Codex Desktop continuously generates Crashpad pending dumps

https://github.com/openai/codex/issues/25921
50•AIorNot•6h ago•25 comments

An ESPN producer who quit because of sports gambling

https://www.cjr.org/the-interview/nicole-noren-espn-producer-quit-protest-sports-betting-gambling...
121•danso•3d ago•62 comments

Solar surpasses nuclear power globally for first time

https://www.pv-magazine.com/2026/09/29/solar-surpasses-nuclear-power-globally-for-first-time/
453•xbmcuser•10h ago•300 comments

You could have invented transformers from memory

https://alexwang.ai/posts/associative-memory/
491•speckx•1d ago•116 comments

Laser Fault Injection on a Budget: RP2350 Edition

https://courk.cc/rp2350-challenge-laser
35•gregsadetsky•2d ago•8 comments

Each step of decoding a PNG (2022)

https://iter.ca/post/png/
3•jxmorris12•3d ago•0 comments

Artie (YC S23) Is Hiring Enterprise AES and Senior Engineers

https://www.artie.com/careers
1•j-cheong•6h ago

I Became a Citizen of Japan

https://www.derekwessman.com/blog-1/natural
129•luu•6h ago•49 comments

A skeptic's first contact with Kubernetes (2024)

https://blog.davidv.dev/posts/first-contact-with-k8s/
73•pmoriarty•20h ago•38 comments

Vintage Cassettes: 1963-2010

http://vintagecassettes.com/
46•austinallegro•3d ago•7 comments

Show HN: Parin – A 2D game engine between raylib and Godot, written in Dlang

https://github.com/Kapendev/parin
40•Kapendev•1d ago•6 comments

Show HN: Esp32sim – Run ESP32 firmware in the browser

https://github.com/mikroverk/esp32sim
110•joakimeriksson•10h ago•11 comments

Rendering pretty sky in Around The World game

https://frozenfractal.com/blog/2026/10/12/around-the-world-34-a-pretty-sky/
120•ibobev•1d ago•8 comments

JDK 28

https://openjdk.org/projects/jdk/28/
34•ejboy•2h ago•10 comments

Microsoft and CMU team up to train early career software engineers

https://www.cs.cmu.edu/news/2026/microsoft-cmu-praise
54•azhenley•5h ago•64 comments

OpenCode Hacked: User credentials leaked

https://twitter.com/opencode/status/2111516673953935833
695•pranshuchittora•6h ago•120 comments

Show HN: Llmspeed – feel how fast a local LLM runs before you buy the hardware

https://llmspeed.dev/
238•albinstman•19h ago•76 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?