Ah, The Battles with Spam
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 back-end–using ThnLnks with those domain names redirects to a spam-page.
One fall-out from this is that people clicking on spam links immediately after we catch them will go to a ThnLnk-branded page, and so people will think that ThnLnk is sending the spam.
But we’re not. I have to figure out a way to get around this misconception. I think it’s just being proactive about blocking domains as soon as they start cropping up.
You can see the spam-warning page here.