frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Your ePub Is Fine. Kobo Disagrees. Blame Adobe

https://andreklein.net/your-epub-is-fine-kobo-disagrees-blame-adobe/
119•sohkamyung•2h ago•39 comments

Write for One Person

https://wizardzines.com/comics/write-for-one-person/
36•evakhoury•2d ago•6 comments

Show HN: Kage – Shadow any website to a single binary for offline viewing

https://github.com/tamnd/kage
386•tamnd•7h ago•89 comments

Rio de Janeiro's "homegrown" LLM appears to be a merge of an existing model

https://github.com/nex-agi/Nex-N2/issues/4
270•unrvl22•9h ago•146 comments

Firewood Splitting Simulator

https://screen.toys/firewood/
616•memalign•4d ago•206 comments

Chaosnet (1981)

https://tumbleweed.nu/r/lm-3/uv/amber.html
60•RGBCube•5h ago•7 comments

Chopped, Stored, Secured – The Story of the Hash Function

https://0xkrt26.github.io/math_behind_security/2026/06/09/the-story-of-the-hash-function.html
17•denismenace•4d ago•3 comments

Show HN: Trace – Offline Mac meeting transcripts you can flag mid-call

https://traceapp.info
87•AG342•1d ago•33 comments

Ask HN: What are you working on? (June 2026)

150•david927•8h ago•548 comments

TorchCodec 0.14: HDR Video Decoding for CPU and CUDA, and Fast Wav Decoder

https://github.com/meta-pytorch/torchcodec/releases/tag/v0.14.0
18•scott_s•4d ago•2 comments

Segmented type appreciation corner (2018)

https://aresluna.org/segmented-type/
59•unexpectedVCR•3d ago•14 comments

Formal methods and the future of programming

https://blog.janestreet.com/formal-methods-at-jane-street-index/?from_theconsensus=1
185•eatonphil•12h ago•68 comments

AI is code – and can't be prompted into being smarter

https://www.theregister.com/ai-and-ml/2026/06/14/ai-is-code-and-cant-be-prompted-into-being-smart...
55•wglb•4h ago•33 comments

Caddy compatibility for zeroserve: 3x throughput and 70% lower latency

https://su3.io/posts/zeroserve-caddy-compat
153•losfair•11h ago•45 comments

Perlisisms (1982)

https://www.cs.yale.edu/homes/perlis-alan/quotes.html
91•tosh•10h ago•42 comments

The only scalable delete in Postgres is DROP TABLE

https://planetscale.com/blog/the-only-scalable-delete
125•hollylawly•3d ago•47 comments

Show HN: Discover Wikipedia articles popular on Hacker News

https://www.orangecrumbs.com/
49•octopus143•7h ago•11 comments

FarOutCompany

https://faroutcompany.com/
99•bookofjoe•10h ago•16 comments

Bitsy

https://bitsy.org/
5•tosh•3d ago•0 comments

Lisp's Influence on Ruby

https://blog.tacoda.dev/lisps-influence-on-ruby-6a54f1a7740e
216•tacoda•3d ago•56 comments

I indexed 669 GB of my GoPro videos using my M1 Max computer and local ML models

272•iliashad•9h ago•63 comments

Stanford grads walk out on Google CEO Sundar Pichai speech

https://twitter.com/maattttbrown/status/2066215255987163246
91•sosomoxie•2h ago•40 comments

The Birth and Death of JavaScript (2014)

https://www.destroyallsoftware.com/talks/the-birth-and-death-of-javascript
210•subset•12h ago•122 comments

USB Power Delivery: Plugging into the Benefits

https://www.aptiv.com/en/insights/article/usb-power-delivery-plugging-into-the-benefits
32•mooreds•3d ago•67 comments

How to earn a billion dollars

https://paulgraham.com/earn.html
436•kingstoned•13h ago•1330 comments

Not everyone is using AI for everything

https://gabrielweinberg.com/p/people-are-consuming-ai-like-they
416•yegg•10h ago•451 comments

Linux 7.1

https://lore.kernel.org/lkml/CAHk-=wi4BF4bMhZNZ1tqs+FFV4OuZRe3ZqdWB+LxRLmRweUzQw@mail.gmail.com/T/#u
226•berlianta•9h ago•82 comments

Abu Fanous

https://en.wikipedia.org/wiki/Abu_Fanous
60•joebig•3h ago•10 comments

The first game engine for robotics

https://luckyrobots.com/
28•arnejenssen•2d ago•19 comments

Inverse Rubric Optimization: A testbed for agent science

https://fulcrum.inc/2026/06/09/inverse-rubric-optimization.html
21•etherio•3d ago•0 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?