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.

  • cendawanita@kbin.social
    2·
    1 year 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…

    • Otome-chan@kbin.socialOP
      0·
      1 year ago

      So I just checked on lemmy.world and the comment is not removed there like it is here on kbin. yet, kbin is the hosting instance of the community. if kbin thinks it’s removed, then surely that removal should be sent out to others who look at it?

      • manfre@kbin.social
        4·
        1 year ago

        With ActivityPub there is no forced actions on other instances. When a delete happens on an instance, it sends a “this was deleted” announcement to the relevant instances it knows about. The servers that receive the message could easily ignore it and keep their copy of the message active/visible.

      • cendawanita@kbin.social
        0·
        1 year ago

        @Otome-chan@kbin.social oh yeah, definitely some kind of copy primacy/conflict issue for sure. I have no idea how to describe it well enough for the codeberg ticket tho - definitely worth raising.