Require captcha on Follow
There are a few ways to make the captcha less intrusive to users who are not abusing the Follow feature.
1. Only require captcha after someone has followed a large number of people (e.g. 200) in a short period of time
2. Only require captcha sporadically - e.g. after adding the 25th friend, after the 50th friend, etc.
Please consider adding this feature soon because we don't want Twitter to turn in to MySpace and there are clear signs that it's going in that direction.
The more people who like this idea, the more it gets noticed.
-
Inappropriate?Ideally, an image recognition CAPTCHA system. It hasn't been done well on a large scale yet, but it would be in keeping with Twitter's reputation for being fun. Rather than straining to guess whether it's a lowercase R or N, you get to solve a puzzle!
But I'd also take a wavy line through text before radically distorted characters.
1 person thinks
this is one of the best points
-
Inappropriate?William, great suggestion on using an image-based CAPTCHA. I'm sure that the creative minds at Twitter could come up with something fun, similar to what they have done with the down-time page.
-
Inappropriate?It's a great idea, although I fear it won't solve the problem completely, since people can still use the API, IM, or SMS to mass-follow people.
In fact, it's probably easier to mass-follow a lot of people using the three other "channels" since they're all text-only, and scripts can be written up to automate the 'follow' activity.
What do you suppose would be a good equivalent captcha for the API, IM, and SMS?
2 people think
this is one of the best points
-
Inappropriate?Great points mdy. Here are my thoughts on the three other channels that you mentioned. None of these are silver bullets, but these are the first things that come to mind.
For people who follow using IM and SMS, Twitter could detect if someone is trying to add a large number of followers in a short amount of time and send a reply asking a simple question - e.g. 'What is 1 + 2?' Sending a 3 back would allow the Follow to go through and be processed. An incorrect response would cause the Follow to fail and prevent any more Follow attempts for some period of time - e.g. 3 hours.
For the API I think the best they can do is throttle the Follower requests, similar to how they throttle the number of refreshes that someone can do in an hour. They should also attach some signature to the Follow request that indicates which client / API initiated the follow (maybe they are already doing this?). If some abuse is detected - e.g. the infamous TwitterAdder app (follows 20 random people; rinse, repeat), the creator of that application should be warned. If the warnings are ignored they should be completely blacklisted.
1 person thinks
this is one of the best points
-
Inappropriate?I hope that this suggestion never gets implemented. I don't want to be hindered if I go on a follow binge, and It goes against everything I like about the ability to tinker with twitter in different ways.
I haven't read the article, a link might be useful. -
Inappropriate?Mashable has a post today about using CAPTCHA when following new people.
http://snurl.com/24g5i
I left a comment over there asking people to come over to this discussion thread. Also, they have put up a survey asking:
"Is it time for Twitter to move aggressively to prevent spammy accounts?"
There results of the survey are here: http://snurl.com/24g5d
I’m optimistic
Loading Profile...





