other accounts:

  • 0 Posts
  • 35 Comments
Joined 1 year ago
cake
Cake day: February 10th, 2024

help-circle
  • lemmy currently doesn’t have granular federation controls. the only option right now is to defederate from mbin instances, but other instances might still announce your users’ votes to mbin instances. the more hacky way would be to also block federation related http requests from mbin instances to prevent them from retrieving user profiles, which is probably the most effective method that could be used.

    piefeds non-federated votes are a user setting for the default value and users have the option for each vote whether it should be federated. see also https://piefed.social/post/982478
















  • 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.




  • MrKaplan@lemmy.worldtoFediverse@lemmy.worldLemmy.one will be shutting down
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    2 months ago

    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.