relevant magazine is /m/RedditMigration here on kbin.social. You can see it’s the one and only report in the modlog yet the user who removed the comment is not listed in the moderators list, is not even a kbin.social user, and did not remove a lemmy.ml comment. Yet, it was removed for me as a kbin.social user.

How is this moderation working exactly? It’s understandable that lemmy.ml mods can remove things for lemmy users, and mods on a magazine can remove things on the magazine. But it seems this is an unrelated user, removing a post of a user from an unrelated instance from a unrelated magazine.

How is this possible? what’s going on here?

Edit: I checked on lemmy.world’s copy and the comment is still visible, meaning the removal did not federate to lemmy.world.

      • arkcom@kbin.social
        9·
        2 years ago

        Bad news for the “who cares how evil the devs are, they can’t affect anyone else” crowd.

        • yozul@kbin.social
          9·
          2 years ago

          Not really. That has to be a bug in kbin, not a problem with Lemmy. Lemmy allows admins to delete stuff off their own instance, but kbin shouldn’t be just accepting that as a mod action from any admin on any server it’s federated with. That doesn’t even make sense. I assume it’s just a weird interaction of different ways of handling things on kbin and Lemmy.

          • arkcom@kbin.social
            2·
            2 years ago

            It honestly would be a terrible idea to allow some cross instance moderation to help ease the load. It would just require a lot of trust.

            Edit: yes I meant wouldn’t ^. don’t want to change it now.

              • arkcom@kbin.social
                1·
                2 years ago

                Yes. Obviously only between instances that agree to it and trust each other.
                There already seems a way for a lemmy user to moderate communities on other servers.

  • HidingCat@kbin.social
    5·
    2 years ago

    That’s a really interesting mod action you caught. Trying to make sense of it now but kbin is still having some issues; I’m still getting 503 errors when poking at the mod stuff.

  • cendawanita@kbin.social
    4·
    2 years ago

    @Otome-chan@kbin.social yeah, that’s what needs to be tested:

    1. Is the originating instance the true copy? Or is every copy of equal status? Kbin’s handling of having local copies is probably the issue here because other fedi protocols don’t choose to do it this way (and it’s probably because this reduces the load from all the fetching; big fedi accounts have been known to induce DDOS-like results when a post gets popular)

    2. If that can be confirmed/clarified, is the mod log a universal log only but specific instance changes not propagating? I think Q1 is going to be the pickle here - because it implies a lot in terms of coordinating copies across the kbin infra at least (not sure with Lemmy I’ve not poked around at all). Copy conflict is going to be inevitable at this point…

  • Shortcake@kbin.social
    2·
    2 years ago

    I haven’t used my mod actions yet, but my guess is that another user used the report function. A mod deleting the comment due to a report from another user is probably what happened

    • Otome-chan@kbin.socialOP
      2·
      2 years ago

      but that lemmy.ml user isn’t a mod of /m/RedditMigration, and the removed comment wasn’t by a lemmy.ml user? do random lemmy.ml users have the ability to remove comments like that? the only mods of /m/RedditMigration are you and ernest and neither of you were the ones to remove it?

      • Shortcake@kbin.social
        6·
        2 years ago

        I meant that because the mods of this magazine saw the report and deleted the comment, the credit in the mod log was given to the reporting user

        • Otome-chan@kbin.socialOP
          5·
          2 years ago

          oh, I see. yeah that makes sense then I guess? I would’ve thought that it’d be reported based on the mod that removed it? but I guess not. that explains it.

          • Shortcake@kbin.social
            5·
            2 years ago

            Again this is my supposition. We can test it if you want, I’m a mod at /m/RedditMigration you could try reporting a comment of mine there, I’ll delete it and see who it shows
            Edit: @Otome-chan i forgot what group we were in. Thought this was RedditMigration for a minute

      • cendawanita@kbin.social
        1·
        2 years ago

        @Otome-chan@kbin.social what’s probably happening is that the mod action, like edits to a post do get federated along as well. The only time you won’t see the changes propagate is if a federated mag is on an instance that gets defed, then no future changes will occur. Not sure if you’ve had a fedi account before this but if you do, it’s like when you boost a post and the post owner edited it and you get a notification that your boosted post has been edited and you see the new text. So the kbin copy (this is where the threadiverse differ, in having local copies. One reason why ‘copy url’ has two versions, the instance copy and the original copy) may have the instance owner as the delegated owner of the mag but the original mod actions can still travel. So the mod is still the mod of the magazine in all federated copies of their community/mag.

        ETA: I’m letting my comment stand but just noting, i didn’t answer your question at all, i think. OTL

        @Shortcake