On Thu, Feb 25, 2010 at 00:06, srikanth reddy <srikanth.yara...@gmail.com>wrote:

> Combine retweet timelines? But 'Retweets by Me' returns only 20( as per
> doc) and other time lines return more.
>

And has a count parameter that can return up to 200.


> <<Plus what does it matter if a user tries to retweet a status they have
> already retweeted? There is no adverse effect>>
>
> Twitter returns 403 since it has already been retweeted. There is no
> adverse effect as such. Just UX concern.
>

I've not tested it so I can't say how useful the response is.


> Hmm that bug is in NEW state.
>
> On Thu, Feb 25, 2010 at 4:46 AM, Abraham Williams <4bra...@gmail.com>wrote:
>
>>
>>
>> On Fri, Feb 19, 2010 at 02:44, srikanth reddy <srikanth.yara...@gmail.com
>> > wrote:
>>
>>> @Abraham
>>> One thing you cant do with the API is
>>> Preventing users from retweeting their friends retweet which has already
>>> been retweeted by the user .To check this
>>> Go to "Retweets By Others" tab just retweet a friend's retweet and
>>> refresh your tabs. In web interface that tweet will appear in both "Retweets
>>> By Others" and "Retweets By Me" tabs and you will be given an option to undo
>>> the retweet in both tabs. But you cannot do the same with the API There is
>>> no way a user can find his retweeted entry in "Retweets By Others" directly
>>> (with one call)
>>>
>>> To fix this either
>>> 1) we should check the original retweet ids in both "Retweets By Others"
>>> and "Retweets by Me" (i.e make 2 calls). Not only is this resource/time
>>> consuming but it is highly unreliable. Some times "Retweets by Me" entries
>>> may not overlap with the entries from "Retweets By Others" due to the data
>>> size limit (200)
>>>
>>> Or
>>> 2)Twitter should add some flag like retweeted_by_me to the pay load for
>>> "Retweets By Others" which is really helpful
>>> This bug has been left untouched for a long time.
>>>
>>
>> It is possible from the API. You just have to combine the different
>> retweet timelines. As I said: "It might take a number of API calls to
>> collect all the data but it is all there"*
>>
>> Plus what does it matter if a user tries to retweet a status they have
>> already retweeted? There is no adverse effect.
>>
>> Abraham
>>
>> *besides the bug that has no open bug report.
>>
>> --
>> Abraham Williams | Community Advocate | http://abrah.am
>> Project | Out Loud | http://outloud.labs.poseurtech.com
>> This email is: [ ] shareable [x] ask first [ ] private.
>> Sent from Seattle, WA, United States
>>
>
>


-- 
Abraham Williams | Community Advocate | http://abrah.am
Project | Out Loud | http://outloud.labs.poseurtech.com
This email is: [ ] shareable [x] ask first [ ] private.

Reply via email to