Asklemmy

43917 readers

987 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

Open-ended question
Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
!lemmy411@lemmy.ca: a community for finding communities

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago

MODERATORS

Backup Lemmy account (lemmy.dbzer0.com)

submitted 11 months ago by nyakojiru@lemmy.dbzer0.com to c/asklemmy@lemmy.ml

20 comments fedilink hide all child comments

This is kind of a question and conformation. Is there a way to backup a lemmy account from one instance and in case some thing happens, restore that user in another (with all the posts, likes, etc) ? I read that they were working on cross instance accounts , but is there a workaround meanwhile? Do we know the status of this implementation?

you are viewing a single comment's thread
view the rest of the comments

[–] mp3@lemmy.ca 15 points 11 months ago (1 children)

So far there is only (officially) the ability to export account settings, not the content itself.

[–] e0qdk@kbin.social 2 points 11 months ago (2 children)

Didn't the GDPR have a data portability rule requiring that sites provide users the ability to easily export their own data? Does that not apply to Lemmy for some reason -- or, am I misremembering it? (I remember account data download being a big deal a while back on reddit, but it's been a few years...)

[–] moon@lemmy.cafe 6 points 11 months ago (1 children)

Lemmy is a small FOSS project ultimately, not a corporate entity. If anyone got penalized, it'd probably be the instance host owner at the end of the day. I'm sure they'd be willing to add this feature if someone added it for them, but they got plenty on their plate. If you desperately wanted to for some reason, you might be able to convince the instance owner to export your info from the DB lol, but it's not even worth the effort.

[–] user224@lemmy.sdf.org 8 points 11 months ago (1 children)

I think it's more about being prepared for potential attack using loads of GDPR requests that definitely can't get processed manually even in 30 days. You know, just like we did with Reddit a few months ago.

[–] rufus@discuss.tchncs.de 6 points 11 months ago* (last edited 11 months ago)

Yeah, Lemmy and the GDPR is just an accident waiting to happen. I suppose somebody could just write a script to extract the requested information from the (PostgreSQL?) database. And share that script with other admins. But there are other parts of the GDPR that we also don't pay any attention to.

Edit: https://github.com/LemmyNet/lemmy/pull/3976

[–] mp3@lemmy.ca 5 points 11 months ago* (last edited 11 months ago) (1 children)

The regulation does not apply to the processing of data by a person for a "purely personal or household activity and thus with no connection to a professional or commercial activity." (Recital 18)

Considering most servers are run by volunteers, it's unlikely the EU will try to enforce it.

However it would be nice to have the feature, and Mastodon does have the feature to export your data to ActivityPub format.

[–] jlow@beehaw.org 1 points 11 months ago (1 children)

Is that working now, though? Last time I heard you can't transfer messages between servers as well on Masto. Would be amazing if it's possible now!

[–] mp3@lemmy.ca 2 points 11 months ago* (last edited 11 months ago)

You can't transfer but you can at least archive.

The issue I could see is ill-intentioned users importing a modified archive to alter the publication date to make it appear they posted something at a specific date in the past when they in fact didn't.