I cleaned up about 100 lines of code, which should make things a *little* bit faster. Mostly housekeeping, not much in the way of actual optimization.
I also implemented some more spam control, allowing ThnLnk to ban IPs and to monitor ThnLnks that are being used at a suspiciously high rate.
I’ve been working with my fantastic hosting company, DreamHost, who first warned me of the spam generated via ThnLnk, to control the creation of spam links through ThnLnk.
I’ll be implementing a sizable slew of them by the week’s end, and hopefully this will help stem the usage of ThnLnk for despicable purposes by the one [...]
There has recently been a rash of probably one spammer who has been active in sending out links with ThnLnk URLs. I’ve just implemented a banning procedure for URLs and domains for which spam is associated. It bans the domains on the front-end–i.e., you can’t create ThnLnks for those domains–as well as on the [...]
One of the main purposes of ThnLnk is to create some credibility and accountability in URL shortening services. By including the domain name in the URL users can quickly check the “value” of a URL redirect based upon the domain.
So there is a bit of semantic and social protection against spam links. But it’s not [...]