Path

Everything shipped, and the day it shipped.

Every technical and product decision behind Milo, in the open, as it gets made. What shipped and the tradeoff it carried, what is being worked on now, and what is only an intention. Dated honestly, including the quiet weeks.

Not shipped yet

no dates promised
  • Wanted, unscheduled

    Link controls

    One link per application, and UTM presets so a candidate can tell LinkedIn from a referral without hand-editing query strings.

    • Product
Things shipped
17
Days with a release
12
Days since the first
84
  1. 31 October 2026

    2 releases
    • Shipped

      The account-wide activity log says which resume, and shows the whole event

      The /logs page lists events across every resume someone tracks, but each row just said "Page 1 viewed" with nothing identifying which one. ActivityLog now takes an optional linkTitleFor resolver, passed only by AccountLogs, since the per-link logs page is already scoped to one resume and doesn't need it. The row also surfaces every signal an event actually carries instead of a subset: utm_medium and utm_campaign were captured but never shown anywhere, and the relative timestamp ("2h ago") gets the exact time as a hover title. A raw session id was briefly shown here too and removed, not useful to a resume owner and an identifier with no reason to be on screen. Separately, an old event with no page_number, captured before this session's PDF-viewer rework added real page tracking, used to render literally "Page ? viewed"; it now reads "Resume viewed".

      • Frontend
      • Analytics
    • Shipped

      Forgot your password, without a way to probe who has an account

      POST /auth/forgot-password and POST /auth/reset-password reuse the registration flow's OTP mechanics, a hashed code, an attempt limit, a TTL-expiring record, but in their own password_resets collection, so a pending email verification and a pending password reset for the same user never collide on one row. forgot-password is written to be the one auth endpoint whose response never varies: no email echo, no timers, 200 whether or not the address has an account, whether it's verified, or whether an email actually went out, deliberately stricter than /auth/verify-email/status, which does leak known-vs-unknown and was an accepted gap for the less sensitive registration flow. reset-password follows the same rule, collapsing an unknown email, no pending reset, an expired code, and a wrong code into one password_reset_invalid rather than a response that would let the endpoint be used to test which emails have accounts. The frontend adds a two-step /forgot-password page and a show/hide toggle on every password field, shared by login and register.

      • Backend
      • Auth
      • Security
  2. 30 October 2026

    2 releases
    • Shipped

      The resume viewer renders its own PDF, instead of trusting the browser's

      The /l/:slug page handed the fetched PDF straight to the browser's native viewer, an iframe pointed at the raw bytes. That viewer ships its own download/print controls, which save whatever's already loaded in the viewport without ever hitting /l/{slug}?download=true, so a click there was never counted as a tracked download event. Replaced by a canvas renderer built on pdfjs-dist: no native browser chrome, so Milo's own Download button (already wired to the tracked endpoint) is the only way to save the file. Page navigation and zoom are new controls this needed, and the dwell beacon now reports the page actually open instead of a hardcoded 1, the per-page tracking this feature always lacked for want of an in-browser renderer. A canvas has no DOM, so a link baked into the PDF (LinkedIn, GitHub, mailto:) isn't clickable on its own the way it was in a native viewer; restored by overlaying a transparent <a> per Link annotation, positioned from pdf.js's own annotation rects.

      • Frontend
      • PDF
    • Shipped

      Resume URLs get checked for a real PDF, not just a safe address

      Creating or editing a resume ran the URL through the SSRF guard and stopped there; it never fetched the thing, so a Google Drive /view page or a login wall was accepted at submission and only failed later, for whoever opened a tracking link. Both POST /resumes and PATCH /resumes/{id} now fetch the URL and run the same check the tracking-link resolver already applied: the body's own %PDF magic bytes are required, never a declared Content-Type alone, since a host claiming application/pdf while actually serving HTML with an inline script tag is exactly the stored-XSS path this closes. (Some hosts, Google Drive's own direct-download endpoint among them, serve a real PDF as application/octet-stream; that's accepted only together with the magic bytes, never on the declared type by itself.) A Google Drive share link in the exact form Drive's own Share button produces is also rewritten to its direct-download form before validation, so a candidate doesn't have to hand-edit it. Separately, the share_url returned from POST /resumes/{id}/links was built from the API's own origin, so a copied tracking link opened the raw PDF in the browser's native viewer instead of Milo's page with its tracked download button; that's now a dedicated FRONTEND_PUBLIC_BASE_URL setting, split from the API's own origin.

      • Backend
      • Security
  3. 28 October 2026

    1 release
    • Shipped

      A real download button, and a warning before an edit touches more than one link

      The resume viewer gets a visible download button next to the inline view, pointing at the same /l/:slug route with ?download=true, which the backend already turned into a Content-Disposition: attachment response and a DOWNLOAD event instead of a VIEW one. The viewer also now reports device category, browser and OS on that same request, the three allowed signals that had a backend column but nothing sending them from this page. On the settings side, editing a resume's title or URL now shows a notice when other tracking links share that resume, since the row is shared and the edit would otherwise silently change every sibling link with no warning; the raw, truncated resume URL is also replaced with an "Open resume" button.

      • Frontend
      • Analytics
  4. 27 October 2026

    1 release
    • Shipped

      Dashboards gain device, browser, trend, and top-link panels

      Three panels on top of data the backend already recorded but no page ever showed. Device/browser/OS breakdowns reuse a new shared bar-list component (the same one traffic sources already used, now de-duplicated into one place), since those three fields have been on every analytics event since the first version of this feature and had zero UI consumers until now. A 14-day daily views chart is the first time-based view anywhere in the product; every other panel before this only ever showed one running total. The account dashboard also gets a top-links ranking, sorting every link an owner has by view count, which is the actual answer to "which application is getting looked at" instead of one combined number across all of them. All three are frontend-only reads against the existing /events and /links APIs, no schema change, no new signal beyond what root CLAUDE.md already allows. 9 new Vitest tests.

      • Frontend
      • Analytics
  5. 26 October 2026

    1 release
    • Shipped

      Tracking links get a real backend, end to end

      The links, dashboard and logs pages now talk to an actual FastAPI service instead of the stand-in store. Creating a resume runs its URL through an SSRF guard that resolves the host and rejects anything private, loopback or link-local before the address is ever persisted; creating a link mints a random slug via secrets.token_urlsafe rather than one a user picks. Opening a share link checks expiry and revocation before touching the network at all, then fetches the external PDF with a linear-backoff retry on transient 5xx and transport errors (a 4xx or an oversized body fails immediately instead of retrying a wrong answer three times) and streams the bytes back while recording one view or download event. A dwell-time beacon, sent via navigator.sendBeacon from a new public resume-viewer page as the tab hides or unloads, closes the one allowed analytics signal that had no route yet; it's whole-document time for now, not per-PDF-page, since there's no pdf.js. Editing stays narrow on purpose: a resume's title and URL, a link's expiry, nothing else. Revoking is enforced as permanent at the database query level, there is no un-revoke. 31 backend and 16 frontend unit tests back this, the first automated test coverage this codebase has had.

      • Backend
      • FastAPI
      • Security
      • Testing
  6. 17 October 2026

    1 release
    • Shipped

      A resume card that reads itself, on both marketing sites

      Decorative, not data: a CSS-only mockup sits in each hero, each site rendering its own take so the two brand treatments stay distinct, landing's tilted with a looping "Viewed" badge, the product app's upright with a line that scans down the page. Every row is an abstract bar, never invented resume text, and the whole thing is aria-hidden since the headline already carries the meaning. No Three.js: each page already runs one WebGL canvas elsewhere and the house rule is one per page. A global prefers-reduced-motion rule already collapses every animation duration to near-zero, so neither card needed its own escape hatch to stay still for a visitor who's asked for that.

      • Frontend
      • Marketing
      • CSS
      • Accessibility
  7. 16 October 2026

    1 release
    • Shipped

      Tracking links, working end to end against a stand-in store

      The links, dashboard and logs pages stop being empty states: create a link, see it on the account-wide and per-link dashboards, edit it, delete it with a confirm step that also drops its events. A Zustand store holds the links and their view/download events in memory, seeded with a couple of examples, and a small set of pure functions turns raw events into the numbers the UI shows (views, unique viewers by session id, download rate, traffic sources, per-page dwell time), the same shape the real backend would eventually return, so swapping in the actual Link API later was a matter of replacing the store, not the pages. (That swap shipped 2026-10-26.)

      • Frontend
      • Zustand
      • Analytics
  8. 15 October 2026

    1 release
    • Shipped

      The product app now actually logs you in

      Register and login call the real backend instead of sitting next to it unused. A Zustand store holds the session as plain client state; a TanStack Query check against /auth/me mirrors into it once at the root, and PrivateProvider/GuestOnlyProvider read that same flag to redirect a signed-out visitor out of the dashboard, never rendering it for a frame, and a signed-in one out of the login page. The verification screen the register flow already expected now exists at /verify: it resolves live against /auth/verify-email/status on every mount, including a hard refresh, and only sends a fresh code when nothing is already pending, so the resend cooldown survives a refresh instead of resetting and a refresh never fires a duplicate email. That same resolve step also closed a bug where an already-verified email used to fall through into sending another code and hit the backend's own already-verified error.

      • Frontend
      • Auth
      • React Query
      • Zustand
  9. 15 September 2026

    2 releases
    • Shipped

      Accounts, and a signup that proves you own the address

      Register, verify by one-time code, login, refresh, logout and a current-user endpoint, layered routes to service to dao so the rules stay testable with no database and no running app. Codes are HMAC hashed with a server-side pepper before they reach Mongo, and the row keeps only a user id: an email copy and a stored expiry are both facts the users collection already owns, so expiry is derived from last sent, which is the same field the TTL index deletes on. Tokens carry a type claim that decoding checks, so a refresh token cannot be replayed as an access token, and they only ever travel in httpOnly cookies. Passwords are argon2id and deliberately never trimmed, since trimming one silently changes the credential someone typed.

      • Auth
      • FastAPI
      • MongoDB
      • Security
    • Shipped

      Mail that refuses to fail quietly

      SMTP delivery derives from the environment: console in development, where the whole message lands in the log so signup works with no mail server, and real delivery in production, which refuses to start on console mode, a local mail catcher host, missing TLS, absent credentials, or a missing code pepper. That last check is not cosmetic, without a shared pepper every worker hashes codes differently and verification fails at random. Rate limiting surfaced its own trap: with headers enabled a limited route must also accept the response object, or it raises on the first request rather than at import.

      • Email
      • Configuration
      • Reliability
  10. 13 August 2026

    2 releases
    • Shipped

      Product app, and the design system underneath it

      Marketing shell for the app, with a story section where one beat index drives the copy feed, the figure pose and a WebGL backdrop of 54 cards rendered as a single InstancedMesh. Tokens and shared components moved into their own packages so both apps render from one source; Tailwind v4 needs explicit source globs to scan a linked package, verified against the built CSS rather than assumed.

      • React
      • Three.js
      • Design system
      • Monorepo
    • Shipped

      Polyglot monorepo with a single task runner

      npm workspaces for TypeScript, Poetry for the FastAPI service, and a Makefile so one command lints both languages. CI splits into parallel JavaScript and Python jobs. Prettier is fenced out of the Python package, proven by dropping an identical malformed file into each and checking only one was flagged.

      • Infrastructure
      • CI
      • Python
  11. 12 August 2026

    1 release
    • Shipped

      Source-available licensing, notices generated not guessed

      Elastic License 2.0, diffed byte for byte against two official Elastic repositories rather than reproduced from memory. Third-party notices built from each dependency own license file, which surfaced that lucide-react carries ISC terms plus a separate MIT notice for Feather-derived code.

      • Licensing
      • Compliance
  12. 9 August 2026

    2 releases
    • Shipped

      Waitlist API, and a Mongo client that survives a cold start

      Zod validation at the boundary, rate limiting, and a honeypot that returns success so bots learn nothing. Duplicates are rejected by a unique index rather than a read-then-write check that would race. One cached client per serverless instance, and a rejected connect promise clears itself, since a memoised rejection makes a warm instance fail forever after the cluster is fixed.

      • API
      • MongoDB
      • Security
      • Reliability
    • Shipped

      Landing page, and privacy enforced in the schema

      A scroll-driven WebGL story in five acts. Progress lives in a ref, not state, so the canvas runs at 60fps while React re-renders about five times across the section, and it degrades to a static composition under reduced-motion or without WebGL. There is no identity field to switch on later: IPs are hashed with a rotating salt for rate limiting only, and Permissions-Policy denies camera, microphone and geolocation at the HTTP layer.

      • Three.js
      • Performance
      • Privacy
      • Accessibility