Follow-up to #1137.
It has recently been announced that one can now migrate a Bridgy-hosted AT repo to another PDS. But the real point of “credible exit” is that you could migrate out of a PDS at any time even if your host is adversary (not that I don’t trust you :), and for that to work, the user must be in control of the DID before they actually need to migrate out.
IIUC, this is technically possible with the recent introduction of the migration feature, by migrating out of Bridgy’s PDS, making a PLC op to add a rotation key, and then Bouncing back to Bridgy, but the migration step is essentially a pure overhead. So it would be great if Bridgy just lets the user add a rotation key without the need for the migration.
Follow-up to #1137.
It has recently been announced that one can now migrate a Bridgy-hosted AT repo to another PDS. But the real point of “credible exit” is that you could migrate out of a PDS at any time even if your host is adversary (not that I don’t trust you :), and for that to work, the user must be in control of the DID before they actually need to migrate out.
IIUC, this is technically possible with the recent introduction of the migration feature, by migrating out of Bridgy’s PDS, making a PLC op to add a rotation key, and then Bouncing back to Bridgy, but the migration step is essentially a pure overhead. So it would be great if Bridgy just lets the user add a rotation key without the need for the migration.