The captcha every form shares: the CaptchaService interface its providers implement, the forms it protects and their checks, wired once
An image captcha the product draws itself, with digits read out for whoever cannot see it, no keys and no third party, as the provider of captcha
Cloudflare Turnstile as the provider of captcha, which asks it for the answers of the forms it protects
Sign-in provider accounts (ORCID, GitHub…) linked to users, and the one OAuth flow every provider registers on (register_oauth_provider): sign-in, connect, and new accounts through /account/complete-signup, a typed address opening one only through a mailed link. With the identities page, disconnecting, the rule that keeps a product without signup closed, and an optional hint on the login page
Publishing on the hub itself, under an identifier of its own (no DOI), the dataset's public id, with its landing at dataset's /records/<public_id>: the publication provider of a hub without Zenodo
Google reCAPTCHA v2 as the provider of captcha, which asks it for the answers of the forms it protects
Zenodo as a publication provider of dataset: deposits a hub's datasets and gets their DOIs (the sandbox outside production)