frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Specsmaxxing – On overcoming AI psychosis, and why I write specs in YAML

https://acai.sh/blog/specsmaxxing
80•brendanmc6•2h ago•63 comments

A Couple Million Lines of Haskell: Production Engineering at Mercury

https://blog.haskell.org/a-couple-million-lines-of-haskell/
191•unignorant•8h ago•70 comments

This Month in Ladybird - April 2026

https://ladybird.org/newsletter/2026-04-30/
309•richardboegli•12h ago•64 comments

Dav2d

https://code.videolan.org/videolan/dav2d
462•dabinat•15h ago•123 comments

The IBM Granite 4.1 family of models

https://research.ibm.com/blog/granite-4-1-ai-foundation-models
78•wglb•2d ago•10 comments

Six Years Perfecting Maps on WatchOS

https://www.david-smith.org/blog/2026/04/29/maps-on-watchos/
279•valzevul•11h ago•61 comments

Neanderthals ran 'fat factories' 125,000 years ago (2025)

https://www.universiteitleiden.nl/en/news/2025/07/neanderthals-ran-fat-factories-125000-years-ago
181•andsoitis•12h ago•72 comments

Do_not_track

https://donottrack.sh/
314•RubyGuy•15h ago•100 comments

Care homes and hotels in Japan shut as expansion strategy unravels

https://www.newsonjapan.com/article/149075.php
38•mikhael•7h ago•12 comments

Inventions for battery reuse and recycling increase seven-fold in last decade

https://www.epo.org/en/news-events/news/inventions-battery-reuse-and-recycling-increase-more-seve...
195•JeanKage•2d ago•14 comments

VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage

https://github.com/microsoft/vscode/pull/310226
1151•indrora•12h ago•578 comments

Forging ZK proofs to mint arbitrary DUSK tokens

https://osec.io/blog/2026-04-30-unverified-evaluations-dusk-plonk/
6•deut-erium•2d ago•0 comments

A more efficient implementation of Shor's algorithm

https://lwn.net/Articles/1066156/
77•signa11•2d ago•14 comments

Clojurists Together – Q2 2026 Open Source Funding Announcement

https://www.clojuriststogether.org/news/q2-2026-funding-announcement/
104•dragandj•11h ago•11 comments

The agent harness belongs outside the sandbox

https://www.mendral.com/blog/agent-harness-belongs-outside-sandbox
101•shad42•11h ago•77 comments

Because It Doesn't Have To

https://blog.computationalcomplexity.org/2026/04/because-it-doesnt-have-to.html
48•zdw•3d ago•12 comments

Maryland to ban A.I.-driven price increases in grocery stores

https://www.nytimes.com/2026/05/01/business/surveillance-pricing-groceries-maryland.html
147•doener•7h ago•93 comments

Show HN: State of the Art of Coding Models, According to Hacker News Commenters

https://hnup.date/hn-sota
100•yunusabd•11h ago•50 comments

San Francisco streets with confusingly similar names

https://j-nelson.net/san-francisco-streets-with-similar-names/
25•SeenNotHeard•2d ago•34 comments

Kimi K2.6 just beat Claude, GPT-5.5, and Gemini in a coding challenge

https://thinkpol.ca/2026/04/30/an-open-weights-chinese-model-just-beat-claude-gpt-5-5-and-gemini-...
261•bazlightyear•4h ago•119 comments

A physics engine with incremental rollback for multiplayer games

https://easel.games/blog/2026-rollback-physics
84•BSTRhino•1d ago•27 comments

How fast is a macOS VM, and how small could it be?

https://eclecticlight.co/2026/05/02/how-fast-is-a-macos-vm-and-how-small-could-it-be/
247•moosia•23h ago•86 comments

AI, Intimacy, and the Data You Never Meant to Share

https://fshot.org/techzone/the-algorithm-knows.php
23•victorkulla•6h ago•1 comments

When Dawkins met Claude – Could this AI be conscious?

https://unherd.com/2026/04/is-ai-the-next-phase-of-evolution/
28•pentestercrab•2d ago•152 comments

Musk's AI told me people were coming to kill me (BBC)

https://www.bbc.com/news/articles/c242pzr1zp2o
17•walden789•1h ago•1 comments

Little magazines are back

https://wsjfreeexpression.substack.com/p/little-magazines-are-back
91•prismatic•2d ago•33 comments

The USB Situation

https://randsinrepose.com/archives/the-usb-situation/
125•herbertl•3d ago•144 comments

NetHack 5.0.0

https://nethack.org/v500/release.html
448•rsaarelm•14h ago•139 comments

Dabbling in Erlang, part 2: A minimal introduction (2013)

https://agis.io/post/dabbling-in-erlang-a-minimal-introduction/
27•pasxizeis•1d ago•6 comments

Barman – Backup and Recovery Manager for PostgreSQL

https://github.com/EnterpriseDB/barman
156•nateb2022•3d ago•23 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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