solid-spec icon indicating copy to clipboard operation
solid-spec copied to clipboard

How to transfer data between POD?

Open linonetwo opened this issue 7 years ago • 5 comments

It's said that "you’re free to move it at any time". If one POD is stopping its service, how can user transfer data between the previous POD and next POD easily?

Or make a backup.

Another question is: If you change a POD, will you change your WebID?

linonetwo avatar Oct 14 '18 13:10 linonetwo

Seems by entering "External WebID:" when register, you can move your data.

linonetwo avatar Oct 14 '18 14:10 linonetwo

@linonetwo Interesting question, and actually External WebID is not the full solution. That option is useful for when you have an existing WebID you want to reuse, but not for moving data.

So let me reopen your issue.

RubenVerborgh avatar Oct 15 '18 08:10 RubenVerborgh

This is a good one for the FAQ.

There's three aspects

  • moving the data (this can be done technically)
  • moving the internal links (this can be done technically using relative URIs)
  • moving the external inbound links, that is a more difficult process, because in a social context it is outside of your control

melvincarvalho avatar Oct 15 '18 08:10 melvincarvalho

There have been many detailed discussion of this in the Social Web community, which I think are all applicable.

eg:
https://github.com/tootsuite/mastodon/issues/8465 https://github.com/swicg/general/issues/1 https://github.com/swicg/general/issues/4

I wrote a pod-copy tool at one point, as did a student.

There are various attacks and failure modes to consider.

<30 pages of discussion elided>

Bottom line, simplest approach that tackles nearly all the issues, I think: one should generally have one or more backup/failover pods. Your primary pod data should be mirrored to the backup(s) (which might be a feature of the primary, the backups, or just a client). If you don't thoroughly own the domain your using, your pod should be informing all visors about your backup domain(s) to use in case there's a problem. Hopefully the being-informed can be at a machine level so humans don't generally have to worry about it. One probably wants some crypto in there, too, to narrow the options for attacking by taking over via a backup. If the domain failover works well enough, one could just use IP addresses, and live DNS-free internally.

sandhawke avatar Oct 17 '18 01:10 sandhawke

I wrote a pod-copy tool at one point, as did a student

@sandhawke nice to see you here. Is that code kicking around some place?

melvincarvalho avatar Oct 17 '18 07:10 melvincarvalho