You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Caveat: I'm still pretty new to Ruby and how the Twitter gem works so it's entirely possible I've done something wrong.
I've got a list of tweet IDs and I want to download a list of IDs of retweeters. I'm using the client.retweeters_ids() method and for the most part it works. However. it hangs on occasion on seemingly random tweet IDs:
eg twitter.com/statuses/743450000793927680
I'm looking at the actual tweet on my browser and nothing seems unusual. My understanding is all media in a tweet are simply link references. Otherwise I can't imagine why my script would hang (and on occasion, eventually resolve the content and proceed). I tried to debug and follow the stack trace but I don't have enough experience to understand what does what when, so I don't know if it's a gem issue (doubtful) or an API node issue (highly likely). Has anyone seen this?
Thanks for the attention,
Joe
The text was updated successfully, but these errors were encountered:
Caveat: I'm still pretty new to Ruby and how the Twitter gem works so it's entirely possible I've done something wrong.
I've got a list of tweet IDs and I want to download a list of IDs of retweeters. I'm using the client.retweeters_ids() method and for the most part it works. However. it hangs on occasion on seemingly random tweet IDs:
eg twitter.com/statuses/743450000793927680
I'm looking at the actual tweet on my browser and nothing seems unusual. My understanding is all media in a tweet are simply link references. Otherwise I can't imagine why my script would hang (and on occasion, eventually resolve the content and proceed). I tried to debug and follow the stack trace but I don't have enough experience to understand what does what when, so I don't know if it's a gem issue (doubtful) or an API node issue (highly likely). Has anyone seen this?
Thanks for the attention,
The text was updated successfully, but these errors were encountered: