frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Microsoft degrades functionality of perpetually-licensed offline products

https://consumerrights.wiki/w/Microsoft_Office_2019_and_2021_for_Mac_view-only_conversion_(2026)
163•antipurist•1h ago•61 comments

Domain expertise has always been the real moat

https://www.brethorsting.com/blog/2026/05/domain-expertise-has-always-been-the-real-moat/
222•aaronbrethorst•4h ago•146 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
188•Hawzen•1d ago•56 comments

Accenture to acquire Ookla

https://newsroom.accenture.com/news/2026/accenture-to-acquire-ookla-to-strengthen-network-intelli...
231•Garbage•8h ago•117 comments

wolfSSL releases a new product; wolfCOSE a zero alloc C embbedded COSE stack

https://github.com/wolfSSL/wolfCOSE
53•aidangarske•4h ago•6 comments

Jef Raskin, the Visionary Behind the Mac (2013)

https://lowendmac.com/2013/jef-raskin-the-visionary-behind-the-mac/
62•tylerdane•4h ago•28 comments

Zig ELF Linker Improvements Devlog

https://ziglang.org/devlog/2026/#2026-05-30
161•kristoff_it•7h ago•42 comments

Voxel Space (2017)

https://s-macke.github.io/VoxelSpace/
246•davikr•10h ago•55 comments

Parallel Reconstruction of Lawful TLS Wiretapping

https://remyhax.xyz/posts/reproducing-lawful-tls-wiretapping/
50•jerrythegerbil•4h ago•25 comments

Shantell Sans

https://shantellsans.com/process
27•aleda145•2h ago•0 comments

OpenRouter raises $113M Series B

https://openrouter.ai/announcements/series-b
342•freeCandy•7h ago•164 comments

Show HN: 500 years of Joseon court omens as an observability dashboard

https://ajin.im/is/building/omen.ops/
71•poppypetalmask•5h ago•11 comments

Openrsync: An implementation of rsync, by the OpenBSD team

https://github.com/kristapsdz/openrsync
314•sph•13h ago•138 comments

Microcode inside the Intel 8087 floating-point chip: register exchange

https://www.righto.com/2026/05/microcode-inside-intel-8087-floating.html
82•pwg•7h ago•16 comments

Design Engineering Magazine

https://interfaces.dev/
44•hnhsh•3h ago•5 comments

Dusklight – GC Twilight Princess Decompiled

https://twilitrealm.dev/
53•shepherdjerred•4h ago•6 comments

Cheese Paper: a text editor specifically designed for writing

https://brie.gay/cheese-paper/
26•sohkamyung•1h ago•6 comments

Gustav Klimt and Egon Schiele in Conversation

https://www.theparisreview.org/blog/2018/01/31/the-drawings-of-klimt-and-schiele/
9•rballpug•2d ago•1 comments

Pandoc Templates

https://pandoc-templates.org/
357•ankitg12•14h ago•48 comments

Tsplat – Run Gaussian splatting in your terminal

https://github.com/darshanmakwana412/tsplat
24•martianvoid•2d ago•7 comments

Zig: Build System Reworked

https://ziglang.org/devlog/2026/#2026-05-26
317•tosh•16h ago•206 comments

Werner Herzog in conversation with Paul Cronin (2014)

https://fsgworkinprogress.com/2014/09/26/insignificant-bullets-evil-poachers-and-l-a-culture/
70•Michelangelo11•8h ago•24 comments

Navier-Stokes fluid simulation explained with Godot game engine

https://myzopotamia.dev/navier-stokes-fluid-simulation-explained-with-godot
177•myzek•4d ago•23 comments

90% of the T Distribution

https://entropicthoughts.com/ninety-percent-of-the-t-distribution
15•ibobev•3d ago•5 comments

It takes two neurons to ride a bicycle (2004)

https://fermatslibrary.com/s/it-takes-two-neurons-to-ride-a-bicycle#email-newsletter
95•malshe•4d ago•42 comments

Leo's first encyclical attacks technological messianism

https://www.economist.com/europe/2026/05/28/leos-first-encyclical-attacks-technological-messianism
171•1vuio0pswjnm7•14h ago•189 comments

Show HN: Open Envelope – an open schema for defining AI agent teams

https://openenvelope.org/docs/schema/
14•ashconway•2d ago•1 comments

IXI's autofocusing lenses are almost ready to replace multifocal glasses

https://www.engadget.com/wearables/ixis-autofocusing-lenses-multifocal-glasses-ces-2026-212608427...
159•amichail•3d ago•70 comments

Rotary GPU: Exploring Local Execution for Large MoE Models Under Limited VRAM

https://arxiv.org/abs/2605.29135
7•dryarzeg•3h ago•0 comments

What are locusts and what happened to them?

https://explosion-scratch.github.io/locusts/
217•explosion-s•4d ago•50 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?