2w ago

Lemmy.one will be shutting down

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

84 comments

Thanks for the cross post.
Citations needed on mod tool complaints. I mod one of the largest communities on Lemmy. In 2 years I've had around a couple dozen times that required actual mod stuff. The tools are perfectly adequate for the volume of users in my opinion.
We all took it a little hard when some regular users left. I get that. There will always be people coming and going for various reasons.
There is also always an issue with narcissists that tend to get involved with moderating for the wrong reasons.
All humans are lazy at times. And all of us have a right to pick up an leave if we choose. Blaming the tools as a scapegoat for one's laziness, or inadequacy, or to mask one's financial limitations, seems to me like a narcissistic way to toss in the towel and check out, like an attempt to drag others down too.
I wish those that want to leave all the best, and I'll still be here hanging around if you ever want to come back, friend. Regardless , thanks for what you contributed to this place in the time we spent as digital neighbors.
- The linked post explains:
  A Lemmy.World user informed us about an instance we are federated with that was hosting very illegal content a while back. This was a result of an attack more than a year ago, and said content federated to many other instances, which made local copies of the material. Unfortunately, when this material was taken down at the source, that action did not federate to all linked instances, meaning that there are still some instances showing this material.
  Once we were made aware of this, we realized that this was likely not the only occurrence, so we started looking for other instances where this content may also still exist. We have identified more than 50 affected instances and already reached out to many of them to inform them about this content to have it taken down.
  It seems that it is quite difficult for instance admins to do things like permanently remove posts locally which have already been removed by a mod somewhere else. Ironically, by intentionally making it difficult to access, its inaccessibility afterwards makes it difficult to... uh... access, e.g. to delete it, very much a design flaw.
  
  This should be the top post. This is the part with the meat and potatoes.
  
  I didn't know this bit when I made the crosspost.
  
  No worries.
  
  it's a combination of multiple issues.
  lemmy federation has improved significantly over the past years, so if this was happening with lemmy instances today, especially online ones involved, this would be much less of an issue.
  the original user posting this stuff was on a kbin instance. kbin/mbin still do not support federating bans of users. kbin is basically dead, mbin is tracking that here. when this was originally removed on kbin this never federated out to other platforms.
  the next problem is that the original instance is no longer there, so attempting to address this with community bans from lemmys side is not working anymore if the user isn't known to the instance anymore, as it can't be refetched from the source. if the instances that the related communities are hosted on purged this user in the past they wouldn't be able to federate out a community ban anymore.
  another problem is that lemmy is typically configured in a way where it creates a local copy of thumbnails if no thumbnail url is provided by the source, which is what lead to a local copy of this material. in the end i consider this only a secondary issue, as while most people would rather not have this stored on their servers at all, if you allow media uploads you can never be 100% sure about the content uploaded to your server. this is therefore typically something where providers are expected to take action once they become aware of it. some providers are also taking preventative measures like scanning uploads, comparing to hash databases of known csam, etc. had the original instance ban or community bans been performed properly this would at least have removed public access to the stuff, as the media filenames are randomly generated and not guessable.
  it's generally not impossible to prevent stuff from returning to your instance once you have taken it down properly, but in cases where federation didn't work, which could be for a wide range of reasons, including your instance being misconfigured during maintenance, your instance being defederated from an instance involved in the removal, and others, it may require local action. if i ban a user then no new content form that user is going to come to LW until they are unbanned again. this includes manually fetching posts or other content, so if i purge an old post of theirs the post wouldn't be able to come back until the user gets unbanned.
- The biggest one is that there needs to be a distinction between mod report and ijstance admin report
- Fully agree. Make issue, open bug bounty if you wish. Ask your community for donations or plain make a paid service so you can handle finances. Thats it. Of course things can always improve but that also requires that instances drive donations to the devs and are active in decisionmaking.

84 comments