Thanks for pointing this out. We likely have too aggressive of caching in the response to that call. If you get a successful return code from the friendships/destroy end point, you should likely assume the call was successful, regardless of the response. I'll look into this.
If you have a capture of the specific instance where you received this cached response back, you may want to file a bug with the details at http://code.google.com/p/twitter-api/ Thanks, Taylor On Mon, Aug 23, 2010 at 7:12 AM, funkyboy <cesareroc...@gmail.com> wrote: > Hello, > > I am playing with the api. > When I unfollow somebody (friendships/destroy) the info returned is > incorrect, that is > following = 1. > > The opposite works correctly, that is when I follow (friendships/ > create), the info > returned is correct, following = 1. > > Is it a bug? > I am using json format. > > Thanks > > -c. > > ps: After unfollowing if I load user profile (/users/show) the info > returned is correct, > I am not following him. >
