Skip to content

Commit 5e7ed2c

Browse files
Create pds-migrator.md
Brief project description of PDS migrator
1 parent 9ec24f4 commit 5e7ed2c

1 file changed

Lines changed: 22 additions & 0 deletions

File tree

pds-migrator.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
# PDS Migrator
2+
A Project to make moving data between POD's easier
3+
4+
## PDS migration
5+
More important than moving data in, is to know how to move data out.
6+
We want to do this from the frontend, not letting data reside on any intermediate server.
7+
Creating an app that makes moving data easy is our first step.
8+
9+
## Sustainable Storage
10+
When your data is in a SOLID POD and you are using five different social networks, three email clients, maybe hundreds of apps, moving your storage backend is a PITA when you need to change it at all those suppliers. We want to change this.
11+
Redirecting: http status codes (B, C)
12+
When PODs are migrated, it would be great if apps would still be able to reach the data. We would like to extend the specification. And the user should be in control.
13+
301 - Moved elsewhere permanently (key change)
14+
307 - Temporary moved, (good change, maintenance?)
15+
404 - Nothing here. (right to be forgotten? able to reuse?)
16+
410 - No longer here. (prevent abuse by keeping it occupied)
17+
18+
## The storage side
19+
The server needs to honour the user wishes and provide the correct status codes to apps, depending on data moved, permanently deleted, etc.
20+
21+
## The app side
22+
Applications should follow the data, adjust records, especially after a 301. We will deliver demo code to demonstrate how this could work.

0 commit comments

Comments
 (0)