When a change can’t be undone
PLC Keeper sends you here when it can’t reverse a change to your identity: the 72 hours to undo it have passed, or the change was made by a key ranked above every key you hold. Here’s what you can still do.
If the 72 hours haven’t passed
A change can still be undone by anyone holding a key ranked above the one that made it. When none of your keys rank that high, the key that does is often your PDS operator’s. Contact your PDS operator now, tell them the change wasn’t yours, and give them the time it was made. PLC Keeper shows that time, and the deadline, on the change.
If one of your keys is still listed
Once the 72 hours have passed, the change itself stays in your identity’s history. But any key listed in your identity’s current recovery keys can still sign a new change. If the unwanted change left one of your keys in place, use it to put your PDS back and remove the keys you don’t recognize.
Talk to your PDS operator
Your PDS operator hosts your account and its data. Tell them what happened. They may be able to lock the account, confirm what was changed and when, and help you move your posts and follows. Change your account password, and secure the email account your confirmation codes go to.
If you own your handle’s domain
A domain handle, such as riley.example.com, belongs to whoever controls the domain. Remove or change its _atproto DNS record, or its /.well-known/atproto-did file, so the handle stops pointing at the identity you lost. People then stop seeing that identity under your name.
Starting again
If the identity can’t be recovered, create a new account, point your domain handle at it, and tell the people who follow you where you’ve gone. Add your own recovery keys to the new identity from the start, ranked above your PDS, so a change you didn’t make can be undone next time.
Get help
Write to hello@plckeeper.app or message @plckeeper.app on Bluesky, and we’ll help you work out what’s possible. We’ll never ask for your password, your confirmation codes or your keys.