-
-
Notifications
You must be signed in to change notification settings - Fork 862
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: post removals not being properly federated #3980
Comments
Confirmation of ProblemConfirming this issue also exists for lemmy.dbzer0.com, but it is intermittent. For example, all of the six example posts below were made on a community hosted by lemmy.dbzer0.com. Four of these posts were removed by a lemmy.dbzer0.com admin. However those removals are not observed to be federating consistently to other instances - I have included specific examples below. In two of the included examples, the posts were removed by another instance admin (from the origin server of the user who created the post). We would not expect those post removals to federate to lemmy.dbzer0.com and elsewhere, however those removals did in fact (mostly) federate to other instances that we checked. Expected behavior
Examples
|
This is actually not a bug. The implications of what you are suggesting is giving other instances the authority to affect other instances that they should not have authority over. Having moderator or administrator permissions on instance A does not imply moderator or administrator permissions on instance B. This would be a severe security flaw. |
This is confirmed to be a bug by Dessalines. I posted this here on his request.
Moderators and Admins of the community's instance absolutely need to be able to remove posts from their instance's communities. And those removes shoulld be federating.
|
IzzyData: To clarify, if I moderate a community hosted on my instance, and I remove a post from that community on my instance, then that removal should be federated out to all other instances that federate with my community. That is how I, and many other admins, expect lemmy to behave (see https://matrix.to/#/#lemmy-support-general:discuss.online) for a recent discussion on this topic. Otherwise we would need admins on every federated instance to deal with the exact same report independently which is totally unworkable. If you are talking about the second example I gave where a remote admin removed a post and the removal federated to my instance, I totally agree that is not how it should be working, however that is what we observed to happen. There is no removal mod action recorded in our modlog, only in the modlog of the remote instance, even though the community is hosted on my instance. |
Same problem here. Getting a lot of reports from remote users for posts that I long moderated on our instance, and it really paints a bad picture of our communities as unmoderated when viewing them remotely. My guess is that this mainly happens when a site admin that is not the same time also community moderator of that specific community takes a moderation action specific to that community? Edit: it is not only post removals but also community specific user bans that don't get federated it seems. |
Removals are definitely supposed to federate when they are made on the instance where the community is hosted.
Good thinking, it looks like you are right. Im currently trying to fix it. Edit: fixed in #3988 |
Requirements
Summary
A user from lemmy.ml posted into a lemmy.world community. After the thread was removed from the lemmy.world community the thread stayed visible on lemmy.ml
Thread on Lemmy.ml
https://lemmy.ml/post/5128305
Community on Lemmy World.
https://lemmy.world/c/sciencefiction
Community on Lemmy.ml
https://lemmy.ml/c/sciencefiction@lemmy.world
Steps to Reproduce
Technical Details
No logs available
Version
BE 0.18.4
Lemmy Instance URL
lemmy.world
The text was updated successfully, but these errors were encountered: