Some Twitter::Tweet properties doesn't work #419

Closed
mindhells opened this Issue Jun 24, 2013 · 8 comments

Comments

Projects
None yet
3 participants
@mindhells

favoriters, repliers and retweeters are always set to nil.

@stve

This comment has been minimized.

Show comment Hide comment
@stve

stve Jun 25, 2013

Collaborator

Can you explain in a little more detail the problems you are experiencing, a tweet id, for instance, would be helpful to troubleshoot. Thanks.

Collaborator

stve commented Jun 25, 2013

Can you explain in a little more detail the problems you are experiencing, a tweet id, for instance, would be helpful to troubleshoot. Thanks.

@mindhells

This comment has been minimized.

Show comment Hide comment
@mindhells

mindhells Jun 25, 2013

As far as I know this properties are filled out when you use the
undocumented status_activity to get the tweet info which response includes
them. The problem is this service is not working anymore and there's no
workaround.
El 25/06/2013 17:35, "Steve Agalloco" notifications@github.com escribió:

Can you explain in a little more detail the problems you are experiencing,
a tweet id, for instance, would be helpful to troubleshoot. Thanks.


Reply to this email directly or view it on GitHubhttps://github.com/sferik/twitter/issues/419#issuecomment-19984970
.

As far as I know this properties are filled out when you use the
undocumented status_activity to get the tweet info which response includes
them. The problem is this service is not working anymore and there's no
workaround.
El 25/06/2013 17:35, "Steve Agalloco" notifications@github.com escribió:

Can you explain in a little more detail the problems you are experiencing,
a tweet id, for instance, would be helpful to troubleshoot. Thanks.


Reply to this email directly or view it on GitHubhttps://github.com/sferik/twitter/issues/419#issuecomment-19984970
.

@sferik sferik closed this in 77cc963 Jun 25, 2013

@sferik

This comment has been minimized.

Show comment Hide comment
@sferik

sferik Jun 25, 2013

Owner

Since this breaks the public API, we will need to wait to ship this change until version 5.0 is ready. Returning nil for all these methods is not ideal but it’s better than a NoMethodError.

Owner

sferik commented Jun 25, 2013

Since this breaks the public API, we will need to wait to ship this change until version 5.0 is ready. Returning nil for all these methods is not ideal but it’s better than a NoMethodError.

@mindhells

This comment has been minimized.

Show comment Hide comment
@mindhells

mindhells Jun 25, 2013

Just to confirm if you are working in to get that data from another source
or just removing the properties.
Thank you so much
El 25/06/2013 18:12, "Erik Michaels-Ober" notifications@github.com
escribió:

Since this breaks the public API, we will need to wait to ship this change
until version 5.0 is ready. Returning nil for all these methods is not
ideal but it’s better than a NoMethodError.


Reply to this email directly or view it on GitHubhttps://github.com/sferik/twitter/issues/419#issuecomment-19987709
.

Just to confirm if you are working in to get that data from another source
or just removing the properties.
Thank you so much
El 25/06/2013 18:12, "Erik Michaels-Ober" notifications@github.com
escribió:

Since this breaks the public API, we will need to wait to ship this change
until version 5.0 is ready. Returning nil for all these methods is not
ideal but it’s better than a NoMethodError.


Reply to this email directly or view it on GitHubhttps://github.com/sferik/twitter/issues/419#issuecomment-19987709
.

@stve

This comment has been minimized.

Show comment Hide comment
@stve

stve Jun 25, 2013

Collaborator

Sadly it sounds like this is a casualty of twitter API 1.1, if its not available via either documented or undocumented API's then we can't possibly support it in this library either. @sferik has removed the properties. If you happen upon another way to access them, feel free to point us to it! Cheers.

Collaborator

stve commented Jun 25, 2013

Sadly it sounds like this is a casualty of twitter API 1.1, if its not available via either documented or undocumented API's then we can't possibly support it in this library either. @sferik has removed the properties. If you happen upon another way to access them, feel free to point us to it! Cheers.

@sferik

This comment has been minimized.

Show comment Hide comment
@sferik

sferik Jun 26, 2013

Owner

@mindhells If you want this API, you might want to politely suggest that Twitter add it to API v1.1 on the discussion forum. Good luck! 🍀

Owner

sferik commented Jun 26, 2013

@mindhells If you want this API, you might want to politely suggest that Twitter add it to API v1.1 on the discussion forum. Good luck! 🍀

@mindhells

This comment has been minimized.

Show comment Hide comment
@mindhells

mindhells Jun 26, 2013

I suspect they're going to ignore that request according to the policy of making things hard to developers... anyway I'll try.
By the way and talking about properties, the identifiers with _str suffix are not mapped while they are loaded into the values hash, ie: in_replay_to_status_id_str (tweet) id_str (tweet and user)
Rgds

I suspect they're going to ignore that request according to the policy of making things hard to developers... anyway I'll try.
By the way and talking about properties, the identifiers with _str suffix are not mapped while they are loaded into the values hash, ie: in_replay_to_status_id_str (tweet) id_str (tweet and user)
Rgds

@sferik

This comment has been minimized.

Show comment Hide comment
@sferik

sferik Jun 27, 2013

Owner

The omission of id_str and in_replay_to_status_id_str was intentional. Those properties are only necessary in languages that don't support large integers, such as JavaScript. If you need a string representation of an integer value in Ruby, you can simply call the to_s method.

Owner

sferik commented Jun 27, 2013

The omission of id_str and in_replay_to_status_id_str was intentional. Those properties are only necessary in languages that don't support large integers, such as JavaScript. If you need a string representation of an integer value in Ruby, you can simply call the to_s method.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment