frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Deno Desktop

https://docs.deno.com/runtime/desktop/
244•GeneralMaximus•2h ago•77 comments

GLM 5.2 vs. Opus

https://techstackups.com/comparisons/glm-5.2-vs-opus/
64•ritzaco•57m ago•30 comments

Help I accidentally a wigglegram

https://lmao.center/blog/wiggle-accidents/
186•gregsadetsky•2d ago•32 comments

Did my old job only exist because of fraud?

https://david.newgas.net/did-my-old-job-only-exist-because-of-fraud/
504•advisedwang•10h ago•225 comments

Apertus – Open Foundation Model for Sovereign AI

https://apertvs.ai/
360•T-A•10h ago•121 comments

There is minimal downside to switching to open models

https://www.marble.onl/posts/cancel_claude.html
203•amarble•11h ago•145 comments

Munich 1991: The Roots of the Current AI Boom

https://people.idsia.ch/~juergen/ai-boom-roots-munich-1991.html
23•tosh•2d ago•4 comments

Memory Safe Inline Assembly

https://fil-c.org/inlineasm
94•pizlonator•2d ago•19 comments

Good results fine tuning a local LLM like Qwen 3:0.6B to categorize questions

https://www.teachmecoolstuff.com/viewarticle/fine-tuning-a-local-llm-to-categorize-questions
118•dev-experiments•9h ago•26 comments

Sakana Fugu

https://sakana.ai/fugu/
110•Finbarr•6h ago•63 comments

Everything is logarithms

https://alexkritchevsky.com/2026/05/25/everything-is-logarithms.html
206•E-Reverance•11h ago•44 comments

Identity verification on Claude

https://support.claude.com/en/articles/14328960-identity-verification-on-claude
725•bathory•19h ago•611 comments

Lisp in the Rust Type System

https://github.com/playX18/lisp-in-types/
48•quasigloam•2d ago•0 comments

How I play video games with spinal muscular atrophy

https://www.openassistivetech.org/how-i-actually-play-video-games-with-sma-the-tools-i-use-every-...
102•dannyobrien•3d ago•15 comments

Danish privacy activist Lars Andersen raided by police

https://twitter.com/LarsAnders1620/status/2068208864747540516#m
209•I_am_tiberius•3h ago•143 comments

JSON-LD explained for personal websites

https://hawksley.dev/blog/json-ld-explained-for-personal-websites/
206•ethanhawksley•13h ago•60 comments

Beyond All Reason (Free Total Annihilation Inspired RTS)

https://www.beyondallreason.info
475•mosiuerbarso•20h ago•279 comments

Japanese verb conjugation the simple hard way

https://underreacted.leaflet.pub/3mmevu6woys27
91•valzevul•9h ago•104 comments

1983 Northern Telecom Commodore Phone

https://www.oldtelephoneroom.ca/1983-northern-telecom-commodore-phone/
47•arexxbifs•7h ago•13 comments

Efficient C++ Programming for Modern C++ CPUs, Chapter 4/part 2

https://6it.dev/blog/infographics-operation-costs-in-cpu-clock-cycles-take-2-80736
45•birdculture•2d ago•5 comments

PowerFox Browser

https://powerfox.jazzzny.me/
125•thisislife2•10h ago•32 comments

Minecraft: Java Edition 26.2, the first version with Vulkan 1.2

https://www.minecraft.net/en-us/article/minecraft-java-edition-26-2
132•ObviouslyFlamer•5d ago•42 comments

Show HN: Teach your kids perfect pitch

https://github.com/paytonjjones/bsharp
125•paytonjjones•19h ago•73 comments

Rent collections are down in New York

https://www.politico.com/news/2026/06/21/rent-collections-are-down-in-new-york-and-no-ones-sure-w...
77•JumpCrisscross•10h ago•290 comments

Show HN: Criterion Closet as a website – pull any of 1,247 films off the shelf

https://the-criterion-closet.vercel.app
96•olievans•1d ago•25 comments

Prefer duplication over the wrong abstraction (2016)

https://sandimetz.com/blog/2016/1/20/the-wrong-abstraction
474•rafaepta•16h ago•313 comments

The minimum viable unit of saleable software

https://brandur.org/minimum-viable-unit
160•brandur•15h ago•60 comments

(How to Write a (Lisp) Interpreter (In Python)) (2010)

https://norvig.com/lispy.html
183•tosh•16h ago•61 comments

Show HN: Recall – Local project memory for Claude Code

https://github.com/raiyanyahya/recall
110•mateenah•11h ago•67 comments

FDA advisors unanimously vote to approve Moderna's mRNA after agency drama

https://arstechnica.com/health/2026/06/fda-advisors-unanimously-vote-to-approve-modernas-mrna-aft...
181•worik•10h ago•94 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?