social.colibri.beta.polyfill.beginMigration
Starts moving the requesting user's hosted repos to their PDS. Each repo enters the migrating state, in which the AppView still accepts its writes. Calling it again resumes an interrupted migration.
Details · procedure
| Kind | procedure |
|---|---|
| Authority | polyfill.beta.colibri.social |
| Commit rev | 3n2benzmpfd22 |
| Indexed |
Procedure
procedure · POSTInput
application/jsonOutput
application/jsonThe spaces whose repos still need to move.
Errors
AuthRequired
The request has no valid service auth.
InvalidRequest
The arguments are inconsistent or malformed beyond schema validation.
SpacesUnsupported
The user's PDS does not serve spaces yet.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
Asks the AppView to verify one repo the client copied to its PDS. The AppView syncs the repo from the PDS and compares it with its own copy. On a match the PDS becomes the source of truth. On a mismatch the repo stays hosted by the AppView, and the client may try again.
-
Reports where the requesting user's space repos live and whether their PDS can host spaces now. The client routes space reads and writes by the mode, and starts a migration when the mode is polyfill and the PDS supports spaces.
-
Pages through every record in the requesting user's hosted repo in one space, in record key order per collection, so the client can replay them on its PDS.
-
social.colibri.beta.community.migrate
procedureStarts moving a repo-backed community onto spaces and returns once the move is queued. Structure, roles, members and bans are recreated in spaces stamped with migratedFrom. Message history of current members is copied from their public repos and served alongside as read-only legacy messages. The move runs in the background and reports progress through social.colibri.beta.sync.defs#communityProgressEvent. Calling it again while it runs returns the current state, and calling it after a failed atte
-
Where a member's repos live. polyfill: the AppView hosts them because the member's PDS cannot. migrating: the client is copying them to the PDS, and the AppView stays authoritative until each copy verifies. native: the PDS hosts them and the AppView syncs from it.