15 | | UPDATE some 4 years later: the level of SPAM has fallen to effectively zero. The most effective method was not to display Timeline and ticket data to users who are not signed in. So, this fight spam project is complete. |
| 15 | UPDATE (August 2015) some 4 years later: the level of SPAM has fallen to effectively zero. The most effective method was not to display Timeline and ticket data to users who are not signed in. So, this fight spam project is complete. |
| 16 | |
| 17 | UPDATE (February 2018) some 3 years later: there is still some spammer activity, although by far not at the same rate as before. It is easy to forget the exact SOP for spam tickets. |
| 18 | |
| 19 | I now do the following: |
| 20 | 1. click on Modify Ticket, |
| 21 | 2. close the ticket as "spam" |
| 22 | 3. replace the short description line with the tag "[SPAM]" |
| 23 | 4. replace the entire text with the tag "[SPAM]" |
| 24 | |
| 25 | I had some automated process at some point in the past, which listed spammers with an sql query and marked them as spammers and/or removed the user entries from the htdigest file. This may need to be verified and documented. We could potentially record the IP addresses and block them from spammers. |
| 26 | |
| 27 | I wish I could send those spammers a retaliation bomb the next time they log in. |