[Feature]: Instance Self-Destruct #9727

Open
opened 3 months ago by lunanova · 8 comments

What feature would you like implemented?

I'm thinking of switching Fedimint back to a Mastodon fork, but in order to do that, I'd need to be able to remove our instance from the Fediverse, like Mastodon.

Why should we add this feature?

Some instance admins just don't want to run their instances anymore, and self-destructing is the best way to make sure that their stuff is gone.

Version

13.1.3-rc2

Instance

fedi.mint.lgbt

What browser are you using?

Firefox

Relevant log output

n/a

Contribution Guidelines

  • I agree to follow this project's Contribution Guidelines
### What feature would you like implemented? I'm thinking of switching [Fedimint](https://fedi.mint.lgbt) back to a Mastodon fork, but in order to do that, I'd need to be able to remove our instance from the Fediverse, like Mastodon. ### Why should we add this feature? Some instance admins just don't want to run their instances anymore, and self-destructing is the best way to make sure that their stuff is gone. ### Version 13.1.3-rc2 ### Instance fedi.mint.lgbt ### What browser are you using? Firefox ### Relevant log output ```shell n/a ``` ### Contribution Guidelines - [x] I agree to follow this project's Contribution Guidelines
panos added the
Feature
label 3 months ago

For my own research:

Here's Mastodon's implementation: 94cbd808b5/lib/cli.rb (L94)

As far as I can tell, it essentially iterates through all accounts, and for each account checks if it has an inbox, if so suspends the account, makes the account publish an update that it's been suspended, then deletes the account.

For my own research: Here's Mastodon's implementation: https://github.com/mastodon/mastodon/blob/94cbd808b5b3e7999c7e77dc724b7e8c9dd2bdec/lib/cli.rb#L94 As far as I can tell, it essentially iterates through all accounts, and for each account checks if it has an inbox, if so suspends the account, makes the account publish an update that it's been suspended, then deletes the account.
Poster

I figured it did something similar to that. I did a similar thing when we switched software for our Matrix server, so that makes sense.

I figured it did something similar to that. I did a similar thing when we switched software for our Matrix server, so that makes sense.

@daikei it is not the instance's job to control/limit admin decisions. What you described is out of scope, but could be implemented in a plugin/server addon, once that gets added.

@daikei it is not the instance's job to control/limit admin decisions. What you described is out of scope, but could be implemented in a plugin/server addon, once that gets added.
Poster

You should probably shut down the web UI while the deletion is in process, as it takes a while. Mastodon solved this by leaving the Sidekiq process running, but the processes are not separated in Calckey.

You should probably shut down the web UI while the deletion is in process, as it takes a while. Mastodon solved this by leaving the Sidekiq process running, but the processes are not separated in Calckey.

While @daikei's feature set might be out of scope for this request, I think part of the idea is something that could be implemented as part of a self-destruct system... The "delay" before the self-destruct is initiated.

I think it would be beneficial if the system strongly suggested to the administrator(s) of an instance that users should be given notice of the instance going offline. This would allow a couple of things:

  • Users can grab copies of all their data.
  • Users can migrate to other instances smoothly if they want.

I agree that there is nothing to stop an admin from just pulling an instance down without notice. However, I do see the benefit in the system trying to dissuade admins from taking actions that are more detrimental to the Fediverse and their users.

While @daikei's feature set might be out of scope for this request, I think part of the idea is something that could be implemented as part of a self-destruct system... The "delay" before the self-destruct is initiated. I think it would be beneficial if the system strongly suggested to the administrator(s) of an instance that users should be given notice of the instance going offline. This would allow a couple of things: * Users can grab copies of all their data. * Users can migrate to other instances smoothly if they want. I agree that there is nothing to stop an admin from just pulling an instance down without notice. However, I do see the benefit in the system trying to dissuade admins from taking actions that are more detrimental to the Fediverse and their users.
Poster

If users were to migrate to other instances, you'd have to leave a window before you start deleting stuff, due to the nature of how deletion works.

If users were to migrate to other instances, you'd have to leave a window _before_ you start deleting stuff, due to the nature of how deletion works.
Poster

We're no longer going to be switching Fedimint to Mastodon, so we won't be self-destructing. However, I'll keep this open as this is an important feature.

We're no longer going to be switching Fedimint to Mastodon, so we won't be self-destructing. However, I'll keep this open as this _is_ an important feature.

Agreed

Agreed
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: calckey/calckey#9727
Loading…
There is no content yet.