Address comments being spammed. #105

Closed
opened 2020-02-22 01:47:20 +00:00 by FreeScholar · 17 comments
FreeScholar commented 2020-02-22 01:47:20 +00:00 (Migrated from gitlab.com)

Background

There are many spammers trying to comment on geo.coop They are being stopped, since anonymous comments must be approved, however a lot are coming in, taking a lot of time to moderate.

Work Required

  • Figure out best way to mitigate the issue
  • Implement
## Background There are many spammers trying to comment on geo.coop They are being stopped, since anonymous comments must be approved, however a lot are coming in, taking a lot of time to moderate. ## Work Required * [ ] Figure out best way to mitigate the issue * [ ] Implement
cedewey commented 2020-02-27 23:36:12 +00:00 (Migrated from gitlab.com)

Hi @joshua_davis ,

We could try adding a CAPTCHA or other spam protection to comments, but it also seems like a lot of these comments are from legitimate humans who have very spammy causes. If that's right, it seems like requiring people create an account before being able to post comments would be the better approach. What do you think?

Hi @joshua_davis , We could try adding a CAPTCHA or other spam protection to comments, but it also seems like a lot of these comments are from legitimate humans who have very spammy causes. If that's right, it seems like requiring people create an account before being able to post comments would be the better approach. What do you think?
cedewey commented 2020-02-27 23:36:25 +00:00 (Migrated from gitlab.com)

assigned to @joshua_davis and unassigned @cedewey

assigned to @joshua_davis and unassigned @cedewey
cedewey commented 2020-02-27 23:41:42 +00:00 (Migrated from gitlab.com)

changed title from {-Spam filter check?-} to {+Address comments being spammed.+}

changed title from **{-Spam filter check?-}** to **{+Address comments being spammed.+}**
cedewey commented 2020-02-27 23:41:42 +00:00 (Migrated from gitlab.com)

changed the description

changed the description
joshua_davis commented 2020-03-04 20:37:28 +00:00 (Migrated from gitlab.com)

I'm not a fan of requiring account set-up to comment. Right now, the
spam is just an annoyance, so unless it gets considerably worse, I think
we just leave it for now. Ideally, we could just have a simple filter
that automatically rejects comment that starts with "<a href..." which
would deal with 80% of them.

Josh Davis
Content Manager
Grassroots Economic Organizing
geo.coop
406-274-3214

I'm not a fan of requiring account set-up to comment. Right now, the spam is just an annoyance, so unless it gets considerably worse, I think we just leave it for now. Ideally, we could just have a simple filter that automatically rejects comment that starts with "<a href..." which would deal with 80% of them. Josh Davis Content Manager Grassroots Economic Organizing geo.coop 406-274-3214
FreeScholar commented 2020-03-05 21:56:46 +00:00 (Migrated from gitlab.com)

Can we install http://drupal.org/project/antibot or configure honeypot differently? I do not have admin access to reconfigure the spam module.

Can we install http://drupal.org/project/antibot or configure honeypot differently? I do not have admin access to reconfigure the spam module.
FreeScholar commented 2020-03-05 21:58:53 +00:00 (Migrated from gitlab.com)

assigned to @mlncn

assigned to @mlncn
FreeScholar commented 2020-03-05 21:59:31 +00:00 (Migrated from gitlab.com)

unassigned @joshua_davis

unassigned @joshua_davis
FreeScholar commented 2020-03-05 22:01:35 +00:00 (Migrated from gitlab.com)

@mlncn There is more spam daily now, I get cc'd.
If you can give me access I can try to configure honeypot or if you can install drupal.org/project/antibot I think we can set that to filter out the spam that has links in it.

@mlncn There is more spam daily now, I get cc'd. If you can give me access I can try to configure honeypot or if you can install drupal.org/project/antibot I think we can set that to filter out the spam that has links in it.
mlncn commented 2020-03-06 23:02:03 +00:00 (Migrated from gitlab.com)

marked this issue as related to drutopia/drutopia_core#37

marked this issue as related to drutopia/drutopia_core#37
mlncn commented 2020-03-06 23:03:05 +00:00 (Migrated from gitlab.com)

@FreeScholar See also https://gitlab.com/drutopia/drutopia_core/issues/37

(Will just also add that my long-held dream is that creating an account happens seamlessly while leaving a comment, but would give the option to require a little more information making it easier to spot and possibly automatically stop spammers.)

@FreeScholar See also https://gitlab.com/drutopia/drutopia_core/issues/37 (Will just also add that my long-held dream is that creating an account happens seamlessly while leaving a comment, but would give the option to require a little more information making it easier to spot and possibly automatically stop spammers.)
FreeScholar commented 2020-03-10 21:05:31 +00:00 (Migrated from gitlab.com)

@mlncn I updated https://gitlab.com/drutopia/drutopia_core/issues/37 with this info: I changed the Honeypot to look for 'url' instead of 'site'. I did check the reports for the list of field names to be sure I was not blocking something valid. If this does not work, I suggest using the antibot module as Hannes does also, I have no spam issues with it on my sites.

@**mlncn** I updated https://gitlab.com/drutopia/drutopia_core/issues/37 with this info: I changed the Honeypot to look for 'url' instead of 'site'. I did check the reports for the list of field names to be sure I was not blocking something valid. If this does not work, I suggest using the antibot module as Hannes does also, I have no spam issues with it on my sites.
mlncn commented 2020-03-25 00:57:57 +00:00 (Migrated from gitlab.com)

mentioned in issue #110

mentioned in issue #110
mlncn commented 2020-03-25 01:09:24 +00:00 (Migrated from gitlab.com)

@FreeScholar's change seemed to help for a brief while, but we are back to being hammered as hard as ever.

I've enabled Antibot (it was already there @FreeScholar !) and we'll see if it helps.

Antibot requires that a person commenting have JavaScript enabled. Unfortunately, it provides no warning and no alternative approach to someone visiting the site without JavaScript or without JavaScript enabled.

@FreeScholar's change seemed to help for a brief while, but we are back to being hammered as hard as ever. I've enabled Antibot (it was already there @FreeScholar !) and we'll see if it helps. Antibot requires that a person commenting have JavaScript enabled. Unfortunately, it provides no warning and no alternative approach to someone visiting the site without JavaScript or without JavaScript enabled.
cedewey commented 2020-04-13 14:53:25 +00:00 (Migrated from gitlab.com)

unassigned @mlncn

unassigned @mlncn
cedewey commented 2020-04-13 14:53:44 +00:00 (Migrated from gitlab.com)

closed

closed
mlncn commented 2024-02-13 02:39:02 +00:00 (Migrated from gitlab.com)

marked this issue as related to #122

marked this issue as related to #122
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: geo/geo-coop#105
No description provided.