#status

Progress and Cons

Epistemic status: Reflections on ProgressCon 2026, written up over the following weeks. Quotes are reconstructed from memory. Artistic license taken. For in much wisdom is much grief: and he that increaseth knowledge increaseth sorrow . – Ecclesiastes 1:18 “I’m sure you’ve all heard about the math stuff that OpenAI released earlier this week.” It is Thursday, October 8, 2026, and the CEO of a bio lab automation startup is giving us a tour of their San Francisco office. “Raise your hand if you think that’s a good thing.” A dozen hands shoot up out of thirty visitors. Along with ten more, my arm

LessWrong · EN

Status update 2026-08

I’ve been refining the API for libdav . Two big tasks were involved here: (1) more flexible generic types for the async helpers and (2) tidying up error types. Flexible async types [ permalink ] The core of libdav follows a sans I/O philosophy: it produces requests and parses response, leaving network transport up to the caller. This kind of design is clean, flexible, and especially convenient for unit testing. Not to mention that it makes the library actually usable with any HTTP client implementation. For typical consumers writing async Rust code with the hyper HTTP library, writing co

Hugo's weblog on WhyNotHugo (雨果) · EN

Status update 2026-10

I’ve completed development work on OAuth support in pimsync. The implementation has been tested primary with NextCloud (both its built-in OAuth provider and the OIDC plugin), but should be usable with any CalDAV/CardDAV server using OAuth for authentication. It should also work with Google’s flavour of CalDAV, although this has yet to be tested. At this point, mostly the documentation is missing — the reference-level documentation is there, but a friendlier “how to” guide covering all the details is still pending. It’s both definitely planned and quite necessary.

Hugo's weblog on WhyNotHugo (雨果) · EN