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
64bit ids are not the same as id_str. Twitter will overflow the id field.
As twitterizer uses decimal as datatype already it should be 64bit safe.
id_str is the longterm post-64bit field. I dont think _str in twitterizer
is not correctly implemented yet.
Are the two the same / equivalent?
—
Reply to this email directly or view it on GitHub.
Does this library handle 64-bit user-ids ?
I ask since https://blog.twitter.com/2013/64-bit-twitter-user-idpocalypse mentions using id_str to get this support. When I look at https://github.com/Twitterizer/Twitterizer/blob/develop/Twitterizer2/Methods/User/TwitterUser.cs I see str_id being used rather than id_str.
Are the two the same / equivalent?
The text was updated successfully, but these errors were encountered: