allow users to fully export their data

Bug #721958 reported by François Marier
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Libravatar (obsolete)
Fix Released
High
François Marier

Bug Description

A few notes on how this could work:

- "export your data" (new option) or "delete your account" would trigger the export (i.e. we always export before deleting someone's account)

- gearman job receives list of emails and the photo hashes that are in /user

- the export will contain a list of email addresses and a list of base64-encoded(?) photos. there's no point in storing the association between the two because the email addresses will need to be revalidated when the xml file is imported elsewhere.

- a link to the .xml.gz is returned to the user

- the filename will be a hash of username+password so that a double export will overwrite the previous one

- that .xml.gz file is kept for 1 day in /export (a cronjob deletes old exports)

- files in /user are deleted by a gearman job (created after the export is done) if the export happened as a result of "delete your account"

- permissions of /user can be changed to root-only writes since the webapp no longer needs to delete files from there

- the last point would also require photo deletion by users (i.e. removing the photo from /user) to be performed by a gearman job

Of course the next step will be to allow imports too :)

Tags: export

Related branches

Changed in libravatar:
assignee: nobody → François Marier (fmarier)
status: Confirmed → In Progress
Revision history for this message
François Marier (fmarier) wrote :

User account export functionality is now live.

Changed in libravatar:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.