| 1 | The following attempts to document and explain the anti-abuse system in |
| 2 | TightURL. Ideally abuse is kept out of the database to begin with, but in |
| 3 | many cases it must be dealt with afterward. |
| 4 | |
| 5 | 1. Rejection of bad bots thanks to Bad Behavior. |
| 6 | |
| 7 | 2. Rejection of invalid URLs. Since garbage in the database is abusive |
| 8 | to the operator of the TightURL service, we attempt to keep junk out. |
| 9 | |
| 10 | 3. Rejection of blacklisted file extensions. Much abuse involves getting |
| 11 | someone to run a Windows executable. A set of abused extensions is |
| 12 | provided, and can be updated by the site administrator. |
| 13 | |
| 14 | 4. Rejection of locally blacklisted sites. |
| 15 | |
| 16 | 5. Rejection of URI blacklisted sites. |
| 17 | |
| 18 | 6. Rejection of links to known redirector sites. |
| 19 | |
| 20 | 7. Re-checking accepted URLs for those who run the "killbot". |
| 21 | |
