beginning to see numerous posts about value of twitter feeds by twalue. it is always fun to see the imaginary prices our valuable musings might capture on the open market, but i wonder why anyone would grant access, to a private account, for an application such as this?
conceivably, they utilize some method of calculation that takes into consideration your: length of time on twitter, followers, following, number of tweets/retweets, etc. to come up with the final price tag. all of this information, however, is accessible without having to hand over the keys to your twitter account. so the question remains, why does twalue require your user name and password to create this fun fact?
in the past several of these sites have proved to be phishing expeditions so i would caution any person looking to have a little fun during the day to never hand this information over to any site you do not trust.
considering twalue is a new site, creation for the domain is 10 Sep 2010 18:29:00 (according to whois data), it hardly has the length of service to trust with sensitive information. also, since there have been numerous phishing, clickjacking and other exploits across the internets recently, specifically targeting twitter and facebook, it confounds me why anyone would grant this type of access to a new site.
yesterday, when i checked the whois data, the site was registered to a name, with an address in the united kingdom – wished i had saved it for inclusion in this post. today, however, checking the whois data, now has that information hidden by whoisguard. twalue’s service may be entirely benign, but in today’s atmosphere, granting this type of access to a private account is really just inviting trouble.
posted a tweet to david barker, @deedeebeeisme, about this very issue and he responded back lightning fast.
the reason they have you sign in is to make it easier to post the final value of your account as a tweet, as well as some api rate limits. i would not agree with the former, but the latter is an issue with twitter, their api and limits that potentially expose users to phishing scams.
if twitter is serious about third-party developers and applications that utilize their api as well as protecting their users, they might want to look into better, less intrusive ways to allow the manipulatation/mash-up of their data.