frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

You don't know HTML Lists

https://blog.frankmtaylor.com/2026/05/13/you-dont-know-html-lists/
154•speckx•1h ago•24 comments

SANA-WM, a 2.6B open-source world model for 1-minute 720p video

https://nvlabs.github.io/Sana/WM/
219•mjgil•6h ago•92 comments

How an Australian Teen Team Is Making Radio Astronomy Affordable for Schools

https://mag.openrockets.com/p/how-an-australian-teen-team-is-making-radio-astronomy-affordable-fo...
77•openrockets•3h ago•24 comments

Kioxia and Dell cram 10 PB into slim 2RU server

https://www.blocksandfiles.com/flash/2026/05/14/kioxia-and-dell-cram-10-pb-into-slim-2ru-server/5...
15•rbanffy•1h ago•7 comments

Windows 9x Subsystem for Linux

https://codeberg.org/hails/wsl9x
58•ibobev•3d ago•25 comments

Accelerando (2005)

https://www.antipope.org/charlie/blog-static/fiction/accelerando/accelerando.html
164•eamag•7h ago•87 comments

Moving away from Tailwind, and learning to structure my CSS

https://jvns.ca/blog/2026/05/15/moving-away-from-tailwind--and-learning-to-structure-my-css-/
269•mpweiher•9h ago•173 comments

Δ-Mem: Efficient Online Memory for Large Language Models

https://arxiv.org/abs/2605.12357
155•44za12•9h ago•38 comments

Show HN: Rocksky – Music scrobbling and discovery on the AT Protocol

https://tangled.org/rocksky.app/rocksky
11•tsiry•1h ago•4 comments

Accelerate

https://github.com/AccelerateHS/accelerate
57•tosh•4h ago•14 comments

DeepSeek-V4-Flash means LLM steering is interesting again

https://www.seangoedecke.com/steering-vectors/
124•Brajeshwar•3h ago•46 comments

Project Gutenberg – keeps getting better

https://www.gutenberg.org/
1087•JSeiko•1d ago•236 comments

Greek Alphabet Cards

https://labs.randomquark.com/alphabet_cards/
71•ricochet11•6h ago•27 comments

Fame! A Misunderstanding: A new translation of Albert Camus's complete notebooks

https://lareviewofbooks.org/article/albert-camus-complete-notebooks-ryan-bloom-existentialism-abs...
6•Caiero•2d ago•1 comments

Futhark by Example

https://futhark-lang.org/examples.html
91•tosh•8h ago•23 comments

My Favorite Bugs: Invalid Surrogate Pairs

https://george.mand.is/2026/05/my-favorite-bugs-invalid-surrogate-pairs/
63•meysamazad•5h ago•34 comments

Clusters become personal (like PCs did)

https://aranya.tech/blog/arrival-of-the-personal-cluster
14•druid•3d ago•5 comments

Kyber (YC W23) Is Hiring a Founding Marketer

https://www.ycombinator.com/companies/kyber/jobs/1rLQAro-founding-marketer-content-community
1•asontha•6h ago

Nearly 50 Years Later, WKRP in Cincinnati Becomes a Real Radio Station

https://www.openculture.com/2026/05/nearly-50-years-later-wkrp-in-cincinnati-becomes-a-real-radio...
72•bookofjoe•4d ago•43 comments

After 8 years, I rewrote my open-source PyTorch curvature library

https://github.com/noahgolmant/pytorch-hessian-eigenthings
39•noahgolmant•2d ago•1 comments

I believe there are entire companies right now under AI psychosis

https://twitter.com/mitchellh/status/2055380239711457578
1726•reasonableklout•22h ago•933 comments

Orthrus-Qwen3: up to 7.8×tokens/forward on Qwen3, identical output distribution

https://github.com/chiennv2000/orthrus
194•FranckDernoncou•20h ago•33 comments

The bird eye was pushed to an evolutionary extreme

https://www.quantamagazine.org/how-the-bird-eye-was-pushed-to-an-evolutionary-extreme-20260513/
191•sohkamyung•2d ago•62 comments

Ploopy Bean: a trackpoint for every computer

https://ploopy.co/shop/bean-pointing-stick/
153•jibcage•3d ago•70 comments

Gaining control of every projector and camera on campus

https://www.edna.land/blogs/posts/scanning/
93•ednaordinary•2d ago•29 comments

A 0-click exploit chain for the Pixel 10

https://projectzero.google/2026/05/pixel-10-exploit.html
421•happyhardcore•1d ago•223 comments

What Were Ancient Greco-Roman Curse Tablets?

https://www.history.com/articles/what-were-ancient-roman-curse-tablets
10•speckx•4d ago•7 comments

The sigmoids won't save you

https://www.astralcodexten.com/p/the-sigmoids-wont-save-you
274•Tomte•1d ago•256 comments

I 3D Printed Origami [video]

https://www.youtube.com/watch?v=FNVBK7-h9Fs
5•Teever•38m ago•1 comments

Frontier AI has broken the open CTF format

https://kabir.au/blog/the-ctf-scene-is-dead
273•frays•11h ago•244 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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