A live protocol demo

One app.
Any OAuth server.

These connections did not require visiting a developer portal, creating an app by hand, or pasting in a client ID. The app introduces itself at runtime.

\n${error ? `

${esc(error)}

` : \"\"}\n

Val Town

RFC 7591 DCR

Val Town dynamically creates this app’s OAuth client when the first person connects.

\n ${valConnected ? `

@${esc(valConnected.username)}Authenticated API response

username${esc(valConnected.username)}

user_id${esc(valConnected.id || valConnected.userId || \"authenticated\")}

` : `Connect Val Town`}\n

Mastodon

DYNAMIC APP REGISTRATION

Choose any Mastodon server. This val registers itself there, then reads your public profile with the token you approve.

\n ${mastodon ? `

${esc(mastodon.profile.display_name || \"@\" + mastodon.profile.acct)}Authenticated API response

account@${esc(mastodon.profile.acct)}

server${esc(new URL(mastodon.instance).host)}

followers${esc(mastodon.profile.followers_count)}

posts${esc(mastodon.profile.statuses_count)}

` : ``}\n

This is the n² collapse: the app and provider agree on a protocol, so they do not need a prearranged relationship. Mastodon’s endpoint predates RFC 7591 but demonstrates the same runtime-registration primitive. View the val.

One app.Any OAuth server.

Val Town

Mastodon

One app.
Any OAuth server.

Diff · v12