Re: [twitter-dev] #newtwitter and the API
Brian, Thanks for the info. retweet_count The status object now includes a retweet_count field. When enabled this field will indicate the number of times a Tweet has been retweeted using the Twitter retweet function. What does when enabled mean? I have a couple of tweets for which I am trying to find out the absolute count of retweets. All I know is that the Twitter UI says 100+ retweets. But when I pull the status objects, retweet_count is blank. These tweets are from 2 days ago. Can someone point me to the best way to find out? Thanks! /damon -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] #newtwitter and the API
Hey Everyone,
Last week we announced #newtwitter, the new twitter.com built on top
of the Twitter API. For the Platform team in particular, this was an
important event. With #newtwitter using the API all users will become
API consumers, providing valuable feedback about issues they
encounter, helping us isolate and fix problems that are found.
When creating #newtwitter the value of this was clear. A heightened
level of visibility communication with our engineers enabled us to
reproduce and fix many of the API bugs you’ve encountered and reported
to us. #newtwitter makes it easier for us to concretely develop new
API features, giving other teams at Twitter an agile environment to
experiment with new ideas.
All of this combined resulted in many deployed fixes to the API -- and
some new features! Many of these have already been announced and are
already being used by many of you.
Listed below are the various changes and updates that have been made to the API.
URL format
--
The first important change is that URLs now have a new format. This
new format is part of the Javascript routing system used by
#newtwitter for page management. This means our website URLs now
contain a #! like this:
http://twitter.com/#!/themattharris
instead of:
http://twitter.com/themattharris
The two formats work on both versions of twitter.com so you don’t need
#newtwitter to use them.
There is more information about the #! URL format in Google’s article:
Making AJAX Applications Crawlable
http://code.google.com/web/ajaxcrawling/docs/getting-started.html
New methods
A number of new methods have been added to the API. Some of them can
be used now, while others only work if you have access to #newtwitter.
Some of these methods may be candidates for feature-specific rate
limiting in the future so be aware of the headers we return to you.
Like all REST API methods, the new ones live on
http://api.twitter.com. If you are not using this host please update
your code. The non-versioned API endpoints do not support the new
parameters or recent enhancements.
GET /1/account/totals.{format}
Requires authentication.
Returns the current count of friends, followers, updates (statuses)
and favorites of the authenticating user.
Example: twurl /1/account/totals.json
GET /1/account/settings.{format}
Requires authentication.
Returns the current trend, geo and sleep time information for the
authenticating user.
Example: twurl /1/account/settings.json
GET /1/users/suggestions/:category_slug/members.{format}
Does not require authentication.
Access the users in a given category of the Twitter suggested user
list and return their most recent status if they are not a protected
user.
Example: twurl /1/users/suggestions/technology/members.json
GET /1/direct_messages/show/:id.{format}
Requires authentication.
Returns a single direct message, specified by an id parameter. Like
the /1/direct_messages.{format} request, this method will include the
user objects of the sender and recipient.
Example: twurl /1/direct_messages/show/12345678.json
GET /1/statuses/retweeted_to_user.{format}
Does not require authentication, unless the user is protected.
Returns the 20 most recent retweets posted by users the specified user
follows. The user is specified using the user_id or screen_name
parameters. This method is identical to statuses/retweeted_to_me
except you can choose the user to view.
Example: twurl /1/statuses/retweeted_to_user.json?screen_name=twitterapi
GET /1/statuses/retweeted_by_user.{format}
Does not require authentication, unless the user is protected.
Returns the 20 most recent retweets posted by the specified user. The
user is specified using the user_id or screen_name parameters. This
method is identical to statuses/retweeted_by_me except you can choose
the user to view.
Example: twurl /1/statuses/retweeted_by_user.json?screen_name=twitterapi
GET /1/friendships/lookup.{format}
Requires authentication.
Returns the relationship of the authenticating user to the comma
separated list of up to 100 screen_names or user_ids provided. Values
for connections can be: following, following_requested, followed_by,
none.
Example: twurl
/1/friendships/lookup.json?screen_name=twitter,twitterapi,twittereng
POST /1/friendships/update.{format}
Requires authentication.
Allows you enable or disable retweets and device notifications from
the specified user. Valid values for enable are 't','1' or 'true'. All
other values are assumed to be false.
Example: twurl /1/friendships/update.json -d screen_name=twitterapi
-d device=true -d retweets=false
GET /1/lists/all.{format}
Requires authentication unless requesting for another user.
Returns all lists the authenticating or specified user subscribes to,
including their own. The user is specified using the user_id or
screen_name parameters. If no user is given, the authenticating user
is used.
Example: twurl /1/lists/all.json?screen_name=twitterapi
GET
Re: [twitter-dev] #newtwitter and the API
Thanks!! A somewhat philosophical question, with some practical
overtones. I've got a blog (self-hosted WordPress) and a LinkedIn
profile and, of course, a Twitter account. With #newtwitter, I'm
beginning to think I can ditch the blog and replace it with my Twitter
page - my microblog, as it were.
So I'm wondering how much customization someone can do to their
Twitter page now, and how much we might be able to expect in the
future? For openers, when I look at a Twitter page in #newtwitter,
there's a huge blank space on the lower right. Is there any way I can
use that space, either static or dynamic, without violating the TOS or
causing strain on the servers? Is there some way we'd be able to get
the kind of analytics from our Twitter pages that we can get from a
self-hosted WordPress blog?
--
M. Edward (Ed) Borasky
http://borasky-research.net http://twitter.com/znmeb
A mathematician is a device for turning coffee into theorems. - Paul Erdos
Quoting Matt Harris thematthar...@twitter.com:
Hey Everyone,
Last week we announced #newtwitter, the new twitter.com built on top
of the Twitter API. For the Platform team in particular, this was an
important event. With #newtwitter using the API all users will become
API consumers, providing valuable feedback about issues they
encounter, helping us isolate and fix problems that are found.
When creating #newtwitter the value of this was clear. A heightened
level of visibility communication with our engineers enabled us to
reproduce and fix many of the API bugs you’ve encountered and reported
to us. #newtwitter makes it easier for us to concretely develop new
API features, giving other teams at Twitter an agile environment to
experiment with new ideas.
All of this combined resulted in many deployed fixes to the API -- and
some new features! Many of these have already been announced and are
already being used by many of you.
Listed below are the various changes and updates that have been made
to the API.
URL format
--
The first important change is that URLs now have a new format. This
new format is part of the Javascript routing system used by
#newtwitter for page management. This means our website URLs now
contain a #! like this:
http://twitter.com/#!/themattharris
instead of:
http://twitter.com/themattharris
The two formats work on both versions of twitter.com so you don’t need
#newtwitter to use them.
There is more information about the #! URL format in Google’s article:
Making AJAX Applications Crawlable
http://code.google.com/web/ajaxcrawling/docs/getting-started.html
New methods
A number of new methods have been added to the API. Some of them can
be used now, while others only work if you have access to #newtwitter.
Some of these methods may be candidates for feature-specific rate
limiting in the future so be aware of the headers we return to you.
Like all REST API methods, the new ones live on
http://api.twitter.com. If you are not using this host please update
your code. The non-versioned API endpoints do not support the new
parameters or recent enhancements.
GET /1/account/totals.{format}
Requires authentication.
Returns the current count of friends, followers, updates (statuses)
and favorites of the authenticating user.
Example: twurl /1/account/totals.json
GET /1/account/settings.{format}
Requires authentication.
Returns the current trend, geo and sleep time information for the
authenticating user.
Example: twurl /1/account/settings.json
GET /1/users/suggestions/:category_slug/members.{format}
Does not require authentication.
Access the users in a given category of the Twitter suggested user
list and return their most recent status if they are not a protected
user.
Example: twurl /1/users/suggestions/technology/members.json
GET /1/direct_messages/show/:id.{format}
Requires authentication.
Returns a single direct message, specified by an id parameter. Like
the /1/direct_messages.{format} request, this method will include the
user objects of the sender and recipient.
Example: twurl /1/direct_messages/show/12345678.json
GET /1/statuses/retweeted_to_user.{format}
Does not require authentication, unless the user is protected.
Returns the 20 most recent retweets posted by users the specified user
follows. The user is specified using the user_id or screen_name
parameters. This method is identical to statuses/retweeted_to_me
except you can choose the user to view.
Example: twurl /1/statuses/retweeted_to_user.json?screen_name=twitterapi
GET /1/statuses/retweeted_by_user.{format}
Does not require authentication, unless the user is protected.
Returns the 20 most recent retweets posted by the specified user. The
user is specified using the user_id or screen_name parameters. This
method is identical to statuses/retweeted_by_me except you can choose
the user to view.
Example: twurl /1/statuses/retweeted_by_user.json?screen_name=twitterapi
GET
