frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

SWE-CI: Evaluating Agent Capabilities in Maintaining Codebases via CI

https://arxiv.org/abs/2603.03823
39•mpweiher•2h ago•3 comments

Cloud VM benchmarks 2026

https://devblog.ecuadors.net/cloud-vm-benchmarks-2026-performance-price-1i1m.html
234•dkechag•9h ago•101 comments

"Warn about PyPy being unmaintained"

https://github.com/astral-sh/uv/pull/17643
182•networked•8h ago•64 comments

Show HN: Curiosity – DIY 6" Newtonian Reflector Telescope

https://curiosity-telescope.vercel.app/
19•big_Brain69•2h ago•2 comments

From RGB to L*a*b* color space (2024)

https://kaizoudou.com/from-rgb-to-lab-color-space/
34•kqr•4d ago•7 comments

Notes on Writing WASM

https://notes.brooklynzelenka.com/Blog/Notes-on-Writing-Wasm
4•vinhnx•47m ago•0 comments

CasNum

https://github.com/0x0mer/CasNum
281•aebtebeten•13h ago•35 comments

How to run Qwen 3.5 locally

https://unsloth.ai/docs/models/qwen3.5
158•Curiositry•10h ago•44 comments

Rijksmuseum researchers discover new painting by Rembrandt van Rijn

https://www.rijksmuseum.nl/en/press/press-releases/rijksmuseum-researchers-discover-new-painting-...
12•ohjeez•3d ago•0 comments

A decade of Docker containers

https://cacm.acm.org/research/a-decade-of-docker-containers/
301•zacwest•17h ago•202 comments

MonoGame: A .NET framework for making cross-platform games

https://github.com/MonoGame/MonoGame
78•azhenley•7h ago•47 comments

Emacs internals: Deconstructing Lisp_Object in C (Part 2)

https://thecloudlet.github.io/blog/project/emacs-02/
72•thecloudlet•2d ago•2 comments

Dumping Lego NXT firmware off of an existing brick (2025)

https://arcanenibble.github.io/dumping-lego-nxt-firmware-off-of-an-existing-brick.html
205•theblazehen•2d ago•11 comments

Yoghurt delivery women combatting loneliness in Japan

https://www.bbc.com/travel/article/20260302-the-yoghurt-delivery-women-combatting-loneliness-in-j...
290•ranit•20h ago•156 comments

Show HN: A weird thing that detects your pulse from the browser video

https://pulsefeedback.io/
83•kilroy123•3d ago•38 comments

Digital Iris [video]

https://www.youtube.com/watch?v=Kg_2MAgS_pE
7•surprisetalk•3d ago•1 comments

Best performance of a C++ singleton

https://andreasfertig.com/blog/2026/03/best-performance-of-a-cpp-singleton/
34•jandeboevrie•1d ago•20 comments

Autoresearch: Agents researching on single-GPU nanochat training automatically

https://github.com/karpathy/autoresearch
118•simonpure•13h ago•31 comments

The surprising whimsy of the Time Zone Database

https://muddy.jprs.me/links/2026-03-06-the-surprising-whimsy-of-the-time-zone-database/
124•jprs•15h ago•36 comments

I'm Not Consulting an LLM

https://lr0.org/blog/p/gpt/
24•birdculture•1h ago•2 comments

In 1985 Maxell built a bunch of life-size robots for its bad floppy ad

https://buttondown.com/suchbadtechads/archive/maxell-life-size-robots/
111•rfarley04•3d ago•13 comments

Ten years of deploying to production

https://brandonvin.github.io/2026/03/04/ten-years-of-deploying-to-production.html
30•mooreds•2d ago•4 comments

Ask HN: Why there are no actual studies that show AI is more productive?

16•make_it_sure•1h ago•16 comments

FLASH radiotherapy's bold approach to cancer treatment

https://spectrum.ieee.org/flash-radiotherapy
212•marc__1•18h ago•65 comments

macOS code injection for fun and no profit (2024)

https://mariozechner.at/posts/2024-07-20-macos-code-injection-fun/
94•jstrieb•3d ago•17 comments

Files are the interface humans and agents interact with

https://madalitso.me/notes/why-everyone-is-talking-about-filesystems/
222•malgamves•23h ago•121 comments

Sem – Semantic version control. Entity-level diffs on top of Git

https://github.com/ataraxy-labs/sem
6•pabs3•4h ago•0 comments

SigNoz (YC W21) is hiring for engineering, growth and product roles

https://signoz.io/careers
1•pranay01•17h ago

Lisp-style C++ template meta programming

https://github.com/mistivia/lmp
51•mistivia•11h ago•6 comments

To the Polypropylene Makers

https://www.lesswrong.com/posts/HQTueNS4mLaGy3BBL/here-s-to-the-polypropylene-makers
31•raldi•3h ago•4 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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