[NEW] /account/update_location.[xml|json] - sets the location for the authenticated user to the string passed in a "location" parameter. Nothing fancy, no geocoding or normalization. Just putting this out there so developers can start playing with how geolocation might fit into their Twitter applications.
[NEW] You can add do /friendships/create/example_user.xml?follow=true to turn notifications on for a user as well as befriend/follow them.
[NEW] Block users via the API, ex: /blocks/create/1234235.xml and /blocks/destroy/1232352.xml.
[NEW] A simple test method: /help/test. Returns "ok" with a 200 response in the requested format.
[NEW] /help/downtime_schedule. Returns the same text we display on /home when we have a maintenance window scheduled. May be formalized to hard dates in the future.
[NEW] /account/update_delivery_device?device=[sms|im|none] - set which device Twitter delivers updates to for the authenticating user. Sending "none" as the "device" parameter will disable IM or SMS updates.
[NEW] Detailed status representations (ex: /statuses/show/1212235.xml) have a "favorited" boolean attribute that is true if the requesting user has made that statues a favorite.
[FIXED] Returning 401 when we should be returning 403 for a couple methods.
[FIXED] Enforce authentication for friends_timeline to prevent confusion.
[FIXED] /account/archive now supports since, If-Modified-Since, and since_id parameters/headers.
[FIXED] /statuses/replies now supports the since_id parameter.
[FIXED] /statuses/user_timeline now supports the since_id parameter.
[FIXED] /statuses/friends now support since and If-Modified-Since.
[FIXED] Should now send the same attributes in our Atom representation of status updates via XMPP as in XML/JSON representations.
[FIXED] The recently-introduced "following" attribute on detailed representations of users was a misnomer, and actually reflected whether or not the requesting user had enabled notifications for the requested user. This attribute has been renamed to "notifications". "following" now accurately reflects the friendship status between the two users.
Everything applicable to the documentation has been updated. Please let the list know if you see any inconsistencies, though.
Yup. I will buy you a beer next time I'm in the City.
-- ------------------------------------ personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- "Bad dog, what a big mess you made! I told you to sit! SIT!!!" -- unknown --
On Tue, Apr 29, 2008 at 9:11 PM, Alex Payne <a...@twitter.com> wrote:
> It's a good one, I hope!
> [NEW] /account/update_location.[xml|json] - sets the location for the > authenticated user to the string passed in a "location" parameter. > Nothing fancy, no geocoding or normalization. Just putting this out > there so developers can start playing with how geolocation might fit > into their Twitter applications.
> [NEW] You can add do /friendships/create/example_user.xml?follow=true > to turn notifications on for a user as well as befriend/follow them.
> [NEW] Block users via the API, ex: /blocks/create/1234235.xml and > /blocks/destroy/1232352.xml.
> [NEW] A simple test method: /help/test. Returns "ok" with a 200 > response in the requested format.
> [NEW] /help/downtime_schedule. Returns the same text we display on > /home when we have a maintenance window scheduled. May be formalized > to hard dates in the future.
> [NEW] /account/update_delivery_device?device=[sms|im|none] - set > which device Twitter delivers updates to for the authenticating user. > Sending "none" as the "device" parameter will disable IM or SMS > updates.
> [NEW] Detailed status representations (ex: > /statuses/show/1212235.xml) have a "favorited" boolean attribute that > is true if the requesting user has made that statues a favorite.
> [FIXED] Returning 401 when we should be returning 403 for a couple > methods.
> [FIXED] Enforce authentication for friends_timeline to prevent confusion.
> [FIXED] /account/archive now supports since, If-Modified-Since, and > since_id parameters/headers.
> [FIXED] /statuses/replies now supports the since_id parameter.
> [FIXED] /statuses/user_timeline now supports the since_id parameter.
> [FIXED] /statuses/friends now support since and If-Modified-Since.
> [FIXED] Should now send the same attributes in our Atom > representation of status updates via XMPP as in XML/JSON > representations.
> [FIXED] The recently-introduced "following" attribute on detailed > representations of users was a misnomer, and actually reflected > whether or not the requesting user had enabled notifications for the > requested user. This attribute has been renamed to "notifications". > "following" now accurately reflects the friendship status between the > two users.
> Everything applicable to the documentation has been updated. Please > let the list know if you see any inconsistencies, though.
> [NEW] /account/update_location.[xml|json] - sets the location for the
> authenticated user to the string passed in a "location" parameter.
> Nothing fancy, no geocoding or normalization. Just putting this out
> there so developers can start playing with how geolocation might fit
> into their Twitter applications.
> [NEW] You can add do /friendships/create/example_user.xml?follow=true
> to turn notifications on for a user as well as befriend/follow them.
> [NEW] Block users via the API, ex: /blocks/create/1234235.xml and
> /blocks/destroy/1232352.xml.
> [NEW] A simple test method: /help/test. Returns "ok" with a 200
> response in the requested format.
> [NEW] /help/downtime_schedule. Returns the same text we display on
> /home when we have a maintenance window scheduled. May be formalized
> to hard dates in the future.
> [NEW] /account/update_delivery_device?device=[sms|im|none] - set
> which device Twitter delivers updates to for the authenticating user.
> Sending "none" as the "device" parameter will disable IM or SMS
> updates.
> [NEW] Detailed status representations (ex:
> /statuses/show/1212235.xml) have a "favorited" boolean attribute that
> is true if the requesting user has made that statues a favorite.
> [FIXED] Returning 401 when we should be returning 403 for a couple methods.
> [FIXED] Enforce authentication for friends_timeline to prevent confusion.
> [FIXED] /account/archive now supports since, If-Modified-Since, and
> since_id parameters/headers.
> [FIXED] /statuses/replies now supports the since_id parameter.
> [FIXED] /statuses/user_timeline now supports the since_id parameter.
> [FIXED] /statuses/friends now support since and If-Modified-Since.
> [FIXED] Should now send the same attributes in our Atom
> representation of status updates via XMPP as in XML/JSON
> representations.
> [FIXED] The recently-introduced "following" attribute on detailed
> representations of users was a misnomer, and actually reflected
> whether or not the requesting user had enabled notifications for the
> requested user. This attribute has been renamed to "notifications".
> "following" now accurately reflects the friendship status between the
> two users.
> Everything applicable to the documentation has been updated. Please
> let the list know if you see any inconsistencies, though.
> [NEW] /account/update_delivery_device?device=[sms|im|none] - set
> which device Twitter delivers updates to for the authenticating user.
> Sending "none" as the "device" parameter will disable IM or SMS
> updates.
> [NEW] /account/update_location.[xml|json] - sets the location for the
> authenticated user to the string passed in a "location" parameter.
> Nothing fancy, no geocoding or normalization. Just putting this out
> there so developers can start playing with how geolocation might fit
> into their Twitter applications.
> [NEW] You can add do /friendships/create/example_user.xml?follow=true
> to turn notifications on for a user as well as befriend/follow them.
> [NEW] Block users via the API, ex: /blocks/create/1234235.xml and
> /blocks/destroy/1232352.xml.
> [NEW] A simple test method: /help/test. Returns "ok" with a 200
> response in the requested format.
> [NEW] /help/downtime_schedule. Returns the same text we display on
> /home when we have a maintenance window scheduled. May be formalized
> to hard dates in the future.
> [NEW] /account/update_delivery_device?device=[sms|im|none] - set
> which device Twitter delivers updates to for the authenticating user.
> Sending "none" as the "device" parameter will disable IM or SMS
> updates.
> [NEW] Detailed status representations (ex:
> /statuses/show/1212235.xml) have a "favorited" boolean attribute that
> is true if the requesting user has made that statues a favorite.
> [FIXED] Returning 401 when we should be returning 403 for a couple methods.
> [FIXED] Enforce authentication for friends_timeline to prevent confusion.
> [FIXED] /account/archive now supports since, If-Modified-Since, and
> since_id parameters/headers.
> [FIXED] /statuses/replies now supports the since_id parameter.
> [FIXED] /statuses/user_timeline now supports the since_id parameter.
> [FIXED] /statuses/friends now support since and If-Modified-Since.
> [FIXED] Should now send the same attributes in our Atom
> representation of status updates via XMPP as in XML/JSON
> representations.
> [FIXED] The recently-introduced "following" attribute on detailed
> representations of users was a misnomer, and actually reflected
> whether or not the requesting user had enabled notifications for the
> requested user. This attribute has been renamed to "notifications".
> "following" now accurately reflects the friendship status between the
> two users.
> Everything applicable to the documentation has been updated. Please
> let the list know if you see any inconsistencies, though.
> [NEW] /account/update_location.[xml|json] - sets the location for the > authenticated user to the string passed in a "location" parameter. > Nothing fancy, no geocoding or normalization. Just putting this out > there so developers can start playing with how geolocation might fit > into their Twitter applications.
> [NEW] You can add do /friendships/create/example_user.xml?follow=true > to turn notifications on for a user as well as befriend/follow them.
> [NEW] Block users via the API, ex: /blocks/create/1234235.xml and > /blocks/destroy/1232352.xml.
> [NEW] A simple test method: /help/test. Returns "ok" with a 200 > response in the requested format.
> [NEW] /help/downtime_schedule. Returns the same text we display on > /home when we have a maintenance window scheduled. May be formalized > to hard dates in the future.
> [NEW] /account/update_delivery_device?device=[sms|im|none] - set > which device Twitter delivers updates to for the authenticating user. > Sending "none" as the "device" parameter will disable IM or SMS > updates.
> [NEW] Detailed status representations (ex: > /statuses/show/1212235.xml) have a "favorited" boolean attribute that > is true if the requesting user has made that statues a favorite.
> [FIXED] Returning 401 when we should be returning 403 for a couple > methods.
> [FIXED] Enforce authentication for friends_timeline to prevent > confusion.
> [FIXED] /account/archive now supports since, If-Modified-Since, and > since_id parameters/headers.
> [FIXED] /statuses/replies now supports the since_id parameter.
> [FIXED] /statuses/user_timeline now supports the since_id parameter.
> [FIXED] /statuses/friends now support since and If-Modified-Since.
> [FIXED] Should now send the same attributes in our Atom > representation of status updates via XMPP as in XML/JSON > representations.
> [FIXED] The recently-introduced "following" attribute on detailed > representations of users was a misnomer, and actually reflected > whether or not the requesting user had enabled notifications for the > requested user. This attribute has been renamed to "notifications". > "following" now accurately reflects the friendship status between the > two users.
> Everything applicable to the documentation has been updated. Please > let the list know if you see any inconsistencies, though.
In particularly I'm looking at the update_location method. However one
thing I'd love to see is that it stamped each tweet with your location
at the time of the tweet. (opt in, blah, etc.)
So when you got a list of <status>, there was a <location> (or
<located_at/>) tucked into each one. Meaning that if I updated my
location to "Paris" when I was there last week and updated my <status>
a couple of times, and then came back to San Francisco and made some
more updates, I (or anyone) could see where I was (according to me) at
the time of the update/tweet.
Please, please, please :)
-D
On Apr 29, 7:11 pm, "Alex Payne" <a...@twitter.com> wrote:
> In particularly I'm looking at the update_location method. However one
> thing I'd love to see is that it stamped each tweet with your location
> at the time of the tweet. (opt in, blah, etc.)
> So when you got a list of <status>, there was a <location> (or
> <located_at/>) tucked into each one. Meaning that if I updated my
> location to "Paris" when I was there last week and updated my <status>
> a couple of times, and then came back to San Francisco and made some
> more updates, I (or anyone) could see where I was (according to me) at
> the time of the update/tweet.
> Please, please, please :)
> -D
> On Apr 29, 7:11 pm, "Alex Payne" <a...@twitter.com> wrote:
> On Apr 29, 10:11 pm, "Alex Payne" <a...@twitter.com> wrote:
> > It's a good one, I hope!
> > [NEW] /account/update_location.[xml|json] - sets the location for the
> > authenticated user to the string passed in a "location" parameter.
> > Nothing fancy, no geocoding or normalization. Just putting this out
> > there so developers can start playing with how geolocation might fit
> > into their Twitter applications.
> > [NEW] You can add do /friendships/create/example_user.xml?follow=true
> > to turn notifications on for a user as well as befriend/follow them.
> > [NEW] Block users via the API, ex: /blocks/create/1234235.xml and
> > /blocks/destroy/1232352.xml.
> > [NEW] A simple test method: /help/test. Returns "ok" with a 200
> > response in the requested format.
> > [NEW] /help/downtime_schedule. Returns the same text we display on
> > /home when we have a maintenance window scheduled. May be formalized
> > to hard dates in the future.
> > [NEW] /account/update_delivery_device?device=[sms|im|none] - set
> > which device Twitter delivers updates to for the authenticating user.
> > Sending "none" as the "device" parameter will disable IM or SMS
> > updates.
> > [NEW] Detailed status representations (ex:
> > /statuses/show/1212235.xml) have a "favorited" boolean attribute that
> > is true if the requesting user has made that statues a favorite.
> > [FIXED] Returning 401 when we should be returning 403 for a couple methods.
> > [FIXED] Enforce authentication for friends_timeline to prevent confusion.
> > [FIXED] /account/archive now supports since, If-Modified-Since, and
> > since_id parameters/headers.
> > [FIXED] /statuses/replies now supports the since_id parameter.
> > [FIXED] /statuses/user_timeline now supports the since_id parameter.
> > [FIXED] /statuses/friends now support since and If-Modified-Since.
> > [FIXED] Should now send the same attributes in our Atom
> > representation of status updates via XMPP as in XML/JSON
> > representations.
> > [FIXED] The recently-introduced "following" attribute on detailed
> > representations of users was a misnomer, and actually reflected
> > whether or not the requesting user had enabled notifications for the
> > requested user. This attribute has been renamed to "notifications".
> > "following" now accurately reflects the friendship status between the
> > two users.
> > Everything applicable to the documentation has been updated. Please
> > let the list know if you see any inconsistencies, though.
On Tue, Apr 29, 2008 at 8:05 PM, sugree <sug...@gmail.com> wrote:
> Incorrect url of downtime_schedule.
> Are all new features ready to use? I tried test and downtime but it > just 302 redirected me to login page.
> Thanks for hard works.
> On Apr 30, 9:11 am, "Alex Payne" <a...@twitter.com> wrote: > > It's a good one, I hope!
> > [NEW] /account/update_location.[xml|json] - sets the location for the > > authenticated user to the string passed in a "location" parameter. > > Nothing fancy, no geocoding or normalization. Just putting this out > > there so developers can start playing with how geolocation might fit > > into their Twitter applications.
> > [NEW] You can add do /friendships/create/example_user.xml?follow=true > > to turn notifications on for a user as well as befriend/follow them.
> > [NEW] Block users via the API, ex: /blocks/create/1234235.xml and > > /blocks/destroy/1232352.xml.
> > [NEW] A simple test method: /help/test. Returns "ok" with a 200 > > response in the requested format.
> > [NEW] /help/downtime_schedule. Returns the same text we display on > > /home when we have a maintenance window scheduled. May be formalized > > to hard dates in the future.
> > [NEW] /account/update_delivery_device?device=[sms|im|none] - set > > which device Twitter delivers updates to for the authenticating user. > > Sending "none" as the "device" parameter will disable IM or SMS > > updates.
> > [NEW] Detailed status representations (ex: > > /statuses/show/1212235.xml) have a "favorited" boolean attribute that > > is true if the requesting user has made that statues a favorite.
> > [FIXED] Returning 401 when we should be returning 403 for a couple methods.
> > [FIXED] Enforce authentication for friends_timeline to prevent confusion.
> > [FIXED] /account/archive now supports since, If-Modified-Since, and > > since_id parameters/headers.
> > [FIXED] /statuses/replies now supports the since_id parameter.
> > [FIXED] /statuses/user_timeline now supports the since_id parameter.
> > [FIXED] /statuses/friends now support since and If-Modified-Since.
> > [FIXED] Should now send the same attributes in our Atom > > representation of status updates via XMPP as in XML/JSON > > representations.
> > [FIXED] The recently-introduced "following" attribute on detailed > > representations of users was a misnomer, and actually reflected > > whether or not the requesting user had enabled notifications for the > > requested user. This attribute has been renamed to "notifications". > > "following" now accurately reflects the friendship status between the > > two users.
> > Everything applicable to the documentation has been updated. Please > > let the list know if you see any inconsistencies, though.
So "friends" returns people the authenticated user is following, and
supposedly supports a "since" parameter. "Followers" returns people
following the auth user, and does not yet support "since". So getting
a list of all followers still requires paging on the client side. Just
clarifying.
Also, is there any plan to rename or duplicate the "friends" call as
"following", as the "friends" language was dropped from the UX a while
ago?
On Apr 29, 9:11 pm, "Alex Payne" <a...@twitter.com> wrote:
> [NEW] /account/update_location.[xml|json] - sets the location for the
> authenticated user to the string passed in a "location" parameter.
> Nothing fancy, no geocoding or normalization. Just putting this out
> there so developers can start playing with how geolocation might fit
> into their Twitter applications.
> [NEW] You can add do /friendships/create/example_user.xml?follow=true
> to turn notifications on for a user as well as befriend/follow them.
> [NEW] Block users via the API, ex: /blocks/create/1234235.xml and
> /blocks/destroy/1232352.xml.
> [NEW] A simple test method: /help/test. Returns "ok" with a 200
> response in the requested format.
> [NEW] /help/downtime_schedule. Returns the same text we display on
> /home when we have a maintenance window scheduled. May be formalized
> to hard dates in the future.
> [NEW] /account/update_delivery_device?device=[sms|im|none] - set
> which device Twitter delivers updates to for the authenticating user.
> Sending "none" as the "device" parameter will disable IM or SMS
> updates.
> [NEW] Detailed status representations (ex:
> /statuses/show/1212235.xml) have a "favorited" boolean attribute that
> is true if the requesting user has made that statues a favorite.
> [FIXED] Returning 401 when we should be returning 403 for a couple methods.
> [FIXED] Enforce authentication for friends_timeline to prevent confusion.
> [FIXED] /account/archive now supports since, If-Modified-Since, and
> since_id parameters/headers.
> [FIXED] /statuses/replies now supports the since_id parameter.
> [FIXED] /statuses/user_timeline now supports the since_id parameter.
> [FIXED] /statuses/friends now support since and If-Modified-Since.
> [FIXED] Should now send the same attributes in our Atom
> representation of status updates via XMPP as in XML/JSON
> representations.
> [FIXED] The recently-introduced "following" attribute on detailed
> representations of users was a misnomer, and actually reflected
> whether or not the requesting user had enabled notifications for the
> requested user. This attribute has been renamed to "notifications".
> "following" now accurately reflects the friendship status between the
> two users.
> Everything applicable to the documentation has been updated. Please
> let the list know if you see any inconsistencies, though.
> So "friends" returns people the authenticated user is following, and > supposedly supports a "since" parameter. "Followers" returns people > following the auth user, and does not yet support "since". So getting > a list of all followers still requires paging on the client side. Just > clarifying.
> Also, is there any plan to rename or duplicate the "friends" call as > "following", as the "friends" language was dropped from the UX a while > ago?
> On Apr 29, 9:11 pm, "Alex Payne" <a...@twitter.com> wrote: > > It's a good one, I hope!
> > [NEW] /account/update_location.[xml|json] - sets the location for the > > authenticated user to the string passed in a "location" parameter. > > Nothing fancy, no geocoding or normalization. Just putting this out > > there so developers can start playing with how geolocation might fit > > into their Twitter applications.
> > [NEW] You can add do /friendships/create/example_user.xml?follow=true > > to turn notifications on for a user as well as befriend/follow them.
> > [NEW] Block users via the API, ex: /blocks/create/1234235.xml and > > /blocks/destroy/1232352.xml.
> > [NEW] A simple test method: /help/test. Returns "ok" with a 200 > > response in the requested format.
> > [NEW] /help/downtime_schedule. Returns the same text we display on > > /home when we have a maintenance window scheduled. May be formalized > > to hard dates in the future.
> > [NEW] /account/update_delivery_device?device=[sms|im|none] - set > > which device Twitter delivers updates to for the authenticating user. > > Sending "none" as the "device" parameter will disable IM or SMS > > updates.
> > [NEW] Detailed status representations (ex: > > /statuses/show/1212235.xml) have a "favorited" boolean attribute that > > is true if the requesting user has made that statues a favorite.
> > [FIXED] Returning 401 when we should be returning 403 for a couple methods.
> > [FIXED] Enforce authentication for friends_timeline to prevent confusion.
> > [FIXED] /account/archive now supports since, If-Modified-Since, and > > since_id parameters/headers.
> > [FIXED] /statuses/replies now supports the since_id parameter.
> > [FIXED] /statuses/user_timeline now supports the since_id parameter.
> > [FIXED] /statuses/friends now support since and If-Modified-Since.
> > [FIXED] Should now send the same attributes in our Atom > > representation of status updates via XMPP as in XML/JSON > > representations.
> > [FIXED] The recently-introduced "following" attribute on detailed > > representations of users was a misnomer, and actually reflected > > whether or not the requesting user had enabled notifications for the > > requested user. This attribute has been renamed to "notifications". > > "following" now accurately reflects the friendship status between the > > two users.
> > Everything applicable to the documentation has been updated. Please > > let the list know if you see any inconsistencies, though.
> Yup. I will buy you a beer next time I'm in the City.
> --
> ------------------------------------ personal:http://www.cameronkaiser.com/-- > Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com
> -- "Bad dog, what a big mess you made! I told you to sit! SIT!!!" -- unknown --
