Follow

masto account question, remote data retention 

we're aware that there's *always* the risk that our posts and associated data are going to be cached somewhere indefinitely. However, if we wish to ensure the best possible data deletion when we delete an account, would it be better to delete the posts one by one first or just nuke the account?

Web 2 4 1

masto account question, remote data retention 

welp, in the meantime until we have a more definitive answer I have Forget currently picking posts off once every minute. Hopefully that's slow enough to not get rate-limited.

Show thread

masto account question, remote data retention 

@alanae this is a really good question to which i would like to know the answer as well!

re: masto account question, remote data retention 

@alanae yeah i think that deleting the posts with forget is the best way to go?

but also i dunno because i think that an account deletion is supposed to send Delete activities out for each post?

馃し

re: masto account question, remote data retention 

@compufox maybe we're being paranoid but we just want to make sure it's all as gone as it can be.

I kinda wish we had did that with our alanae.net accounts but oh well.

re: masto account question, remote data retention 

@compufox and it's like we don't even care that it's there a the moment, we just don't want to not have control over it once the instance shuts down

re: masto account question, remote data retention 

@alanae @compufox fwiw, slowly doing post deletes before the account delete is *much* nicer on the rest of the fediverse... for example, the Snouts Incident took up all of our sidekiq workers for a couple hours, and that sucked

Sign in to participate in the conversation
LGBT.io

We are a Mastodon instance for LGBT+ and allies!