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
    1·
    1 year 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