I'm sorry to say I didn't capture JSON returned in that "will not
favorite" case.
---
As an update, I've noticed that some tweets that were not favoriteable
before, now are.
Yours, for example, was subsequently correctly favorited via API:
http://twitter.com/al3x/statuses/967108203
Possibly related, the JSON API is now returning "favorited":false it
at least
some cases where it HAS created a favorite. For example. looking to
star
http://twitter.com/ttseco/statuses/967052986 I execute
http://twitter.com/favorites/create/967052986.json
it returns:
{"in_reply_to_status_id":null,"user":{"description":"I'm not a native
speaker and it snows.","url":"http:\/\/sites.google.com\/site\/ttseco
\/","name":"Theo
Tsecouras","protected":false,"profile_image_url":"http:\/\/
s3.amazonaws.com\/twitter_production\/profile_images\/44289712\/
tweet_normal.jpg","screen_name":"ttseco","followers_count":
270,"location":"Athens, Greece","id":
12217652},"favorited":false,"in_reply_to_user_id":null,"truncated":false,"id":
967052986,"source":"web","created_at":"Mon Oct 20 05:18:03 +0000
2008","text":"I don't think there's anyone in the world who likes to
eat Japanese more than I do except, maybe, Godzilla."}
But is in fact favorited and is returned that way from the web
interface.
So the earlier not favoriting (via API or Web) followed by now
favoriting some things that it indicates it didn't favorite suggests
that there's still something out of balance.
On Oct 20, 1:26 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote:
> What happens when you favorite them via the API and it doesn't take?
