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
spam comments bypassing moderators #8434
Comments
Thank you SO MUCH for reporting this @bronwen9 !!!!! |
Hi @bronwen9 - thanks, and good to hear from you. The comment you mentioned is listed at https://publiclab.org/spam2/comments in the new comment moderation system created by @keshavsethi, so that part of the issue I believe is resolved. For your idea --
Tracing our comment moderation system, I believe comments by first timers are (code for ref below) Lines 651 to 655 in e92aa27
Lines 140 to 142 in e92aa27
I think this resolves the issue but please re-open if anything looks wrong or there are gaps here, or if you have other ideas to add. Thanks a lot! |
I think we have not communicated with our moderators that they should be using /spam2, or when /spam2 might replace /spam. |
Comments from unapproved posters land on pages without 1) appearing on the moderation queue or 2) appearing as a new/unmoderated comment on the dashboard (am assuming because technically they're not approved or live on the site.
The comments do show up with the approve/spam button once you navigate onto the page, but there isn't anything to alert moderators to their presence unless they happen to open the post. Users don't appear in "active user" lists.
I haven't deleted the posts on this page here (these should only be visible to moderators):
https://publiclab.org/questions/mimiss/09-16-2020/for-the-bucket-monitor-how-many-tedlar-bags-do-you-need-per-sampling
Screen shot
Is there a way to ensure that the alerts to moderators for first time posters include posts that are made in the comments? I have observed most of these limbo posts to be spam, but wonder if we are also missing some "real" first time posters this way.
The text was updated successfully, but these errors were encountered: