Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How can i delete my instance #4636

Closed
2 tasks
neoranger opened this issue Aug 18, 2017 · 5 comments
Closed
2 tasks

How can i delete my instance #4636

neoranger opened this issue Aug 18, 2017 · 5 comments

Comments

@neoranger
Copy link

I need to delete my entire instance, with all the services to. How can i do that? I can't rebuild my VPS.


  • I searched or browsed the repo’s other issues to ensure this is not a duplicate.
  • This bug happens on a tagged release and not on master (If you're a user, don't worry about this).
@Gargron
Copy link
Member

Gargron commented Aug 18, 2017

Sounds like it's already "deleted"?

@neoranger
Copy link
Author

No no, my instance is working right now, but i need to delete it. (Sorry for my bad english)

@clworld
Copy link
Contributor

clworld commented Aug 20, 2017

What needed for instance deletion (As I know. not tested. instance version <= 1.5.1 and I don't consider about ActivityPub):

  • remove all follows to instance's user.
    • if not removed, remote instance send subscribe request forever
    • run BlockService and UnblockService (please be careful about BlockService and UnblockService are executed asynchronously (by Sidekiq))
    • if re-create instance with same domain, remember that same username on same domain is same user. So, if they aren't unfollowed before deletion, remote user still follow user after re-create instance.
  • remove subscriptions to remote instance.
    • if not removed, remote instance send toot until subscriptions are expired
    • run UnsubscribeService for account subscription_expires_at >= now()
  • (optional?) remove some interactions.
    • Blocks, follow request, favorites, and so on.. are federated and still exists in remote instance after delete instance.
    • if re-create instance with same domain after deletion, these federated interactions may cause trouble.
  • (optional) remove users content federated.
    • SuspendAccountService may helps you. but it is slow and costs many(because it send delete for all toot to remote instances).

Note: With ActivityPub(Mastodon >1.5.1), federations depend on follows. so remove follow before execute SuspendAccountService is bad. and SuspendAccountService remove anything after execution. be careful.

@neoranger
Copy link
Author

Thanks!

@Neustrashimy
Copy link

Could you tell me the specific procedure?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants