Skip to content

Tags

Tags

v0.2.0

Toggle v0.2.0's commit message
0.2.0: niches may be a function

A site's niche vocabulary lives in its database, and an array frozen at import
means a collection added today cannot be claimed today. A function is resolved
per request instead.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0144uEVbZK3jdaQkwcLYTXPE

v0.1.0

Toggle v0.1.0's commit message
Partners 0.1.0: signup, domain verification, niches, rate, payout, ea…

…rnings

The seller side of a dataset, as one Fetch-API handler mounted on the host's
own auth. It never sees a password and owns no login: it asks currentUser()
who is here and sends everyone else to loginUrl, which is what lets it drop
onto a site whose accounts already exist.

Verification is the load-bearing part, since a rate and a payout address hang
off it. Two automated methods, no manual path: a DNS TXT record read over
DNS-over-HTTPS through fetch (so it runs at the edge and needs no resolver),
or one file under /.well-known. The token is an HMAC of the domain under a
required secret, so it is stable across visits and unguessable without it. An
absent secret throws rather than defaulting, because a guessable token pays
the wrong person for someone else's work.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0144uEVbZK3jdaQkwcLYTXPE