Implement a way for a user to export their account data.

[StaticallyTypedRice]

Most social media platforms have a way to export all of your account data into a downloadable zip file, including all your posts, comments and uploaded files. This is good for privacy as it allows the user to easily check what information the website has on them, and also allows the user to back up or archive their own data offline. I believe GDPR and CPPA also requires this feature, at least for the user's personal information (along with a way to permanently delete that information), so we should add it to the list of things to implement before Lemmy gets out of beta.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[Nutomic]

Okay so what kind of data does this need to include? And what should be the goal of this export, to import it somewhere else, or to view it locally?

[StaticallyTypedRice]

Okay so what kind of data does this need to include? And what should be the goal of this export, to import it somewhere else, or to view it locally?

I would try to export anything that can be attributed to a user, but it should at least include posts, comments, votes and settings. Also images uploaded to pictshare and maybe things like subscriptions. At the very least anything that contain the user's personally identifiable information should be exportable in compliance with privacy laws.

As for what it's for, I think the main goal would be to have an easy way to back it up at first. However, a restore system would make a lot of sense when Lemmy becomes federated to allow users to switch instances without losing their content.

[dessalines]

This isn't too difficult, as a lot of the back-end DB calls can already filter by user. So this is kind of just creating a wrapper for a lot of that data. Its just wayyy down in priority for me.

[glibg10b]

With the current surge of users migrating from Reddit, this feature would allow us to relieve some pressure of lemmy.ml, whose amount of active users has grown 683% since Reddit's API announcement

[TheYang]

I'd say exporting and importing subscriptions would be a good first step in easing users ability to migrate instances.

[maltfield]

@TheYang see #3040 for just importing a list of community subscriptions with a single-click

[RobertSchuh]

There's a bookmarklet workaround to get a list of subscribed communities, useful for if you're moving to another instance:
https://feddit.de/post/808717

[academician]

I'd like to recommend that this be implemented in a way that it can be offloaded to a cron job or something, possibly performed on a different service entirely. From experience, database exports can be expensive for accounts with a large amount of data, and if there's ever a rush of multiple at once it can bog down the server or database.

My initial approach for a problem like this:

• Make an export queue DB table
• Make a script/program that polls the table periodically and grabs the newest row(s?)
• Lock the row(s) it's processing (with a timeout)
• Do the work and upload the zip file somewhere
• Email a link to the user (and/or put it on a web page accessible from the UI)

If an export fails or a row lock times out (ie, because the script crashed), unlock the row and increment a retry counter, then retry the export after some backoff interval up to some max number of retries where we report the failure to the user (and admins?).

Should probably also only keep the last N exports and only for M days. This can be configured in something like an S3 bucket.

[m3gatech9]

I'd like to be able to backup my saved posts/comments as well.

[CMahaff]

I elaborated more in #3040 (#3040 (comment)), but besides what has already been requested here, being able to migrate user and community blocks is also super important.

Nice to haves are things like being able to migrate profile settings like theme, default sort, etc. These are more problematic though because they are still changing a lot.

[Nutomic]

#3976