frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Dav2d

https://jbkempf.com/blog/2026/dav2d/
208•captain_bender•2h ago•54 comments

The Website Specification

https://specification.website/
295•k1m•7h ago•120 comments

London's Free Roof Terraces

https://diamondgeezer.blogspot.com/2026/05/londons-free-roof-terraces.html
157•zeristor•7h ago•73 comments

Domain expertise has always been the real moat

https://www.brethorsting.com/blog/2026/05/domain-expertise-has-always-been-the-real-moat/
718•aaronbrethorst•17h ago•416 comments

Security Envelope Pattern collection – S.E.C.R.E.T

https://secret-archive.org/
46•ColinWright•2d ago•4 comments

Shantell Sans (2023)

https://shantellsans.com/process
319•aleda145•16h ago•35 comments

One year of Roto, a compiled scripting language for Rust

https://blog.nlnetlabs.nl/one-year-of-roto-the-compiled-scripting-language-for-rust/
76•Hasnep•2d ago•16 comments

A Gentle Introduction to Lattice-Based Cryptography [pdf]

https://cryptography101.ca/wp-content/uploads/lattice-based-cryptography.pdf
119•jayhoon•2d ago•7 comments

United Airlines 767 Returns to Newark After Bluetooth Name Sparks Alert

https://simpleflying.com/united-airlines-767-returns-newark-bluetooth-name-alert/
43•Eridanus2•1h ago•28 comments

The AV2 Video Standard Has Released (Final v1.0 Specification)

https://av2.aomedia.org
272•ksec•16h ago•119 comments

I found a seashell in the middle of the desert

https://github.com/Hawzen/I-found-a-seashell-in-the-middle-of-the-desert#i-found-a-seashell-in-th...
367•Hawzen•2d ago•99 comments

I Put a Datacenter GPU in My Gaming PC for £200

https://blog.tymscar.com/posts/v100localllm/
10•birdculture•28m ago•0 comments

Avian Visitors

https://theodore.net/projects/AvianVisitors/
75•fdb•8h ago•7 comments

Show HN: Breathe CLI – Paced resonance breathing in the macOS terminal

https://github.com/marekkowalczyk/breathe-cli
73•marekkowalczyk•17h ago•9 comments

A pictorial introduction to differential geometry (2017)

https://arxiv.org/abs/1709.08492
79•ricudis•8h ago•2 comments

What it's like to have your insulin pump die while you're on vacation

https://blog.lauramichet.com/what-its-like-to-have-the-machine-that-keeps-you-alive-die-while-you...
31•speckx•2d ago•23 comments

Racket v9.2

https://blog.racket-lang.org/2026/05/racket-v9-2.html
201•spdegabrielle•3d ago•17 comments

Telli (YC F24) is hiring in engineering, design, and GTM [Berlin, on-site]

https://hi.telli.com/join-us
1•sebselassie•7h ago

Associative learning turns DEET from aversive to appetitive in Aedes aegypti

https://journals.biologists.com/jeb/article/229/10/jeb251935/371741/Associative-learning-switches...
51•croes•2d ago•22 comments

Mechanical Pencil: An illustrated celebration of the engineering around us

https://mechanical-pencil.com/
124•Muhammad523•13h ago•16 comments

Accenture to acquire Ookla

https://newsroom.accenture.com/news/2026/accenture-to-acquire-ookla-to-strengthen-network-intelli...
305•Garbage•21h ago•153 comments

Microsoft Office 2019 and 2021 for Mac view-only conversion

https://consumerrights.wiki/w/Microsoft_Office_2019_and_2021_for_Mac_view-only_conversion_(2026)
930•antipurist•14h ago•328 comments

Openrsync: An implementation of rsync, by the OpenBSD team

https://github.com/kristapsdz/openrsync
443•sph•1d ago•162 comments

Inkstravaganza

https://www.inkandswitch.com/newsletter/dispatch-015/
4•surprisetalk•3d ago•0 comments

Backpressure is all you need

https://www.lucasfcosta.com/blog/backpressure-is-all-you-need
47•lucasfcosta•2h ago•46 comments

Voxel Space (2017)

https://s-macke.github.io/VoxelSpace/
294•davikr•23h ago•62 comments

Zig ELF Linker Improvements Devlog

https://ziglang.org/devlog/2026/#2026-05-30
219•kristoff_it•20h ago•84 comments

Mysteries of the Griffin iMate

https://www.projectgus.com/2023/04/griffin-imate/
28•geerlingguy•4d ago•5 comments

Pandoc Templates

https://pandoc-templates.org/
419•ankitg12•1d ago•55 comments

Ahoy, DECmate II the little PDP-8 that could

http://oldvcr.blogspot.com/2026/05/ahoy-decmate-ii-little-pdp-8-that-could.html
46•TMWNN•9h ago•7 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?