Yeah I realized shortly after writing that that I was already handling this bug, and it was only that I just happened to be noticing it again and thinking that it was a recent occurrence :-)
On Apr 15, 12:14 pm, btjones <btjo...@gmail.com> wrote: > FYI, looks like this bug was submitted quite a while ago. > > http://code.google.com/p/twitter-api/issues/detail?id=855&q=favorites... > > On Apr 14, 5:47 pm, btjones <btjo...@gmail.com> wrote: > > > > > This is happening for me as well. > > > The problem can be easily recreated with the Twitter API > > explorer:http://twitapi.com/explore/favorites-create/http://twitapi.com/explor... > > > -Brandon > > > On Mar 30, 7:26 pm, "Orian Marx (@orian)" <or...@orianmarx.com> wrote: > > > > It seems thatfavorites/createandfavorites/destroy are no longer > > > returning tweets with a properly updated <favorited> node. If I try to > > > favorite a tweet, theresponsecomes back with favorited = false, but > > > if I re-fetch the tweet immediately after it comes back as favorited = > > > true. It was not working like this until very recently. > > > > Anybody else getting this? > > > > Thanks, > > > @orian -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
