Follow-me / Link in bio page
README.md

jeremy.herve.bzh — my follow-me-everywhere page #

When I wanted to point people to my identity on the AT Protocol, I used to link to my Bluesky profile. It works, but atproto isn't just Bluesky, and bsky.app isn't really mine. So I built this: a small page on my own domain where you can find me across the open social web, follow me where you already are, and poke at my atproto data if you're curious.

It's live at jeremy.herve.bzh, and it's styled like an old 8-bit game, because why not 😃

What it does #

It has three tabs:

  • Links — one card per place you can follow me: RSS, the Fediverse, ATProto, GitHub, WordPress, Tangled, Sifa. Each card has its own action.
    • The ATProto card signs you in with your own atproto account (real OAuth) and creates the follow for you, right there on the page.
    • The Fediverse card hands you my @jeremy@herve.bzh address to copy and paste into your own instance; there's no single follow URL for the Fediverse, so a copy button is the honest way to do it.
    • The rest are plain links out.
  • Posts — my blog posts, read straight from my PDS (the site.standard.document records that back herve.bzh), each linking back to the full post.
  • ATProto records — a little pdsls-style browser for every collection in my repo, in case you want to see what's actually stored on my PDS.

How it's built #

Plain HTML, vanilla JS modules, and CSS; no framework. The only real dependency is the atproto SDK, bundled with esbuild, and the whole thing runs as an assets-only Cloudflare Worker.

  • @atproto/oauth-client-browser handles the sign-in-and-follow flow. It's a public OAuth client with no secret, so the page can stay fully static.
  • @atproto/api creates the follow record.
  • The Posts and ATProto records tabs use public, unauthenticated atproto XRPC, so no login is needed just to read.

One note on the OAuth scope: following someone means writing a record to your repo, and the scope atproto can grant for that today (transition:generic) is broad. The page says so plainly, and the only thing it ever writes is a single follow record.

Running it locally #

  1. npm install
  2. npm run dev (builds the bundle and starts wrangler dev)
  3. Open http://127.0.0.1:8787/

Use 127.0.0.1, not localhost: atproto's loopback OAuth client requires the IP address, so signing in won't work on localhost.

Other commands:

  • npm test runs the Vitest unit tests.
  • npm run build just builds the bundle.
  • npm run deploy builds and deploys to Cloudflare (the jeremy.herve.bzh custom-domain route is already in wrangler.toml).

Project layout #

public/                 static site served by the Worker
  index.html            the three views in one document
  styles.css            the 8-bit theme
  client-metadata.json  atproto OAuth client metadata (public by design)
  jeremy-herve.svg      the portrait
  icons/  fonts/
src/
  config.js             identity + the list of channel cards (start here)
  app.js                routing and wiring
  cards.js              the Links cards + modals
  modal.js              the little modal helper
  follow-ui.js          the atproto follow widget
  oauth.js              atproto OAuth + follow/unfollow
  records.js            public-XRPC resolution and record listing
  records-ui.js         the ATProto records browser
  posts-ui.js           the Posts list
test/                   Vitest unit tests

Making it your own #

Most of what you'd change lives in src/config.js: your handle, your DID, your blog URL, and the list of cards. Swap the portrait in public/jeremy-herve.svg, point public/client-metadata.json and the route in wrangler.toml at your own domain, and deploy. Feel free to take it and run with it 😃

Credits #

The fonts in public/fonts/ are Overused Grotesk and IBM Plex Mono, both freely licensed for use and redistribution.