If you would have taken a look deeper into the sourcecode of twitter you would have seen how efficiently it works.

And there is really no difference in how often you can use the twitter api compared to checking out the page content which requires a complete reload every time because Twitter limits both the same way to a maximum of 150 requests per hour (http://apiwiki.twitter.com/Rate-limiting). Sure, if you try it yourselfe, you can just reload the page as fast as you want, but after doing this 150 times, you will see that by as you said 6 times a minute you will be blocked for the rest of the hour after reloading so often for 25 minutes! (150/6=25)

Now tell me: How do you want to control your computer with your program if your twitter account is blocked?

You didn’t really listen to what your math-teacher in school told you, did you?

Just trying to keep you on your toes.

Even though I now realize that TweetMyPC is far better than any program I can make, I am continuing my project just for fun. For those of you who did not see my last post, the idea was to get tweet updates through screen-scraping instead of through Twitter’s API.
The reasons this would be good are:
– The program doesn’t need your password
– It can get updates at faster intervals
– It is against Twitter’s terms of service…
– …so therefore it is funner
But there are also the bad things:
– It takes more CPU
– You can’t use a private account
– It is less reliable

Again, I will attach what I have so far. It is still in super rough shape and I am only in high-school so my coding skills are, shall we say, less than exemplary.(Basically it’s pretty sloppy.)
However, if you are interested at all, I will include the .exe and the C# source so you can see what’s going on.
Please comment, or email me, if you have suggestions/criticisms.
At least let me know if I’m making a fool of myself.

Download:http://www.mediafire.com/?tdgjw02jmmw

(BTW: Only tested on my WIN-XP and you need .NET framework installed)