Create legacy contact pages #21
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
deansaxe
added
documentation
|
Anyone know what triggers contacting the legacy contacts? It looks like the onus is on the legacy contact to know they are the contact and contact Apple. Looks like the contact needs a key you would share with them prior to death and a death certificate. |
|
That's correct, you have to share a key in advance. The contact has to manage the key over time and conduct the recovery. |
Added a doc for LinkedIn.
|
Added LinkedIn, Google Workspaces, 1Password |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As I add legacy contact pages for services I use, I'll document the processes and add a few to this PR before merging. Related to #18.
GitHub has been added.