frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

X5.1 solar flare, G4 geomagnetic storm watch

https://www.spaceweatherlive.com/en/news/view/593/20251111-x5-1-solar-flare-g4-geomagnetic-storm-...
163•sva_•5h ago•43 comments

.NET MAUI is coming to Linux and the browser, powered by Avalonia

https://avaloniaui.net/blog/net-maui-is-coming-to-linux-and-the-browser-powered-by-avalonia
88•vyrotek•3h ago•64 comments

I didn't reverse-engineer the protocol for my blood pressure monitor in 24 hours

https://james.belchamber.com/articles/blood-pressure-monitor-reverse-engineering/
122•jamesbelchamber•5h ago•55 comments

Laptops adorned with creative stickers

https://stickertop.art/main/
184•z303•1w ago•190 comments

Four strange places to see London's Roman Wall

https://diamondgeezer.blogspot.com/2025/11/odd-places-to-see-londons-roman-wall.html
69•zeristor•4h ago•18 comments

Heroku Support for .NET 10

https://www.heroku.com/blog/support-for-dotnet-10-lts-what-developers-need-know/
37•runesoerensen•4h ago•7 comments

A modern 35mm film scanner for home

https://www.soke.engineering/
147•QiuChuck•6h ago•107 comments

Why Nietzsche Matters in the Age of Artificial Intelligence

https://cacm.acm.org/blogcacm/why-nietzsche-matters-in-the-age-of-artificial-intelligence/
45•pseudolus•2h ago•20 comments

The terminal of the future

https://jyn.dev/the-terminal-of-the-future
113•miguelraz•6h ago•55 comments

The history of Casio watches

https://www.casio.com/us/watches/50th/Heritage/1970s/
163•qainsights•3d ago•90 comments

A catalog of side effects

https://bernsteinbear.com/blog/compiler-effects/
75•speckx•6h ago•5 comments

Pikaday: A friendly guide to front-end date pickers

https://pikaday.dbushell.com
133•mnemonet•11h ago•68 comments

My fan worked fine, so I gave it WiFi

https://ellis.codes/blog/my-fan-worked-fine-so-i-gave-it-wi-fi/
123•woolywonder•6d ago•48 comments

Scaling HNSWs

https://antirez.com/news/156
150•cyndunlop•12h ago•32 comments

Collaboration sucks

https://newsletter.posthog.com/p/collaboration-sucks
310•Kinrany•6h ago•181 comments

FFmpeg to Google: Fund us or stop sending bugs

https://thenewstack.io/ffmpeg-to-google-fund-us-or-stop-sending-bugs/
546•CrankyBear•8h ago•414 comments

Meticulous (YC S21) is hiring to redefine software dev

https://jobs.ashbyhq.com/meticulous/3197ae3d-bb26-4750-9ed7-b830f640515e
1•Gabriel_h•5h ago

We ran over 600 image generations to compare AI image models

https://latenitesoft.com/blog/evaluating-frontier-ai-image-generation-models/
117•kalleboo•9h ago•68 comments

Modern Optimizers – An Alchemist's Notes on Deep Learning

https://notes.kvfrans.com/7-misc/modern-optimizers.html
10•maxall4•4d ago•0 comments

Adk-go: code-first Go toolkit for building, evaluating, and deploying AI agents

https://github.com/google/adk-go
45•maxloh•6h ago•12 comments

Terminal Latency on Windows (2024)

https://chadaustin.me/2024/02/windows-terminal-latency/
90•bariumbitmap•8h ago•71 comments

The Department of War just shot the accountants and opted for speed

https://steveblank.com/2025/11/11/the-department-of-war-just-shot-the-accountants-and-opted-for-s...
122•ridruejo•11h ago•185 comments

iPhone Pocket

https://www.apple.com/newsroom/2025/11/introducing-iphone-pocket-a-beautiful-way-to-wear-and-carr...
436•soheilpro•16h ago•1104 comments

Agentic pelican on a bicycle

https://www.robert-glaser.de/agentic-pelican-on-a-bicycle/
48•todsacerdoti•6h ago•32 comments

Learning to Model the World with Language

https://dynalang.github.io/
13•jxmorris12•5d ago•0 comments

Cache-friendly, low-memory Lanczos algorithm in Rust

https://lukefleed.xyz/posts/cache-friendly-low-memory-lanczos/
108•lukefleed•9h ago•18 comments

Array-programming the Mandelbrot set

https://jcmorrow.com/mandelbrot/
54•jcmorrow•4d ago•8 comments

Xortran - A PDP-11 Neural Network With Backpropagation in Fortran IV

https://github.com/dbrll/Xortran
32•rahen•6h ago•4 comments

Étude in C minor (2020)

https://zserge.com/posts/etude-in-c/
56•etrvic•1w ago•11 comments

Show HN: Cactoide – Federated RSVP Platform

https://cactoide.org/
54•orbanlevi•9h ago•21 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•5mo ago

Comments

balloob•5mo 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•5mo ago
Discussion for the other article in the series:

https://news.ycombinator.com/item?id=44011381

tomhow•5mo ago
Comments moved thither. Thanks!
pabs3•5mo ago
They are two different articles, I don't think that was correct.
tomhow•5mo 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•5mo ago
Thanks for the response, guess that makes sense.
pabs3•5mo 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?