Make sure you have "StatusMoodUpdate" in your activityTypes parameter.

At 12:45pm EDT (GMT-4) I changed the status on one account. In the activities ATOM feed of another account it reported the status published/updated time to be "2009-07-07T00:44:46Z". The actual GMT timestamp it was submitted should be "2009-07-07T16:44:46Z" (12:44 - (-04:00) = 16:44). The time being reported by the activities ...

Yes, I've transformed them all to the local time zone; that's why some of them are correct. The problem is that after the transformation some of the timestamps are incorrect (using the user home page as a reference), as outlined in the image and described in my original post.

http://pic.im/6a8 Timestamps returned from /users/{userid}/friends/status are not consistent with what I see on the MySpace friends-status page. In the picture linked above, you can see timestamps in my app that match those on the website (in green boxes). There's one timestamp-pair in this picture that doesn't match, highlighted in ...

According to the documentation for the activity stream for friends ( http://wiki.developer.myspace.com/index.php?title=Standards_for_Activity_Streams#Friend_Activities ), there is an optional parameter named "datetime". However, it seems to be referenced as lastRetrievalTimeStamp in the description of the error codes. Providing ...

I'm using py-oauth (http://code.google.com/p/oauth/), the urllib2 module of python (http://docs.python.org/library/urllib2.html), and some in-house code. However, I'm not sure how that's relevant- I'm talking about the data on the wire.

When accessing /v1/users/{my-userid}/friends with an expired OAuth token (because I unlinked the service from my MySpaceID), a 401 error is returned saying that the token is invalid or expired. When accessing /v1/users/{not-my-userid}/friends with a valid token, a 401 error is returned with a message saying something about not having ...