Hey there! tweetscan is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What are you doing? Join today to start receiving tweetscan's tweets.

Already using Twitter
from your phone? Click here.

tweetscan

@Fancy_Lad Nothing specifically from the follower action but you could do a historical search for "started following" "now following" etc. 2:17 PM Nov 4th from web in reply to Fancy_Lad
@bingomar There is no historical API yet but if you are interested in specific queries, email datasupport @ tweetscan.com 4:08 PM Oct 23rd from web in reply to bingomar
Our host is experiencing network problems so we are down. We're not alone but should be up soon. 10:25 PM Oct 9th from web
@kevin_m_shannon We don't use email for login. Try http://tweetscan.com/main.php with your username(not email) and password. Thanks. 11:43 PM Oct 3rd from web in reply to kevin_m_shannon
Would you like to search 235 million Twitter messages? Subscribe to our Historical Search going back to 2007. http://tweetscan.com/main.php 5:26 PM Oct 1st from web
The service is now back online. Thanks everyone for your patience. 5:23 PM Oct 1st from web
Our database server is being moved. Expected to be up tomorrow. Thanks for your patience. 12:32 PM Oct 1st from web
@abovegroundmag Seems very doable. Email datasupport@tweetscan.com with the terms/user you need. 12:16 PM Sep 3rd from web in reply to abovegroundmag
@abovegroundmag yes, what is your question? 9:52 AM Sep 3rd from web in reply to abovegroundmag
@jayfresh Thanks for that link. We are not using that but ours combines results from our index with Twitter API calls. TiddlyWikis do rock. 10:16 AM Aug 28th from web in reply to jayfresh
@monkchips Oauth is at the top of the list to implement. Provides interesting possibilities as well so thanks for raising the profile. 10:14 AM Aug 28th from web in reply to monkchips
@EdgarMontano Our indexer must have missed your tweets back when they were posted. This could be due to chance or if you had protected them. 7:48 PM Aug 16th from web in reply to EdgarMontano
@joncanady Yes they are. Your mission if you choose to accept it is to find them. Hint: you already mentioned how they might be found. 3:45 PM Aug 13th from web in reply to joncanady
@joncanady No, early on it was scraping the pt which worked quite well for a time but now Twitter provides feeds that do not use API reqs. 10:41 AM Aug 13th from web in reply to joncanady
@joncanady We've been operating a search engine for almost 2 years so the index has been built over time and never required any API reqs. 10:35 AM Aug 13th from web in reply to joncanady
@Despil We were having trouble with certain requests but this is fixed now. Try it and if it isn't done within 10 minutes, please msg again. 10:34 AM Aug 13th from web in reply to Despil
@battypip Thanks for that message...backups being generated again. Check on previously requests at https://www.tweetscan.com/d... 1:15 PM Aug 12th from web in reply to battypip
@jrick Historical search makes use of our own index that we've built over 2 years. It's not complete but it's the best we know of. 3:05 PM Aug 11th from web in reply to jrick
@jrick That is a separate service called Historical Search. It's $20. You just have to register and upgrade to a 1 year membership. 10:38 AM Aug 11th from web in reply to jrick
@alex_mayorga Thanks for the suggestion. Definitely looking to implement OAuth soon. Are you aware of a reference implementation? 10:21 AM Aug 11th from web in reply to alex_mayorga