Skip to content

Leaving or moving on

Contributors

There are two different exits, and they are not the same thing. Moving takes your account somewhere else and keeps it, with the same DID, posts and followers. Deleting ends the account and removes your repository from this server.

Because your identity is a DID rather than a hostname, moving servers is a first-class operation rather than an export. Your followers do not have to do anything and will not notice.

Mechanically it means creating the account on the new server, copying the repository and blobs across, then updating your DID’s record so it points at the new server. That last step is the one that needs proof it is really you, which is why a confirmation token gets emailed to you partway through.

The Move from Bluesky guide walks the same process in the other direction, and the tooling works both ways. If you are leaving Tophhie Social for somewhere else, the destination values change and nothing else does.

Deletion here is deliberately not instant, and deliberately not fully automatic at the point of request.

Deactivating an account starts a grace period of roughly 14 days. During it nothing is destroyed, and you can change your mind or export your data. After it, the repository is deleted from the server.

You are told at both ends:

When What happens
Day 1 An acknowledgement email confirming deactivation, stating the date deletion will happen
Around day 14 or 15 The repository is deleted, and a confirmation email is sent

The deletion itself runs from a scheduled job rather than being triggered by hand. See Automation and operations for how that works.

Your DID is not owned by Tophhie Social, so deleting your account here does not destroy it. What it does is leave the DID pointing at a server that no longer has your data. If you might want the identity later, move it instead of deleting it.

Start from your client’s account settings if it offers deactivation, or email help@tophhie.cloud.

Account deletion at Tophhie Social is reviewed and executed by a person rather than being fully automated on request. That is a deliberate choice, on the grounds that irreversible account destruction should not be something a bug or a bad actor can trigger unattended.

Whatever you are planning, having your own copy first is sensible. Your client may have its own export. Otherwise com.atproto.sync.getRepo against https://pds.tophhie.cloud returns your repository as a CAR file, though note that covers records only and blobs are separate. PDS MOOver offers a free automated backup service covering both your repository and your blobs, plus a restore path.