Changes between Version 2 and Version 3 of Ticket #16838, comment 30
- Timestamp:
- 12/04/2013 06:37:51 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #16838, comment 30
v2 v3 23 23 P.S. BTW, I recently wrote [https://github.com/hardcorewp/spam-blacklist a Spam Blacklist plugin] because I was getting over ~500 Akismet spam-tagged comments a day on a very low traffic blog. The plugin mined the 100,000+ spam I had received to create a **block** list by author, IP, email and URL, and if blocked it throws up a screen offering to whitelist the person if they contact me. 24 24 25 **It was a blunt force approach to solve ''my'' problem** and has many issues so it's not a general solution but the core concept was to **block** ''(vs. just spam-tag)'' what is easily identifiable as spam ''**on my unique blog**'' given the history of spam on my blog and the topics I write about, and then givingletting the commenter know their comment was blocked so they can contact me to allow them to be whitelisted.25 **It was a blunt force approach to solve ''my'' problem** and has many issues so it's not a general solution but the core concept was to **block** ''(vs. just spam-tag)'' what is easily identifiable as spam ''**on my unique blog**'' given the history of spam on my blog and the topics I write about, and then letting the commenter know their comment was blocked so they can contact me to allow them to be whitelisted. 26 26 27 27 So I think having a peer-to-peer spam plugin architected and built for core that takes into consideration each site's content could go a long way to finally resolving the ongoing spam problem in addition to satisfying the concerns raised by this ticket. FWIW.