Archiving/backup/migration support

[jg10-mastodon-social]

Another use case/level of interoperability is to only use Solid as a backup/archive.

In this context, one could imagine a tool that extracts inbox and outbox collections from e.g. a mastodon server and persists them on the pod - in a form that is compatible with other Solid apps.

It would probably be worth looking at existing ActivityPub migration specs/tools.

[jg10-mastodon-social]

FEP-1580: Move Actor Objects with a migration Collection
https://codeberg.org/fediverse/fep/src/branch/main/fep/1580/fep-1580.md

• a migration collection that contains a mapping from source object URIs to new URIs on the target instance, and
• a moves collection that contains the actor Move activities that prove a migration has taken place and allows verification of object signatures in the case the source Actor is no longer available.

[jg10-mastodon-social]

https://github.com/swicg/activitypub-data-portability

Repository for the ActivityPub Data Portability Task Force of the social web community group at W3C.

We maintain:

• A descriptive report covering the Data Portability problem space, which so far lists all the different data surfaces that end-users might want to include in scope of portability use-cases.
• A draft of a Server-to-Server transfer protocol called LOLA. https://swicg.github.io/activitypub-data-portability/lola