cross-posted from: https://lemmy.one/post/27858506

This post serves as notice that Lemmy.one will be shutting down in 90 days.

Unfortunately, the moderation features in Lemmy never progressed to the point required to continue maintaining this service, and Lemmy simply does not have the userbase to justify the cost of this service. Myself and the moderation team apologize for the inconvenience this will cause.

This is sad news. Hopefully the comms can migrate to other smaller instances.

Edit: just saw this

as this is a fairly active community we just wanted to let you know that this community is no longer federating with Lemmy.World due to defederation from lemmy.one for lack of moderation.

Our announcement can be found here: https://lemmy.world/post/28173093

We recommend migrating to a community on an instance that is maintained better.

I guess it’s been an issue. I think the lemmy.one meant they needed better administration features

  • kersploosh@sh.itjust.worksEnglish
    33·
    17 hours ago

    Here are a few things off the top of my head.

    Deleted accounts leave orphaned posts/comments, which still exist on the site but can be difficult for admins to find and remove: https://github.com/LemmyNet/lemmy/issues/5525

    Private message reports don’t go to all the right people: https://github.com/LemmyNet/lemmy/issues/4436

    We should be getting some vote analytics in the future, which will be great. Lemmy seems to have a significant number of vote manipulation accounts that only exist to upvote/downvote in unison, but they are currently hard to find. https://github.com/LemmyNet/lemmy/pull/5669

    I really should open an issue to improve the reports queue. It’s tolerable if you mod an individual community or a smaller instance, but it is unusable as an admin on a really big instance like .world. There is no way to search or sort the reports. You can filter by posts or comments but then it only shows you 20 entries, which is a weird and unhelpful limitation. All reports have equal priority; there is no mechanism for users to flag reports that should be escalated to admins. And, if something is heavily reported, there is no way to batch resolve the reports after you address the issue.