I just want to be clear.
Is it cool if I store data coming from the twitter API and store it on
my own database? (messages, twits, etc.)?
I find the API rate limit of 100 an hour too restrictive.
Search the archives and you'll find that for the most part it's
perfectly fine. However sending an email off to a twitters legal team,
with a better description of what your planning to do would not go
astray.
On Sun, Jan 11, 2009 at 4:16 PM, danny dco...@gmail.com wrote:
I just want to be
Why not use this? – http://apiwiki.twitter.com/REST+API
+Documentation#exists
On Jan 11, 1:23 pm, Daniel daniel.mcken...@gmail.com wrote:
Hi there,
I was on my way to posting this as a feature request, but thought I'd
first discuss it here first in case there is some other way of doing
what
I am running a script that polls the public timeline API method, and I
am noticing that on almost every poll, I am receiving a duplicate
tweet within the results. Can someone please confirm before I open a
defect?
I am using the following method:
http://twitter.com/statuses/public_timeline.json
