The federation between mastodon and lemmy is strange. If a M account wants to follow a L community, they need to follow an automated M account which represents the L community. But if any M post mentions that L community, the post will get boosted by the community’s M account, so everybody who follows will get a notification. And I’m not sure if this can be moderated from the L side, because it seems like it never goes through L. Such as - do you see this @opensource ? Does a L mod see this?
@otter I’ve seen other instance admins discussing that certain way of removal federates, but other doesn’t. I don’t know the specifics. Deleting from lemmy db directly doesn’t federate, it clears it on that particular instance, but it makes it worse for others. https://slrpnk.net/comment/6287249
Good to know ok, I’ll keep that in mind when dealing with spam
As far as I know, only if the content belongs to the source instance it does federate the removal. So when deleting posts from this community, it should federate (unless of course you do the stupid thing and just delete it in the db). But I’m not sure of how well the deletion does federate over to Mastodon.
@rikudou Yeah it looks like making a mastodon post and tagging a lemmy community makes it very hard for everyone to remove, because each admins has to ban that source account or instance individually. It would be much better if the mentioned lemmy community admin could do that, because that’s the one common place. The reboost is the main problem. The lemmy admin should be able to unboost posts that were moderated, that would remove it from all timelines, not just the lemmy page.
here I found a way to show the issue nicely - boosted comments on mastodon match the comments and posts on lemmy, except the spam, that’s only on mastodon (bitjc1ronj), still boosted, even when it disappeared from lemmy.
From which community it disappeared? Because the admins here did the stupidest thing and deleted it straight from the database, which obviously doesn’t federate. But generally, if the community that has the content removes it (in a normal way), it federates the deletion with others.
Lemmy.ml not doing a normal removal fucked with other Lemmy instances as well and now everyone has to remove it, just as you said. But in a normal situation, the removal would be federated to other Lemmy instances and I guess to Mastodon as well, but not sure how Mastodon deals with it.
@rikudou Ah, looks like you didn’t see my screenshot, it doesn’t federate from mastodon to lemmy? https://mstdn.io/@chebra/111958352624253539
@rikudou I can even see it in the modlog: https://lemmings.world/modlog/44
That’s a modlog on lemmings.world, which is mine instance, where I (or my automod to be specific) indeed removed it. But because this community is not on my instance, my removal does not federate. There’s one other removal but that’s also not from a lemmy.ml admin/mod. Can you see this post somewhere? https://lemmings.world/post/5968108
Because that one was also removed by a lemmy.ml mod/admin, so it should be federated.
Edit: Found the post as well, so federation is indeed broken. But the other cases wouldn’t be federated anyway, even if it worked.
@rikudou the same modlog entry appears on https://lemmy.ml/modlog/14749
@rikudou But scroll down on the mastodon timeline of the lemmy booster and you can find it there: https://mstdn.io/@opensource@lemmy.ml
@rikudou I think it *would* federate the deletion, if this was a post originating from the lemmy instance. But this is originating from an abandoned mastodon instance, merely mentioning the lemmy community. Lemmy admins can remove it from their community, but in the meantime it gets boosted on the mastodon side and that boost stays there even after the removal. This should be fixed, the moderation should be interpreted as an unboost, that seems to me like the most straightforward solution.