Changes between Version 1 and Version 2 of Ticket #47926, comment 13
- Timestamp:
- 09/06/2020 12:55:42 AM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #47926, comment 13
v1 v2 1 1 The responses to this appears to fall into the old "we've always done it this way" trap without thinking about why it was done that way originally or whether it makes sense to continue to include it. I did a quick search on Google and found articles going back to at least 2011 of people asking how to disable this field because of the volume of spam it generates through WordPress sites. 2 2 3 I suspect that an analysis would find that this is the #1generator of spam on WordPress sites. And to what end? Is this a feature of the standard comment field that people clamor to have? No. If it went away or was disabled by default, would anyone miss it? Very few people I suspect. But because someone thought it was a good idea to have this field 1000 WordPress years ago, we're stuck having to install a plugin to disable a form field that serves very little purpose and exposes WordPress sites and their visitor to all kinds of bad content.3 I suspect that an analysis would find that this is the number one generator of spam on WordPress sites. And to what end? Is this a feature of the standard comment field that people clamor to have? No. If it went away or was disabled by default, would anyone miss it? Very few people I suspect. But because someone thought it was a good idea to have this field 1000 WordPress years ago, we're stuck having to install a plugin to disable a form field that serves very little purpose and exposes WordPress sites and their visitor to all kinds of bad content. 4 4 5 5 Isn't it time to have a discussion of whether this is worth all the problems that this form field causes?