Lemmy Support

4650 readers

1 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago

MODERATORS

dessalines@lemmy.ml

How to properly decommission a Lemmy instance? (feddit.de)

submitted 1 year ago by JASN_DE@feddit.de to c/lemmy_support@lemmy.ml

3 comments fedilink hide all child comments

As previously discussed here https://feddit.de/post/1285536 , I am trying to properly decommission my private instance. My main issue: even though I unsubscribed from all communities, the server still gets a lot of POST requests with likes, comments, etc. So how do I tell all the instances to stop sending announcements? I also don't want to go the hacky way of bogus DNS entries, as that won't be good for the other instances. This also continues if I simply shut down the stack, just resulting in a lot of 404s.

Is there a manual for this I missed in all the googling?

top 3 comments

sorted by: hot top controversial new old

[–] hawkwind@lemmy.management 5 points 1 year ago

Commendable that you want to help, but the software needs to handle dead installations as there is no possible way to enforce people to decommission. :) Might be worth dropping just to help the use case of how this gets handled. I feel like you did everything you could.

[–] PriorProject@lemmy.world 3 points 1 year ago

This is a wild guess, but have you tried hacking your proxy to return 410 GONE for the ActivityPub endpoints? A well behaved system is supposed to interpret that response as meaning that the resource is gone forever and to stop trying. I have no idea how Lemmy will respond, but it might be a step along the way to disappearing the endpoints once you've run out of other ideas to see if the rate announcements starts to fall off.

[–] gabriele97@lemmy.g97.top 2 points 1 year ago

There is a PR on GitHub that implements checks towards all the federated instances and those who doesn't respond for a few days will be marked as stale and the instance will stop sending updates to them