-
-
Notifications
You must be signed in to change notification settings - Fork 863
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
Allow all admins to purge content #2976
Comments
I dont think its worth the effort to add another setting. Instead we can allow purging by any admin account. This is a bit risky if an admin gets hacked or goes rogue as he could wipe the entire site. However this could be solved by a rate limit, or restoring from backup. |
Need to change the check in file below and in other files next to it. Looks like the frontend already shows purge buttons to all admins so there is no change needed. https://github.com/LemmyNet/lemmy/blob/main/crates/api/src/site/purge/comment.rs#L27 |
I want to stress that its incredibly dangerous to add this. Anyone you appoint as an admin, can potentially wipe out entire communities, users, and years of content, none of it being resurrectable in any way (unless you were doing backups, and even then, very difficult to restore). I'm not necessarily against it, but I'm100% sure that if we allow this, someone will come complaining to us that someone infiltrated their admin team, deleted all the content on their server, then ask us for how to resurrect it, and we won't be able to. |
Then make it a per-admin setting with an additional pop-up to confirm the setting with a message that informs them of this risk. For those of us that have decided we are okay with the risk (making regular backups and trusting the admin team), being able to purge CSAM content without requiring more people to observe said content in order to purge it is extremely desirable. |
That would be very easy to notice, so at that point you would restore a full db backup and remove the offending admin. Anyway we are not responsible for what people to with Lemmy. Sometimes its just necessary to act fast, and waiting for a single person to come back online is not a good option. |
Shouldn't be too difficult to add, but everything needs to come after this http rework, with v0.18. I'm going on strike w/ respect to more cherry-picking to |
Isn't there a way for admins to suspend content, and just leave it for the top admin later? |
Also supporting a suspend option, if you really need it fast, add an option to disable accessing the content. Because you need to react fast for CSAM. |
this should be resolved by: #3271 |
Has the talk about security also been resolved? Is it possible to restore purged content? |
Purge means that the affected content is permanently gone, so it cant be restored (unless you restore a backup). |
For backend issues, use lemmy
Is your proposal related to a problem?
Someone posted CSAM on another instance last night and we had to wait for the top admin to purge content. To minimize burden on all admins a site should be allowed to set it up so any admin can purge content.
Describe the solution you'd like
Checkbox, something to set, whatever solution allows an instance to let all admins to purge content
Describe alternatives you've considered
No alternative available
Additional context
This really needs to be added ASAP with new user growth correlating with an influx of trolls
The text was updated successfully, but these errors were encountered: