Skip to content
Plugins
House

Devlog

Capture sessions, DSP notes, measurement walkthroughs. The receipt that backs every claim. No marketing fluff — engineer-to-engineer notes from the workbench.

  • 2026-05-03 · Pre-launch · Build 1+2

    Sign-in, keygen, and what runs between an email and a license key

    Plumbing day. The storefront has been live for a week, but the path from someone reading the page to someone holding a license key was missing rails. Today we put them in. Magic-link sign-in — built on Supabase Auth, but routed through our own Postmark pipeline so the emails come from support@me-plugins.com, not a generic noreply, and aren’t subject to a third party’s 2-per-hour cap. A license key utility: MNTSH-XXXX-XXXX-XXXX-XXXX-CCCC, 80 bits of entropy plus a 16-bit CRC-16/CCITT checksum so a typo’d key fails the format gate before any network round-trip. An admin surface at /admin/licenses for minting beta / NFR / press / replacement keys, one at a time or batches up to 50. A user-side view at /account/licenseswhere the recipient signs in and sees the key in a mono code box, machines used, source label, expiry. End-to-end round-trip verified: generate a key in the dashboard, branded email lands, recipient clicks through, key appears on their account — about 30 seconds.

    None of this is the plugin yet. ME-TUEY v1.0 is still in capture and DSP work. What we built today is the storefront’s wiring: every connection from an inbound email address to a license key is now in place, but the keys aren’t yet checkedby anything except the database. Build 3 — the activation server (Ed25519-signed tokens, 90-day TTL, weekly heartbeat revocation checks, machine-fingerprint binding) — lands when the binary is ready for beta drops. Before then: keys exist, are tracked, can be revoked. After then: they actually gate the plugin loading. Same database row, same recipient experience — just a new layer of signature verification in between.

  • 2026-04-30 · Before v1.0

    What this devlog is — and what it isn't

    The devlog is the workbench notebook. Capture sessions, DSP design decisions, measurement walkthroughs, the small calls (which channel do we sample? why 96 kHz and not 192?) and the larger ones (do we model the saturation of the output transformer or just its frequency response?).

    What it isn’t: marketing. There’s no narrative arc, no “founder’s journey”, no metaphors. If the number isn’t in the post, the post doesn’t ship.

    When v1.0 lands, the first real entry is a full capture-session walkthrough: the unit on the bench, the chain (DI → tube DI → patchbay → unit → patchbay → A/D), the level-matching procedure, the deconvolution math, and the residual plots. The receipt becomes the post.

    Want it in your inbox? Subscribe to the devlog — third checkbox on the reservation form. Same content, push not pull, no marketing.

First ME-TUEY v1.0 capture-session entry ships with the plugin.