- Issue created by @chrisfromredfin
- πΊπΈUnited States Jacqui.Tenderwolf
I am working on this issue as part of DrupalCon Pittsburgh.
- Status changed to Needs review
over 1 year ago 6:03pm 7 June 2023 - Status changed to RTBC
over 1 year ago 11:46pm 6 July 2023 - πΊπΈUnited States cmah
This is sufficiently non-technical and is less than 200 characters - great!
- Status changed to Needs review
3 months ago 2:48am 13 September 2024 - πΊπΈUnited States leslieg
Current proposal seems too general and starts with the Module name. Doesn't distingush this module from other spam blocking ones
Suggesting: "Uses both the honeypot and timestamp methods of deterring spam bots from completing forms on your Drupal site"
- πΊπΈUnited States rishi kulshreshtha
Looks good, how about?
Helps stop spam on Drupal sites by adding hidden fields to forms. Bots fill these fields by mistake, which alerts the system to block them, while real users aren't affected.
- Status changed to RTBC
3 months ago 3:17pm 13 September 2024 - πΊπΈUnited States leslieg
New description meets requirements. Moving to RTBC
- Status changed to Fixed
3 months ago 2:20am 16 September 2024 - πΊπΈUnited States tr Cascadia
What was wrong with the original summary description?
Honeypot uses both the honeypot and timestamp methods of deterring spam bots from completing forms on your Drupal site. These methods are effective against many spam bots, and are not as intrusive as CAPTCHAs or other methods which punish the user.
The module currently supports enabling for all forms on the site, or particular forms like user registration or password reset forms, webforms, contact forms, node forms, and comment forms.
The new suggested version is actually wrong in the case of the timestamp strategy - there is no hidden form field to fill out - and skips the all-important "philosophy" of controlling spam in a way that is not intrusive and does not punish the user.
- πΊπΈUnited States tr Cascadia
Can I get an answer please? Or do module maintainers not have a say in any of this?
- πΊπΈUnited States chrisfromredfin Portland, Maine
Hi tr -
Our process is to suggest something to the maintainer, and put that suggestion in the maintainer's queue. They are welcome to provide absolutely any short description that they like. HOWEVER, please note that your suggestion is much larger than 200 characters, and we are trying to say what the module does in 200 characters or less, in a way that speaks to our target audience (non-technical users like "Sarah" from Dries's Starshot demo in his latest Driesnote). This way, the entire answer to the question "what does this module do" fits on the card in Project Browser.
So in short, please do whatever you would like for your summary description! If it's more than 200 characters, it will be truncated on the card view and shown with an ellipsis.
You can refer to our Handbook Page for Maintainers β for more info.
Automatically closed - issue fixed for 2 weeks with no activity.