Any ETA for the following. Its been a while.
> http://code.google.com/p/twitter-api/issues/detail?id=1214
>
> http://code.google.com/p/twitter-api/issues/detail?id=1274

On Tue, Jan 5, 2010 at 12:30 AM, John <munz...@gmail.com> wrote:

> I've noticed that this is not always the case.
>
> If I retweet an older tweet it shows up as a new tweet in
> home_timeline. But if I retweet a tweet on the first page, call
> home_timeline, it doesn't contain the retweet (only visible under
> retweeted_by_me). Same occurrance happens on twitter.com but
> twitter.com knows that i've retweeted (the difference between the API
> and twitter).
>
> I guess if it did show up that could also be a solution instead of
> needing to add new flags as I suggested above.
>
> Basically what you were saying in your first post:
>
> Quote:
> For your second point
> I am not seeing the retweeted status in my home_timeline for some
> reason...
>
>
> On Jan 4, 1:06 am, srikanth reddy <srikanth.yara...@gmail.com> wrote:
> > home_timeline also includes both.
> > For user retweeted status i would just check
> if(status[i].retweeted_status
> > != null and status[i].user.screen_name == currentuser)
> > But the problem comes when you have friends redundant status i.e
> > status[i].retweeted_status != null and status[i].user.screen_name !=
> > currentuser. This friend's status appears in your home time line even
> after
> > you retweet. If you try to retweet this it will throw an error as this
> has
> > already been retweeted by you.
> > To prevent this you have to manually disable friends 'retweets' appearing
> in
> > your home_timeline (this option is available in web only and this has to
> be
> > done for each and every user.Currently this is also not working)
> >
> > Anyhow these issues are already reported here
> >
> > http://code.google.com/p/twitter-api/issues/detail?id=1214
> >
> > http://code.google.com/p/twitter-api/issues/detail?id=1274
> >
> > On Mon, Jan 4, 2010 at 2:24 AM, John <munz...@gmail.com> wrote:
> > > I understood you since the beginning. It doesn't feel redundant to me,
> > > I'm pretty sure that is intended functionality.
> >
> > > Even if they disappeared from "retweeted by others" there still needs
> > > to be a way to know if you can undo regular tweets you've retweeted
> > > since they don't include any "retweeted" information in the other
> > > timeline methods (home_timeline etc).
> >
> > > On Jan 3, 11:40 am, srikanth reddy <srikanth.yara...@gmail.com> wrote:
> > > > I am not sure i expressed it clearly. Pardon my lang
> >
> > > > <<"They will only disappear if your friends undo.">>
> >
> > > >  It is true that they will disappear if your friends undo. But my
> point
> > > is
> > > > that they should also disappear(not instantly) from 'Retweets by
> Others'
> > > > when you retweet them from 'Retweets by Others'  tab( coz it will be
> > > added
> > > > to 'retweets by me' ) and keeping them in 'Retweets by Others' is
> just
> > > > redundant. If you refresh your 'Retweets by Others' tab you will see
> the
> > > > tweet as retweeted by you and your friend and you have the option of
> > > undoing
> > > > it. But this undoing is possible only in web. From API point of view,
> if
> > > > these statuses are removed from 'retweets by others'  the moment the
> user
> > > > retweets them then undo is simple (just delete the status id obtained
> > > from
> > > > the statuses/retweet response ). This type of undoing is done only
> > > > instantly i.e u cannot undo if you refresh the tab.( retweeted_to_me'
> now
> > > > does not include that status)
> >
> > > >  This is true for other timeline methods as well. But if keeping this
> > > > redundant data is intended then twitter has to make changes to the
> > > payload
> > > > (i.e add the retweeted_by_me flag)  and provide destroy/retweet
> methods
> > > as
> > > > suggested by you). Hope i am clear now.
> >
> > > > On Sun, Jan 3, 2010 at 10:14 AM, John <munz...@gmail.com> wrote:
> > > > > They will always remain even if you undo. They will only disappear
> if
> > > > > your friends undo.
>

Reply via email to