[twitter-dev] Re: Either destroy is/was failing, or my understanding of destroy is/was failing

2009-09-02 Thread John Kalucki

There's a note on the Status blog that we're having some delays in
processing a proportion of new statuses. This issue looks to largely
be resolved, and all the subsequent backlogs have been processed --
except there's still a bit of a backlog pushing statuses to Facebook
that should resolve soon enough.

I'd imagine that your test status was delayed. Then, when you tried to
delete it, it wasn't available. You should try again now. The queues
look to be empty.

-John


On Sep 2, 9:38 am, Ted Neward ted.new...@gmail.com wrote:
 I've been hacking on the Twitter API, and I'm running into some serious
 weirdness with destroy.

 I post a message:

 C:\ curl -u name:pass -d 
 status=Testinghttp://twitter.com/statuses/update.xml

 ?xml version=1.0 encoding=UTF-8?

 status

   created_atWed Sep 02 10:10:23 + 2009/created_at

   id3708721364/id

   textTesting/text

   sourcelt;a href=quot;http://apiwiki.twitter.com/;
 rel=quot;nofollowquot;gt;APIlt;/agt;/source

   truncatedfalse/truncated

   in_reply_to_status_id/in_reply_to_status_id

   in_reply_to_user_id/in_reply_to_user_id

   favoritedfalse/favorited

   in_reply_to_screen_name/in_reply_to_screen_name

   user

     id70927096/id

     nameTed Neward/name

     screen_nameTestingScitter/screen_name

     location/location

     description/description

 profile_image_urlhttp://s.twimg.com/a/1251845223/images/default_profile_no
 rmal.png/profile_image_url

     url/url

     protectedfalse/protected

     followers_count1/followers_count

     profile_background_color9ae4e8/profile_background_color

     profile_text_color00/profile_text_color

     profile_link_colorff/profile_link_color

     profile_sidebar_fill_colore0ff92/profile_sidebar_fill_color

     profile_sidebar_border_color87bc44/profile_sidebar_border_color

     friends_count6/friends_count

     created_atWed Sep 02 09:49:13 + 2009/created_at

     favourites_count0/favourites_count

     utc_offset/utc_offset

     time_zone/time_zone

 profile_background_image_urlhttp://s.twimg.com/a/1251845223/images/themes/
 theme1/bg.gif/profile_background_image_url

     profile_background_tilefalse/profile_background_tile

     statuses_count4/statuses_count

     notificationsfalse/notifications

     verifiedfalse/verified

     followingfalse/following

   /user

 /status

 . which is all good, but then I try to delete that message:

 C:\ curl -u name:pass --http-request 
 DELETEhttp://twitter.com/statuses/destroy/3708721364.xml

 ?xml version=1.0 encoding=UTF-8?

 hash

   request/statuses/destroy/3708721364.xml/request

   errorWe could not delete that status for some reason./error

 /hash

 What gives? Is this something that I'm doing wrong on my end? Momentary
 server weirdness? (Though it seems to have been pretty consistent all
 night.)

 Ted Neward

 Java, .NET, XML Services

 Consulting, Teaching, Speaking, Writing

  http://www.tedneward.comhttp://www.tedneward.com


[twitter-dev] Re: Either destroy is/was failing, or my understanding of destroy is/was failing

2009-09-02 Thread Kevin Mesiab

Pushing statuses to Facebook ?

can you clarify this?


On Wed, Sep 2, 2009 at 11:25 AM, John Kaluckijkalu...@gmail.com wrote:

 There's a note on the Status blog that we're having some delays in
 processing a proportion of new statuses. This issue looks to largely
 be resolved, and all the subsequent backlogs have been processed --
 except there's still a bit of a backlog pushing statuses to Facebook
 that should resolve soon enough.

 I'd imagine that your test status was delayed. Then, when you tried to
 delete it, it wasn't available. You should try again now. The queues
 look to be empty.

 -John


 On Sep 2, 9:38 am, Ted Neward ted.new...@gmail.com wrote:
 I've been hacking on the Twitter API, and I'm running into some serious
 weirdness with destroy.

 I post a message:

 C:\ curl -u name:pass -d 
 status=Testinghttp://twitter.com/statuses/update.xml

 ?xml version=1.0 encoding=UTF-8?

 status

   created_atWed Sep 02 10:10:23 + 2009/created_at

   id3708721364/id

   textTesting/text

   sourcelt;a href=quot;http://apiwiki.twitter.com/;
 rel=quot;nofollowquot;gt;APIlt;/agt;/source

   truncatedfalse/truncated

   in_reply_to_status_id/in_reply_to_status_id

   in_reply_to_user_id/in_reply_to_user_id

   favoritedfalse/favorited

   in_reply_to_screen_name/in_reply_to_screen_name

   user

     id70927096/id

     nameTed Neward/name

     screen_nameTestingScitter/screen_name

     location/location

     description/description

 profile_image_urlhttp://s.twimg.com/a/1251845223/images/default_profile_no
 rmal.png/profile_image_url

     url/url

     protectedfalse/protected

     followers_count1/followers_count

     profile_background_color9ae4e8/profile_background_color

     profile_text_color00/profile_text_color

     profile_link_colorff/profile_link_color

     profile_sidebar_fill_colore0ff92/profile_sidebar_fill_color

     profile_sidebar_border_color87bc44/profile_sidebar_border_color

     friends_count6/friends_count

     created_atWed Sep 02 09:49:13 + 2009/created_at

     favourites_count0/favourites_count

     utc_offset/utc_offset

     time_zone/time_zone

 profile_background_image_urlhttp://s.twimg.com/a/1251845223/images/themes/
 theme1/bg.gif/profile_background_image_url

     profile_background_tilefalse/profile_background_tile

     statuses_count4/statuses_count

     notificationsfalse/notifications

     verifiedfalse/verified

     followingfalse/following

   /user

 /status

 . which is all good, but then I try to delete that message:

 C:\ curl -u name:pass --http-request 
 DELETEhttp://twitter.com/statuses/destroy/3708721364.xml

 ?xml version=1.0 encoding=UTF-8?

 hash

   request/statuses/destroy/3708721364.xml/request

   errorWe could not delete that status for some reason./error

 /hash

 What gives? Is this something that I'm doing wrong on my end? Momentary
 server weirdness? (Though it seems to have been pretty consistent all
 night.)

 Ted Neward

 Java, .NET, XML Services

 Consulting, Teaching, Speaking, Writing

  http://www.tedneward.comhttp://www.tedneward.com




-- 
Kevin Mesiab
CEO, Mesiab Labs L.L.C.
http://twitter.com/kmesiab
http://mesiablabs.com
http://retweet.com


[twitter-dev] Re: Either destroy is/was failing, or my understanding of destroy is/was failing

2009-09-02 Thread John Kalucki

We optionally push your statuses to Facebook to allow you to update
your Facebook status automatically. This has been supported for about
14+ months.

-John


On Sep 2, 4:16 pm, Kevin Mesiab ke...@mesiablabs.com wrote:
 Pushing statuses to Facebook ?

 can you clarify this?



 On Wed, Sep 2, 2009 at 11:25 AM, John Kaluckijkalu...@gmail.com wrote:

  There's a note on the Status blog that we're having some delays in
  processing a proportion of new statuses. This issue looks to largely
  be resolved, and all the subsequent backlogs have been processed --
  except there's still a bit of a backlog pushing statuses to Facebook
  that should resolve soon enough.

  I'd imagine that your test status was delayed. Then, when you tried to
  delete it, it wasn't available. You should try again now. The queues
  look to be empty.

  -John

  On Sep 2, 9:38 am, Ted Neward ted.new...@gmail.com wrote:
  I've been hacking on the Twitter API, and I'm running into some serious
  weirdness with destroy.

  I post a message:

  C:\ curl -u name:pass -d 
  status=Testinghttp://twitter.com/statuses/update.xml

  ?xml version=1.0 encoding=UTF-8?

  status

    created_atWed Sep 02 10:10:23 + 2009/created_at

    id3708721364/id

    textTesting/text

    sourcelt;a href=quot;http://apiwiki.twitter.com/;
  rel=quot;nofollowquot;gt;APIlt;/agt;/source

    truncatedfalse/truncated

    in_reply_to_status_id/in_reply_to_status_id

    in_reply_to_user_id/in_reply_to_user_id

    favoritedfalse/favorited

    in_reply_to_screen_name/in_reply_to_screen_name

    user

      id70927096/id

      nameTed Neward/name

      screen_nameTestingScitter/screen_name

      location/location

      description/description

  profile_image_urlhttp://s.twimg.com/a/1251845223/images/default_profile_no
  rmal.png/profile_image_url

      url/url

      protectedfalse/protected

      followers_count1/followers_count

      profile_background_color9ae4e8/profile_background_color

      profile_text_color00/profile_text_color

      profile_link_colorff/profile_link_color

      profile_sidebar_fill_colore0ff92/profile_sidebar_fill_color

      profile_sidebar_border_color87bc44/profile_sidebar_border_color

      friends_count6/friends_count

      created_atWed Sep 02 09:49:13 + 2009/created_at

      favourites_count0/favourites_count

      utc_offset/utc_offset

      time_zone/time_zone

  profile_background_image_urlhttp://s.twimg.com/a/1251845223/images/themes/
  theme1/bg.gif/profile_background_image_url

      profile_background_tilefalse/profile_background_tile

      statuses_count4/statuses_count

      notificationsfalse/notifications

      verifiedfalse/verified

      followingfalse/following

    /user

  /status

  . which is all good, but then I try to delete that message:

  C:\ curl -u name:pass --http-request 
  DELETEhttp://twitter.com/statuses/destroy/3708721364.xml

  ?xml version=1.0 encoding=UTF-8?

  hash

    request/statuses/destroy/3708721364.xml/request

    errorWe could not delete that status for some reason./error

  /hash

  What gives? Is this something that I'm doing wrong on my end? Momentary
  server weirdness? (Though it seems to have been pretty consistent all
  night.)

  Ted Neward

  Java, .NET, XML Services

  Consulting, Teaching, Speaking, Writing

   http://www.tedneward.comhttp://www.tedneward.com

 --
 Kevin Mesiab
 CEO, Mesiab Labs 
 L.L.C.http://twitter.com/kmesiabhttp://mesiablabs.comhttp://retweet.com


[twitter-dev] Re: Either destroy is/was failing, or my understanding of destroy is/was failing

2009-09-02 Thread Alex Payne

We've got a fix for this going out tomorrow.

On Wed, Sep 2, 2009 at 09:38, Ted Newardted.new...@gmail.com wrote:
 I’ve been hacking on the Twitter API, and I’m running into some serious
 weirdness with destroy.



 I post a message:



 C:\ curl -u name:pass -d status=Testing
 http://twitter.com/statuses/update.xml

 ?xml version=1.0 encoding=UTF-8?

 status

   created_atWed Sep 02 10:10:23 + 2009/created_at

   id3708721364/id

   textTesting/text

   sourcelt;a href=quot;http://apiwiki.twitter.com/quot;
 rel=quot;nofollowquot;gt;APIlt;/agt;/source

   truncatedfalse/truncated

   in_reply_to_status_id/in_reply_to_status_id

   in_reply_to_user_id/in_reply_to_user_id

   favoritedfalse/favorited

   in_reply_to_screen_name/in_reply_to_screen_name

   user

     id70927096/id

     nameTed Neward/name

     screen_nameTestingScitter/screen_name

     location/location

     description/description


 profile_image_urlhttp://s.twimg.com/a/1251845223/images/default_profile_normal.png/profile_image_url

     url/url

     protectedfalse/protected

     followers_count1/followers_count

     profile_background_color9ae4e8/profile_background_color

     profile_text_color00/profile_text_color

     profile_link_colorff/profile_link_color

     profile_sidebar_fill_colore0ff92/profile_sidebar_fill_color

     profile_sidebar_border_color87bc44/profile_sidebar_border_color

     friends_count6/friends_count

     created_atWed Sep 02 09:49:13 + 2009/created_at

     favourites_count0/favourites_count

     utc_offset/utc_offset

     time_zone/time_zone


 profile_background_image_urlhttp://s.twimg.com/a/1251845223/images/themes/theme1/bg.gif/profile_background_image_url

     profile_background_tilefalse/profile_background_tile

     statuses_count4/statuses_count

     notificationsfalse/notifications

     verifiedfalse/verified

     followingfalse/following

   /user

 /status



 … which is all good, but then I try to delete that message:



 C:\ curl -u name:pass --http-request DELETE
 http://twitter.com/statuses/destroy/3708721364.xml

 ?xml version=1.0 encoding=UTF-8?

 hash

   request/statuses/destroy/3708721364.xml/request

   errorWe could not delete that status for some reason./error

 /hash





 What gives? Is this something that I’m doing wrong on my end? Momentary
 server weirdness? (Though it seems to have been pretty consistent all
 night.)



 Ted Neward

 Java, .NET, XML Services

 Consulting, Teaching, Speaking, Writing

 http://www.tedneward.com







-- 
Alex Payne - Platform Lead, Twitter, Inc.
http://twitter.com/al3x