Lemmy Support

4625 readers

2 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago

MODERATORS

[email protected]

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

submitted 1 year ago by [email protected] to c/[email protected]

4 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?

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

[–] [email protected] 1 points 1 year ago

I'd also like to know this. Out of curiosity I looked into whether blocking an instance would send some kind of message to de-federate, but that does not appear to be the case. If you look at beehaw and lemmy.world you can see that beehaw has lemmy.world blocked but lemmy.world is still federated with beehaw.

I looked through the ActivityPub spec and didn't find anything interesting there either.

Also found this closed bug report on their github which really went nowhere. But that let me down the rabbit hole to this commit.

I think the conclusion I've come to is that, as of today, there is no proper way to decom a lemmy instance. I think the best we can hope for is for there to be maturity detecting, flagging, and ultimately removing dead peers.