hat it was a failure - but in fact, the posts make it through. This
means I report falsely and people will try and post again - often
ended up with double/triple posts.
Any ideas?
Spode
--
Subscription settings:
http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
tp://search.twitter.com/search.json?q=JournoTwit&rpp=100&since_id=
Run it with no since_id and it works. Then straight away run the
original query...
http://search.twitter.com/search.json?q=JournoTwit&rpp=100&since_id=5402169538
And you get the expected 4 results.
What's going on?
Spode (journotwit.com)
This is STILL a problem. I have a possible theory on what is happening
at a server level.
The search phrases I am using are quite specific - i.e, I may well be
the only person in the world searching for that particular string.
First Call - Because it has a since_id, it assumes that it checks
ag
I've created a screen-cam video to illustrate this problem and how
much of a problem it is...
http://www.youtube.com/watch?v=3a-88MSdqes
The last video I posted was garbled - but I've re-done it.
http://www.youtube.com/watch?v=qedssv3cBCA
rgoing the same transformation?
Spode
On Aug 23, 11:45 pm, Matt Harris wrote:
> Hey Developers!
>
> A while ago we let you know about the new Tweet ID generation service
> we developed called Snowflake and published the source code so you
> could get familiar with how it works. T
