New Post: Best Practise for contiguous collection

I wonder if Twitter is reliable enough to do this.

I have a set of 44 Tweet IDs which I had previously received via filterstream for the pattern "golden". When I pass the first and the last into the routine, it only comes back with a set of 40. Could there be some difference between how filterstream and Search work ?

The ids I got from filterstream for "golden" are :

493791589899444224
493791614364430336
493791641472225280
493791644253425666
493791648925503488
493791657687781376
493791658870571010
493791672120008706
493791672291966976
493791677480325120
493791679506161664
493791684913012736
493791692873428993
493791696027918336
493791704794021888
493791706840449025
493791710129164288
493791737798983681
493791742454693888
493791748943282177
493791755725066241
493791756946014208
493791758484918272
493791760158445568
493791766978363393
493791784414101504
493791788339978241
493791793608404993
493791794669178881
493791800977408001
493791810922098688
493791817905995777
493791822423269376
493791828370792448
493791835060318209
493791837770231808
493791855704670208
493791860255916033
493791862893735936
493791866437918720
493791872515465216
493791873115652096
493791894065786881

I passed these parameters in
RestorePreviousDataBetween(493791589899444224, 493791894065786881)
and get this output

Restoring missed data...
Waiting for Twitter Search API to index the tweets that have been missed...
Twitter Search API successfully indexed the tweets...
Restoring 40 tweets
All tweets have now been restored!


This is an example of a tweet ID which is within the range above and that filterstream did pick up, but search did not :

{'493791873115652096', 28/07/2014 17:15:31, 'Gursiman Feilden', 'http://t.co/XosE14ELKF 820 «Golden Girls» Strip Boutique', 'English', '31/07/2014 10:25:56'}


Your thoughts please Linvi.
Thanks again.