fyi.opensocial.checkImport

What moving an account here would make of it, before anything moves (importAccount moves it so): its handle here, whether that's the one it has, and its address, this host's own name for it. A handle on a domain of the account's own that still names it comes along; one its old server gives out becomes the address. `refused` says why it can't have that address, as importAccount would. While the caller's own move of it is pending, `recommendedCreds` says again what the operation should name, as importAccount did.

Details · query
Kindquery
Authorityopensocial.fyi
Indexed

Query

query · GET

Parameters

query string

address

string

The label of its address here, if not its handle's first label.

did

requiredstring · did

Output

application/json

address

requiredstring

Its address here: one label under this host's handle domain.

did

requiredstring · did

from

string

The handle it has now.

handle

requiredstring · handle

Its handle once moved.

keeps

requiredboolean

Whether that's the handle it has now.

label

requiredstring

pds

string · uri

The server it lives on now, as its DID document names it.

While the caller's own move of it is pending: rotationKeys, alsoKnownAs, verificationMethods and services, as importAccount answered, for the account's server to sign (com.atproto.identity.signPlcOperation).

refused

unknown

{error, message}: InvalidHandle or HandleNotAvailable.

Errors

NotPlc

No description in schema.

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • Start moving an account that already exists on the network, on any server, here to become a group: check the account's proof that it hands its DID to this host, make it here switched off with new keys, and copy its whole repo and its files from its server. Answers with the credentials the account's PLC operation should name; once its server has signed one, completeImport finishes the move. The caller becomes the group's admin. Only a did:plc account, and never the caller's own. Starting again fo

  • Start moving the account the caller signed in to move (getAccountMove) here, to become a group they run: the host asks its server for its token for this host, copies it as importAccount does, brings its spaces as importAccountSpace takes them, and asks its server to email the code that lets its identity move (finishAccountMove). Started again, it starts over.

  • Finish moving an account here: send the PLC operation its old server signed, which must give it to this host as importAccount said, switch it on and tell the network, and make the group's spaces with the caller as its admin. Only for whoever started the move.

  • The account the caller signed in to move here from the console (/console/move/login), if any: the host keeps its tokens at its server for them until the move is finished or cancelled, for a day at most. Empty when there is none.

  • Finish moving the account the caller signed in to move: with the code its server emailed, the host has its server sign the operation that gives its identity to this host, then finishes as completeImport does, and gives its tokens back.