Personal Data Import/Export
[Edited by Fla]
This discussion is about account migration between pods.
Current github issue
Summary: We all agree this is an important feature, but it's hard to deal with considering privacy and security issues.
Tom Scott started a proposal Thu 10 Jan 2013
Abandon the feature? Closed Thu 10 Jan 2013
We're not abandoning this feature. :)
We could always abandon this feature. If we do, it means clearing that advert text on diasporaproject, letting people know in the GH Issue that it's not gonna happen in the near future, and closing it out.
I don't necessarily want to do this, but I figured this is the best time to bring up abandoning an issue, as no work has been done yet.
|Agree - 0|
|Abstain - 0|
|Disagree - 0|
|Block - 0|
Thu 10 Jan 2013
Our users have the rights to the content they post on DIASPORA. Therefore, I think we should press on with this feature as long as we can get it done quickly and without any security issues. Those are my main two concerns.
Thu 10 Jan 2013
This is one of the most important features missing. Without the ability to migrate to another pod (be it a full wizard or manual export/import with limited dataset) - Diaspora* is just a collection of separate pods, not a proper network.
Thu 10 Jan 2013
This feature is absolutely one of THE key elements of the Diaspora concept of privacy and user ownership of their own data. Without it, Diaspora will not be the network it was set up to be.
However long it takes, it must be implemented eventually.
Tom Scott started a proposal Fri 11 Jan 2013
Export pod data to an archive Closed Sun 13 Jan 2013
The first step to this whole project is exporting a person's entire persisted history to an archive. Without this key ingredient, there's no point in coding pod-to-pod communications. In order to maintain the philosophy that you should not only be in control of, but own the data you post to DIASPORA, it will be an option to download the archive from your pod. Pods will only retain archives for 4 hours, after which they will be purged.
|Agree - 2|
|Abstain - 2|
|Disagree - 2|
|Block - 2|
Fri 11 Jan 2013
I don't quite see the benefits without upload, with upload this would be too insecure as it's written in this proposal. If we really do this I want a wiki page explaining why there's no upload, that I can direct the shitstorm to.
Sat 12 Jan 2013
I'm abstaining as I agree there should be the possibility to export an entire account, but not without a corresponding ability to import that entire account into a new pod. As Jonne says, without upload/import, there's no benefit to download/export.
Tom Scott started a proposal Tue 22 Jan 2013
Import pod data from the Export archive Closed Fri 25 Jan 2013
Only registered users can do this off of their Account page. At this time, we will require migrating users to register on the new pod, export their data off the old pod, and then import it onto the new one. The data import feature will be simple, and basically just read in the JSON and photos to the new user's account.
You literally just upload JSON (or however we're storing it) and photos, and we take care of the rest.
|Agree - 6|
|Abstain - 6|
|Disagree - 6|
|Block - 6|
Tue 22 Jan 2013
This is a simple and elegant solution to the data import problem. Pod-to-pod communication will take too long, and we can't really decide on a good way to do it, so I propose we get this code out there in the short term and stop worrying about it.
goob started a proposal Sun 9 Jun 2013
Create manual export/import as short-term measure Closed Mon 1 Jul 2013
There's agreement in principle for a short-term manual solution. Now to work out how this can be implemented, and if there's a way to do it which will require less effort than the full solution.
Just to get things moving, I propose that we implement a manual two-step export/import process while deciding on the best method for implementing automated pod migration in the future.
The user is responsible for the security of their data (and those of their contacts) during the export/import process. They download their account data in toto, including contact information, to a local source (hard drive etc), then separately upload this account information to a new pod.
The exact method of doing this can be agreed if the proposal is passed in principle.
This is just a measure to allow account migration in the short term.
|Agree - 16|
|Abstain - 16|
|Disagree - 16|
|Block - 16|
Sun 9 Jun 2013
There is an export feature - but it is broken. I doubt anyone will object if it is rewritten.
The upload should be for contacts (automated add-to-aspects, tags (to follow) and some stuff like profile details. I don't see how posts could b imported