I am working on a project to read tweets and display them on an LCD for use in an office. I have got it working a few times but it is not consistent as it sometimes fails to get the tweets. I came to realize that this is caused by twitter itself by limiting the number of requests/hr from every IP address. Initially I was reading the twitter page every 1 minute and had to reduce it to every 5 minutes but still no progress.
Through research I came to know that running my project behind a proxy was the cause. This basically causes thousands of users to share the same IP which means that my IP was almost always rate limited. I then found out that using OAuth application can increase the number of request/hr to 350 but have failed to do this since arduino twitter library that uses this application only handles posting tweets and not reading them.
but using an existing domain like twitter wouldn't it be much easier
If twitter didn't need to guard against twits overpowering its server, yes. But, you would have complete control over your server, and could implement whatever policies you liked. Authorization, IP limits, etc.
But, you would have complete control over your server, and could implement whatever policies you liked. Authorization, IP limits, etc.
I know but there isn't much time to do this and I am not familiar with the whole process.I will scratch my head for days i guess to figure out another possible way out.
Through research I came to know that running my project behind a proxy was the cause. This basically causes thousands of users to share the same IP which means that my IP was almost always rate limited.
Not sure that is correct thinking about thousands of users using the same IP address. Anyhow, twitter is probably limiting service because too many twit heads are trying to make twitter bots instead of using the service like origionally intended.