i think the graph might not be fully accurate for the current hour? looking at it now it doesn’t show that significant of a spike anymore. i don’t see anything in our logs about federation issues from LW to p.d in the last 15 days.

I don’t see us going down anytime soon, and at current user numbers I don’t think there’s going to be a major difference in moderation workload with the influx of users compared to what we already have, but it really is not great for decentralization. We already try delegating the majority of moderation to community moderators where applicable, where on a lot of other instances the admin teams seem to be more involved in addressing community reports on admin level as well. For the most part we’re dealing only with instance level topics in the admin team and provide some additional tooling to improve report notifications to community mods. There are even various benefits from a moderation perspective when users are all local and not remote, as with federation a lot of signals that would allow various types of abuse are unfortunately lost. That said, I would still prefer if there were more stable and larger instances overall, while not having a single instance stand out as massively larger than any other one. Friendly “competition” is almost always beneficial for everyone involved.

lemm.ee being the second largest instance and the shutdown only being announced less than a month before is unfortunately also not something that gives people looking for a stable instance much confidence. I hope this won’t scare too many users away from Lemmy and that most will just find a new instance in the Fediverse.

Instance moderation and moderation in general are unfortunately tasks that can be very challenging at scale, even with just a few thousand users, especially when dealing with drama. It’s not really a surprise that there are somewhat frequently posts from larger instances looking for new admins, while older admins on the same instance are becoming less active. Even if people aren’t exhausted from their involvement, their circumstances in life may change, or they may no longer be interested in Lemmy as a platform in general, leading to a number of reasons why admins may not be as active as it seems when looking at the list of admins in an instance sidebar. It’s often a thankless job with a lot of things happening in the background to deal with spam, trolls and other issues, which most users won’t even see when done right.

tbh it’s probably not going to be too complicated to switch to 1.0. the current api is generated from lemmy-js-client, but 1.0 api has an official openapi file. if there is a decently usable openapi generator for go that would probably not be too complicated to swap in instead and adjust the api calls in mlmym code.

already did. it’s the same person running the infrastructure, although moderation of mstdn.party and mstdn.plus is handled by someone else.

we’ve since been in contact with the person running these services and the material has been taken down on lemmy.one, as well as lemmy.one closing down in three months.

we’re still discussing in our team how we will deal with this going forward and will be posting a new announcement about this in the coming days.

you can read https://lemmy.world/post/29550945 for our previous writeup about this.

certainly not something i’m willing to risk. defederated them now.

the stuff is still up on lemmy.one, months from the original report, with zero indication that they care about it in the slightest.

i’m tempted to add their domains to our automod (only removal), but i’ll discuss this in our team before doing so.

even if there are multiple people involved in the operation of this discourse forum, even this announcement is by jonah, who as far as i can tell is the head of these projects and also owner of the associated US companies. if this was something ran by a different team and they’d be able to separate themselves from jonah’s (in)actions then it might be a different story, but as it is right now, it seems that all these services related to PrivacyGuides are operated by the same entity.

we had an issue related to incorrectly caching 404 responses earlier but that was a few hours before your post. it should already have been resolved when you posted this.