Shipping small things (,,

from 2024-05-17

As the design for awaits reviews, I found myself with a fair bit of time and infrastructure readily available. This gave me the unique opportunity of putting small non-commercial services together quickly. sign up to store

The idea is simple: no sign up, no account, anybody can maintain a 64KiB chunk of data by associating it to a public key.

As the updates must be signed using the corresponding private key, something verified by both the infrastructure and serious clients, only people with the private key can update it, and only people with the private key and maintainers of the service can delete it.

To make it easy and lightweight on web clients without trusting NIST curves, we adopted TweetNaCl.js's cryptography.

To support arbitrary chunks of data without going through base64 or the like, the protocol is based on CBOR rather than JSON or HTTP paths.

To avoid ever logging public keys, reads pass the key being looked up in a POST body. Don't disclose the public key and only maintainers of the service know where to get your data.

Encrypt your data and nobody can. Which leads me to the first app using this service, — password → page

Again, the idea is simple: no sign up, no account, anybody can associate up to 64KB of text by associating it to a password.

Of course, it leverages to store the encrypted data. was built for it, really. And it was built, as the name might suggest, to store my 1password secret key so I can recover it on the go, even if I lose all my devices.

The password is used to derive the private key used for's signature, the one needed to deecrypt the data. This derivation uses 100,000 rounds of SHA-256 PBKDF2 with a static salt.

There really isn't much more to it, adding up to only 219 lines of Preact within 30KiB compressed of an open source website whose build is reproducible thanks to the Vite ecosystem. names anything

Feeling inspired by the simplicity of, quick editing experience of, speedy service of, I put together a service to associate a redirection, webpage, or (later) arbitrary file under 1MB to a URL:

Pick a path, pick a password, see what's there if anything, choose what should be there, whether it be a redirect, hand-written HTML, markdown, or an arbitrary file, hit a button, observe the result in a new tab, then share at will, knowing you can come back and edit it later.

It reuses the key derivation from, but this time the salt depends on the path being edited, guaranteeing that the same strong password can be used for multiple paths without correlation in our store. Unlike, the data is never encrypted as the purpose is to publish.

Support for markdown with YAML metadata is implemented entirely in browser allowing for live previews, which combined with cbor-x, TweetNaCl.js, and Preact, puts the admin UI just under 60 KB compressed; of course, the generated resources are served without any overhead.

Eat what you cook

When I wrote about migrating to, I missed an opportunity to touch on this topic. There's nothing like building for your own needs, and there's nothing like using what you build.

Publishing' landing page through its admin UI was a mind-altering moment. I figured I should support uploading files too, so I could ship favicon.ico, the site-wide default icon, without a backend rule for it.

One day, I might need my 1password secret key urgently, without access to any of my devices. I look forward to it.

And of course, all those services use They get the exclusive privilege of exposing APIs through it, something I hope to allow through proxying and a serverless runtime at one point or another. I'll be sure to (re-)build with those.