Data Mobility
From The Socknet
This feature is still under review.
All data must be made mobile via a system to be described here.
It will be through the copy_profile function.
A backup service or new provider will call copy_profile with a callback url. The old provider will give a redirect.
The user will go to the redirect and approve the copy.
The callback function will receive a JSON structure describing the user, his friends, posts, services, etc. The new provider will send a redirect for the user.
The user will still be using the old provider until he changes his OpenID page to point to the new one.
New versions of the transfer specification MUST be published at the same time as new features. Every core feature that includes data must be present in the output of the data mobility document, unless it is not supported (yet) by the Socknet provider.
Considerations
There must be no way to run this function without user interaction. The data is just too sensitive.
Be careful with transferred spam reports. They could be fake.
It should be simple to enable this data to be downloaded to a file. So simple that it may become a UR too, in the future.
See Also
TODO
Describe system.
