@support Yesterday I saw this post https://beehaw.org/post/7776438 where it used the non-propagation of deleted posts as an example o (masto.ai)

submitted 1 year ago by SharkAttak@masto.ai to c/support@beehaw.org

3 comments fedilink hide all child comments

@support Yesterday I saw this post https://beehaw.org/post/7776438 where it used the non-propagation of deleted posts as an example of one of the problems of the Lemmy platform. Today, this post https://lemmy.world/post/5289864 says there's "a bug in kbin where moderation tasks are not federated to other instances".. i'm confused, isn't that a problem coming from the underlying software, Lemmy? Are they shifting blame?

you are viewing a single comment's thread
view the rest of the comments

[-] mp3@lemmy.ca 7 points 1 year ago

The issue is that kbin actions to delete/moderate a submission aren't sent to other federated servers, increasing the moderation workloads to all instance admins.

Kbin and Lemmy are compatible in a way through the underlying protocol (ActivityPub), but on the surface they're two entirely different codebases with their own quirks.

[-] SharkAttak@masto.ai 1 points 1 year ago

@mp3 I know, but from the first beehaw link it seems to be an issue that's on Lemmy too, so what I don't understand is why they're trying to frame it as a Kbin-only bug.

[-] mp3@lemmy.ca 4 points 1 year ago

There are two different issues, kbin will simply not federate mod actions, while in Lemmy you need to make some steps in the right order. If you ban then purge the content a little later it will federate the ban, while if you do it the opposite way it will not federate the ban and leave the content up on other instances.