dev.cocore.app.registration

How an application announces itself to co/core so it can connect users' accounts with one click ("Sign in with co/core"). Published by the application on ITS OWN account (a did:plc or did:web with a repo), one record per DID at rkey `self` — there is no central app registry. When the app calls `dev.cocore.devicePair.start` with `appDid`, the AppView reads this record from the app's PDS: `name` is what the approve screen shows, and `returnUrls` are the only places the approve screen may send the browser afterwards. A return URL is additionally honoured only when its host proves it belongs to this DID by serving `https://<host>/.well-known/cocore-app.json` containing `{"did": "<this DID>"}` — so a record on a stranger's account cannot borrow a real app's domain.

Repository @cocore.dev did:plc:5quuhkmwe2q4k3azfsgg7kdz not from the namespace authority
Details · record, key literal:self
Kindrecord
Record keyliteral:self
Authorityapp.cocore.dev
Indexed
Records · 7 days
0

Records per day

last 7 days
  1. 0
  2. 0
  3. 0
  4. 0
  5. 0
  6. 0
  7. 0

Field presence

share of records · last 7 days

No field data for the last seven complete days yet. Field presence is counted per UTC day, and a day shows here once it's over.