sending bad since_id in twitter API calls

Open snarfed opened this issue 10 years ago • 5 comments

specifically, we're sending since_id=587735912303329281_favorited_by_2788841, which is one of our synthetic ids, instead of a normal tweet id. e.g. this log:

Collected params: [(u'q', u'@gRegorLove'), ...(u'since_id', u'587735912303329281_favorited_by_2788841'), ...]
...
Fetching https://api.twitter.com/1.1/search/tweets.json?...&since_id=587735912303329281_favorited_by_2788841

maybe related to #386. cc @gRegorLove.

Apr 14 '15 20:04 snarfed

this is harmless, everything still works. deprioritizing.

Apr 22 '15 04:04 snarfed

hard to check whether this is still happening, since the google cloud log browser doesn't support regexp search.

Mar 16 '17 21:03 snarfed

still happening.

Jan 02 '18 23:01 snarfed

still happening. easily searchable with text:_favorited_by_ in the log browser.

Jul 16 '20 18:07 snarfed

still happening.

Apr 15 '21 14:04 snarfed

Obsolete, Bridgy Twitter is dead.

Apr 06 '23 21:04 snarfed