Re: [twitter-dev] Race conditions?

[Michael Steuer]

Nice catch! :) but a double negative is a positive so he must be  
following 1 user... ;)




On Mar 29, 2010, at 3:42 PM, Yu-Shan Fung  wrote:


Or some kind of eventual consistency bug (doubt it)?

Anyway, this user is apparently following -2 people. In other words,  
if he follow 2 more people, he would be following nobody...


http://twitter.com/jpcbennett

Screenshot attached. It's messing with some computations on our end,  
you might want to watch out for them too if your code assume that  
following/follower counts are non-negative...


Cheers,
Yu-Shan (@ambivalence)



--
“When nothing seems to help, I go look at a stonecutter hammering aw 
ay at his rock perhaps a hundred times without as much as a crack sh 
owing in it. Yet at the hundred and first blow it will split in two, 
 and I know it was not that blow that did it, but all that had gone  
before.” — Jacob Riis
To unsubscribe from this group, send email to twitter-development- 
talk+unsubscribegooglegroups.com or reply to this email with the  
words "REMOVE ME" as the subject.




To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the 
words "REMOVE ME" as the subject.

Re: [twitter-dev] Re: How to keep my website logged in to twitter so everyone can post to my twitter account ?

[Michael Steuer]

I guess what needs clarification is: what do you mean by "send tweets  
to MY Twitter"? Did u want to allow random users to tweet on your  
behalf (kinda dangerous don't u think?) or simply allow them to  
@mention you?




On Mar 28, 2010, at 10:15 AM, Dinamito  wrote:


What I am trying to do is not related to joomla
I will explain my self again
I want to create a simple page that everyone can read all my tweets
and in the top of the page I want to have an option to write tweets to
my tweeter
I want to keep this page always connect to twitter so everyone can
surf to this page and send tweets to my twitter lets call it a public
tweeter.

There is a way to do it ?


On Mar 27, 8:10 pm, "M. Edward (Ed) Borasky"  wrote:

On 03/27/2010 03:59 AM, Dinamito wrote:> Hi,


I am searching the web for a long time a way to keep my website
connected to twitter with my account so everyone can post in my
twitter directly from my site.
my site based on joomla and I can use external php/html file as you
can understand I am not a processional developer actuality I am just
starting now to learn things. I will very appreciate if you can help
me with this.



Thanks a lot.


To unsubscribe from this group, send email to twitter-development- 
talk+unsubscribegooglegroups.com or reply to this email with the  
words "REMOVE ME" as the subject.


I don't know Joomla! at all, but I suspect there are plugins that  
will

do that.


To unsubscribe from this group, send email to twitter-development- 
talk+unsubscribegooglegroups.com or reply to this email with the  
words "REMOVE ME" as the subject.


To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the 
words "REMOVE ME" as the subject.

Re: [twitter-dev] Retweet "via" Shows Wrong App?

[Michael Steuer]

Via will show the app the original tweet was submitted with...




On Mar 26, 2010, at 10:17 AM, David Cann  wrote:


When posting a retweet to the API, twitter.com is displaying an
incorrect "via" app name.  Is this a known issue or am I doing
something wrong?

The "via" app name displayed is correct when posting new statuses and
replies.  I'm using the MGTwitterEngine and 
http://github.com/bengottlieb/Twitter-OAuth-iPhone
in an iPad app.

You can see 5 retweets on this page claiming to be retweeted via
UberTwitter and twitterfeed, when they should say "via Nightline Test"
instead... like the rest of the updates do:
http://twitter.com/davidcanntest2

Thanks,
David

To unsubscribe from this group, send email to twitter-development- 
talk+unsubscribegooglegroups.com or reply to this email with the  
words "REMOVE ME" as the subject.


To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the 
words "REMOVE ME" as the subject.

Re: [twitter-dev] What would you recommend?

[Michael Steuer]

Why can¹t your application itself track this information? If it¹s a web app,
it should be trivial... If it¹s any other kind of app ­ if it can connect to
Twitter, it should also be able to connect to your web service and
periodically check in... That way you¹ll have accurate info up to the last
tweet, as opposed to extrapolating a random sample and piping millions of
tweets to find those that were send with your app.


On 3/25/10 1:27 PM, "John Kalucki"  wrote:

> Streaming API, /1/statuses/sample.json.
> 
> http://groups.google.com/group/twitter-development-talk/browse_frm/thread/735e
> b1d3ac718cbe/fbf0b331255868b6?lnk=gst&q=confidence+interval#fbf0b331255868b6
> 
> -John Kalucki
> http://twitter.com/jkalucki
> Twitter, Inc.
> 
> 
> On Thu, Mar 25, 2010 at 12:37 PM, metawops  wrote:
>> Hi,
>> if I want to write an application that counts how many tweets are
>> being made with my (officially with its own source parameter
>> registered) Twitter client -- what API technique should I use?
>> - the search API?
>> - the streaming API?
>> - the normal REST API?
>> 
>> Streaming API currently only offers 5 or 15 % of all public tweets,
>> right? :-(
>> 
>> Thanks a lot!
>> Stefan.
>> 
>> To unsubscribe from this group, send email to
>> twitter-development-talk+unsubscribegooglegroups.com
>>   or reply to this email with the words
>> "REMOVE ME" as the subject.
> 
> 
> To unsubscribe from this group, send email to
> twitter-development-talk+unsubscribegooglegroups.com or reply to this email
> with the words "REMOVE ME" as the subject.
> 

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

[twitter-dev] How many lists can one own? Doc inconsistency?

[Michael Steuer]

Hi,

At http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-POST-lists it says:

Creates a new list for the authenticated user. Accounts are limited to 20
lists.

However http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-GET-lists
describes a cursoring method to page through one¹s lists, and says a single
page contains 20 lists...

Why would one need cursoring/paging if the cursor size is the same as the
maximum number of lists one can have? Which of these two docs is incorrect?

Thanks,

Michael.

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words "REMOVE ME" as the subject.

Re: [twitter-dev] Re: bulk user show API

[Michael Steuer]

I'm sorry, with "rate limited users" I meant "white listed users"...  
It was early ;) so white listed users can lookup 2M?




On Mar 24, 2010, at 8:06 AM, Raffi Krikorian  wrote:

if your rate limit is 150/hour - then you can look up 15K users/ 
hour...


On Wed, Mar 24, 2010 at 7:22 AM, Michael Steuer   
wrote:
That's an awesome surprise. So 100 users per request, and 1 call per  
request - does this really mean that rate limited uses can look up  
2M users/hour now? Not that I'm complaining just want to make sure I  
read the doc right as this would be the total opposite of how this  
feature was originally launched not too long ago.


Thanks!!!

Michael.




On Mar 23, 2010, at 11:06 PM, Martin Dudek  
 wrote:


Good morning,


just discovered the change of the rate limit and also the possibility
to lookup 100 users with one call.

Thank you so much to respond in such a generous way to our requests
here. Highly appreciated

Greets

martin

To unsubscribe from this group, send email to twitter-development- 
talk+unsubscribegooglegroups.com or reply to this email with the  
words "REMOVE ME" as the subject.


To unsubscribe from this group, send email to twitter-development- 
talk+unsubscribegooglegroups.com or reply to this email with the  
words "REMOVE ME" as the subject.




--
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi
To unsubscribe from this group, send email to twitter-development- 
talk+unsubscribegooglegroups.com or reply to this email with the  
words "REMOVE ME" as the subject.


To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the 
words "REMOVE ME" as the subject.

Re: [twitter-dev] Re: bulk user show API

[Michael Steuer]

That's an awesome surprise. So 100 users per request, and 1 call per  
request - does this really mean that rate limited uses can look up 2M  
users/hour now? Not that I'm complaining just want to make sure I read  
the doc right as this would be the total opposite of how this feature  
was originally launched not too long ago.


Thanks!!!

Michael.



On Mar 23, 2010, at 11:06 PM, Martin Dudek   
wrote:



Good morning,


just discovered the change of the rate limit and also the possibility
to lookup 100 users with one call.

Thank you so much to respond in such a generous way to our requests
here. Highly appreciated

Greets

martin

To unsubscribe from this group, send email to twitter-development- 
talk+unsubscribegooglegroups.com or reply to this email with the  
words "REMOVE ME" as the subject.


To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the 
words "REMOVE ME" as the subject.

Re: [twitter-dev] streaming api

[Michael Steuer]

I'm not familiar with your library but by just looking at the snippet  
you see

.For(10.Seconds()).Take(100)
I'd imagine if instead of 10 seconds you'd pass 10 years and instead  
of 100 you'd pass something infinitely larger, you'd experience more  
of a stream?


On Mar 20, 2010, at 3:01 AM, rizwan khann  wrote:


Hi
i run this code but it just  give me 100 status whose
track "twitter" word
but it not work as a stream...and not continue update for real time.
plz tell me which method use to continue stream
i m using TweetSharp Preview 24 API



var twitter = FluentTwitter.CreateRequest()
   .AuthenticateAs(TWITTER_USERNAME, TWITTER_PASSWORD)
   .Configuration.TimeoutAfter(1.Minute())
   .Configuration.UseAutomaticRetries(RetryOn.ConnectionClosed, 2)
   .Stream().FromFilter()
   .For(10.Seconds()).Take(100)
   .Tracking("Twitter") // Add other filter options here...
   .CallbackTo((sender, result) =>
   {
   var statuses = result.AsStatuses();
   foreach (var status in statuses)
   {
   Console.WriteLine("{0}: {1}", status.User.ScreenName,
status.Text);
   }

   });
twitter.RequestAsync();

To unsubscribe from this group, send email to twitter-development- 
talk+unsubscribegooglegroups.com or reply to this email with the  
words "REMOVE ME" as the subject.


To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the 
words "REMOVE ME" as the subject.

Re: [twitter-dev] Incorporating the api into a site

[Michael Steuer]

You would read the documentation at http://apiwiki.twitter.com and implement
it into your website.


On 3/16/10 7:33 AM, "Tony"  wrote:

> How would I incorporate this api into my website.?

Re: [twitter-dev] Re: callback to parent window oAuth

[Michael Steuer]

First off, you should first refresh the parent window and THEN close the
child window (once you close the child window execution of your javascript
will stop).

I would presume you can simply output javascript to the client, and it will
get executed. So in your mark up that your servlet renders, simply add a

Re: [twitter-dev] callback to parent window oAuth

[Michael Steuer]

There's better ways of doing this actually, that doesn't require polling of
any kind...

In your pop up, when Twitter redirects to your callback URL:

- process the Oauth tokens etc so that your user's session is authenticated
- set the parents window location to whereever it needs to go (logged in
view of your app), using window.opener.location.href = "whatever"
- close the popup (window.close)





On 3/15/10 5:58 AM, "Taylor Singletary" 
wrote:

> You can't accomplish it exactly the way you want to, but you can do this:
> 
> 1) Set the OAuth callback to a URL that's still on your domain,
> something specific that's purpose is only to collect the callback
> details and quickly return a 200 status.
> 2) In your parent window, occasionally poll the status of the child
> window -- when it's on Twitter.com you won't have access to its
> window.location.
> 3) When the window.location is on your callback URL and the same
> domain as the parent window, you'll be able to close the pop-up window
> and then change the state of the originating window in turn.
> 
> Taylor Singletary
> Developer Advocate, Twitter
> http://twitter.com/episod
> 
> 
> 
> On Mon, Mar 15, 2010 at 6:50 AM, deb123  wrote:
>> I am trying to open the "Accept/Deny" window in a new window. I want
>> the callback to come back to the parent window. If I use window.open,
>> I get the pop up but the callback comes back to the child window. I
>> want the child window to close when the use hits the Accept or Deny
>> and the callback to come to the parent window.
>> How do I make this happen?
>> Thanks,
>> D
>> 

Re: [twitter-dev] Sign Out no longer works

[Michael Steuer]

What URL was switched?

I had this issue confirmed on several machines (both Mac and Windows) on
multiple locations... Shortly after I sent my email to the group, it seemed
to work again...

Weird...



On Thu, Mar 11, 2010 at 6:03 PM, Andrew Badera  wrote:

> Any chance this is related to the URL switch and cookies leftover from
> the old URL? We've seen similar before ...
>
> ∞ Andy Badera
> ∞ +1 518-641-1280 Google Voice
> ∞ This email is: [ ] bloggable [x] ask first [ ] private
> ∞ Google me: http://www.google.com/search?q=andrew%20badera
>
>
>
> On Thu, Mar 11, 2010 at 8:56 PM, Michael Steuer  wrote:
> > Hi Twitter folks,
> >
> > It seems the “Sign Out” link on Twitter.com, as well as the one on the
> Oauth
> > sign in page no longer works... It seems to just be reloading the page or
> > something... I’ve reproduced this on Firefox for Mac and Firefox for
> > Window..
> >
> > Just wanted to let you know, not sure if it was a known issue yet...
> (right
> > now Oauth users (or Twitter.com users) cannot switch accounts it seems)
> >
> > Michael.
>

[twitter-dev] Sign Out no longer works

[Michael Steuer]

Hi Twitter folks,

It seems the ³Sign Out² link on Twitter.com, as well as the one on the Oauth
sign in page no longer works... It seems to just be reloading the page or
something... I¹ve reproduced this on Firefox for Mac and Firefox for
Window..

Just wanted to let you know, not sure if it was a known issue yet... (right
now Oauth users (or Twitter.com users) cannot switch accounts it seems)

Michael.

Re: [twitter-dev] bulk user show API

[Michael Steuer]

I guess what I¹m really trying to say is, I suppose, that for all of us who
have been lobbying for a bulk-lookup method for a pretty long time, what¹s
been made available here is quite disappointing. It¹s like you¹re giving us
the Ferrari we always wanted, but then tell us it has a fuel range of 2
miles so we can¹t use it to drive to work with ;)



On 3/11/10 11:34 AM, "Raffi Krikorian"  wrote:

> i wouldn't necessarily and harshly say "useless" :P  it still prevents you
> from having to make 1000 user/show requests (which you can't do right now).
> 
> 
> On Thu, Mar 11, 2010 at 10:59 AM, Michael Steuer  wrote:
>> Oh wow, I missed that. I understood it was rate limited at 1000 calls/hour
>> (which would come out to 20k user objects)
>> 
>> Having a limit of only 1,000 user objects an hour, renders this new API
>> pretty useless! Come on! I thought the idea was to give developers who now do
>> 10's of thousands of user/show calls a more efficient alternative?!?!
>> 
>> 
>> 
>> On Mar 11, 2010, at 10:11 AM, Abraham Williams <4bra...@gmail.com> wrote:
>> 
>>> My understanding is that it is 50 users/lookup API calls x 20 user objects
>>> per call = 1000 user objects. Not 1000 users/lookup calls of 20 user
>>> objects.
>>> 
>>> Abraham
>>> 
>>> On Thu, Mar 11, 2010 at 10:06, Michael Steuer < <mailto:mste...@gmail.com>
>>> mste...@gmail.com> wrote:
>>>> 
>>>> Erm, doesn¹t 20,000 x users/show equate to 1,000 x users/lookup ?
>>>> 
>>>> Or are you whitelisted for more than 20,000 API calls an hour?
>>>> 
>>>> 
>>>> On 3/11/10 9:53 AM, "Abraham Williams" < <http://4bra...@gmail.com>
>>>> 4bra...@gmail.com> wrote:
>>>> 
>>>>> So for something like Intersect [1] where I have to do sometimes tens of
>>>>> thousands of profile lookups per hour I should stick with users/show? Or
>>>>> can I get an account whitelisted for more lookups per hour?
>>>>> 
>>>>> Abraham
>>>>> 
>>>>> On Thu, Mar 11, 2010 at 07:48, Raffi Krikorian <
>>>>> <http://ra...@twitter.com> ra...@twitter.com> wrote:
>>>>>> hi all.
>>>>>> 
>>>>>> we launched an endpoint yesterday that allows you to fetch 20 users by
>>>>>> user_id or by screen_name at a time -- we call this our "bulk user show"
>>>>>> API.  for example, to retrieve user objects for user IDs 12863272,
>>>>>> 3191321, 9160152, 8285392 and simultaneously screen names of rsarver and
>>>>>> wilhelmbierbaum, put together the following authenticated request
>>>>>> 
>>>>>>  
>>>>>> <http://api.twitter.com/1/users/lookup.xml?user_id=12863272,3191321,91601
>>>>>> 52,8285392&screen_name=rsarver,wilhelmbierbaum>
>>>>>> http://api.twitter.com/1/users/lookup.xml?user_id=12863272,3191321,916015
>>>>>> 2,8285392&screen_name=rsarver,wilhelmbierbaum
>>>>>> 
>>>>>> and you will receive an XML array of those six user objects.
>>>>>> 
>>>>>> you can find more documentation at
>>>>>> <http://apiwiki.twitter.com/Twitter-REST-API-Method:-users-lookup>
>>>>>> http://apiwiki.twitter.com/Twitter-REST-API-Method:-users-lookup.
>>>>>> 
>>>>>> thanks!
>>> 
>>> 

Re: [twitter-dev] bulk user show API

[Michael Steuer]

OK, let me rephrase... For those of us maintaining a cached social graph for
our users and using the social graph methods to update our cache and then
using user/show to update the user objects, the new method is ³useless² as a
replacement for user/show, where you currently CAN do 20,000/hour assuming
you¹re whitelisted...

I don¹t understand why you would impose the 1,000/hour (ie. 50 calls/hour)
on whitelisted accounts? Isn¹t the stress on Twitter¹s systems for 20,000
individual API calls much bigger than say, 1,000 API call returning somewhat
larger responses ??




On 3/11/10 11:34 AM, "Raffi Krikorian"  wrote:

> i wouldn't necessarily and harshly say "useless" :P  it still prevents you
> from having to make 1000 user/show requests (which you can't do right now).
> 
> 
> On Thu, Mar 11, 2010 at 10:59 AM, Michael Steuer  wrote:
>> Oh wow, I missed that. I understood it was rate limited at 1000 calls/hour
>> (which would come out to 20k user objects)
>> 
>> Having a limit of only 1,000 user objects an hour, renders this new API
>> pretty useless! Come on! I thought the idea was to give developers who now do
>> 10's of thousands of user/show calls a more efficient alternative?!?!
>> 
>> 
>> 
>> On Mar 11, 2010, at 10:11 AM, Abraham Williams <4bra...@gmail.com> wrote:
>> 
>>> My understanding is that it is 50 users/lookup API calls x 20 user objects
>>> per call = 1000 user objects. Not 1000 users/lookup calls of 20 user
>>> objects.
>>> 
>>> Abraham
>>> 
>>> On Thu, Mar 11, 2010 at 10:06, Michael Steuer < <mailto:mste...@gmail.com>
>>> mste...@gmail.com> wrote:
>>>> 
>>>> Erm, doesn¹t 20,000 x users/show equate to 1,000 x users/lookup ?
>>>> 
>>>> Or are you whitelisted for more than 20,000 API calls an hour?
>>>> 
>>>> 
>>>> On 3/11/10 9:53 AM, "Abraham Williams" < <http://4bra...@gmail.com>
>>>> 4bra...@gmail.com> wrote:
>>>> 
>>>>> So for something like Intersect [1] where I have to do sometimes tens of
>>>>> thousands of profile lookups per hour I should stick with users/show? Or
>>>>> can I get an account whitelisted for more lookups per hour?
>>>>> 
>>>>> Abraham
>>>>> 
>>>>> On Thu, Mar 11, 2010 at 07:48, Raffi Krikorian <
>>>>> <http://ra...@twitter.com> ra...@twitter.com> wrote:
>>>>>> hi all.
>>>>>> 
>>>>>> we launched an endpoint yesterday that allows you to fetch 20 users by
>>>>>> user_id or by screen_name at a time -- we call this our "bulk user show"
>>>>>> API.  for example, to retrieve user objects for user IDs 12863272,
>>>>>> 3191321, 9160152, 8285392 and simultaneously screen names of rsarver and
>>>>>> wilhelmbierbaum, put together the following authenticated request
>>>>>> 
>>>>>>  
>>>>>> <http://api.twitter.com/1/users/lookup.xml?user_id=12863272,3191321,91601
>>>>>> 52,8285392&screen_name=rsarver,wilhelmbierbaum>
>>>>>> http://api.twitter.com/1/users/lookup.xml?user_id=12863272,3191321,916015
>>>>>> 2,8285392&screen_name=rsarver,wilhelmbierbaum
>>>>>> 
>>>>>> and you will receive an XML array of those six user objects.
>>>>>> 
>>>>>> you can find more documentation at
>>>>>> <http://apiwiki.twitter.com/Twitter-REST-API-Method:-users-lookup>
>>>>>> http://apiwiki.twitter.com/Twitter-REST-API-Method:-users-lookup.
>>>>>> 
>>>>>> thanks!
>>> 
>>> 

Re: [twitter-dev] bulk user show API

[Michael Steuer]

Oh wow, I missed that. I understood it was rate limited at 1000 calls/ 
hour (which would come out to 20k user objects)


Having a limit of only 1,000 user objects an hour, renders this new  
API pretty useless! Come on! I thought the idea was to give developers  
who now do 10's of thousands of user/show calls a more efficient  
alternative?!?!




On Mar 11, 2010, at 10:11 AM, Abraham Williams <4bra...@gmail.com>  
wrote:


My understanding is that it is 50 users/lookup API calls x 20 user  
objects per call = 1000 user objects. Not 1000 users/lookup calls of  
20 user objects.


Abraham

On Thu, Mar 11, 2010 at 10:06, Michael Steuer   
wrote:


Erm, doesn’t 20,000 x users/show equate to 1,000 x users/lookup ?

Or are you whitelisted for more than 20,000 API calls an hour?


On 3/11/10 9:53 AM, "Abraham Williams" <4bra...@gmail.com> wrote:

So for something like Intersect [1] where I have to do sometimes  
tens of thousands of profile lookups per hour I should stick with  
users/show? Or can I get an account whitelisted for more lookups per  
hour?


Abraham

On Thu, Mar 11, 2010 at 07:48, Raffi Krikorian   
wrote:

hi all.

we launched an endpoint yesterday that allows you to fetch 20 users  
by user_id or by screen_name at a time -- we call this our "bulk  
user show" API.  for example, to retrieve user objects for user IDs 12863272 
, 3191321, 9160152, 8285392 and simultaneously screen names of  
rsarver and wilhelmbierbaum, put together the following  
authenticated request


http://api.twitter.com/1/users/lookup.xml?user_id=12863272,3191321,9160152,8285392&screen_name=rsarver,wilhelmbierbaum

and you will receive an XML array of those six user objects.

you can find more documentation at http://apiwiki.twitter.com/Twitter-REST-API-Method:-users-lookup 
.


thanks!



--
Abraham Williams | Community Advocate | http://abrah.am
TwitterOAuth | http://github.com/abraham/twitteroauth
This email is: [ ] shareable [x] ask first [ ] private.

Re: [twitter-dev] bulk user show API

[Michael Steuer]

Erm, doesn¹t 20,000 x users/show equate to 1,000 x users/lookup ?

Or are you whitelisted for more than 20,000 API calls an hour?


On 3/11/10 9:53 AM, "Abraham Williams" <4bra...@gmail.com> wrote:

> So for something like Intersect [1] where I have to do sometimes tens of
> thousands of profile lookups per hour I should stick with users/show? Or can I
> get an account whitelisted for more lookups per hour?
> 
> Abraham
> 
> On Thu, Mar 11, 2010 at 07:48, Raffi Krikorian  wrote:
>> hi all.
>> 
>> we launched an endpoint yesterday that allows you to fetch 20 users by
>> user_id or by screen_name at a time -- we call this our "bulk user show" API.
>>  for example, to retrieve user objects for user IDs 12863272, 3191321,
>> 9160152, 8285392 and simultaneously screen names of rsarver and
>> wilhelmbierbaum, put together the following authenticated request
>> 
>> http://api.twitter.com/1/users/lookup.xml?user_id=12863272,3191321,9160152,82
>> 85392&screen_name=rsarver,wilhelmbierbaum
>> 
>> and you will receive an XML array of those six user objects.
>> 
>> you can find more documentation at
>> http://apiwiki.twitter.com/Twitter-REST-API-Method:-users-lookup.
>> 
>> thanks!

Re: [twitter-dev] Tracking number of users for an OAuth app

[Michael Steuer]

Wouldn't you yourself know best how to calculate how many people are
actively using your app?


On 3/9/10 5:14 PM, "SM"  wrote:

> On the application detail page there is a stat that shows how many
> users your app has.
> 
> How is this stat calculated? Is it the number of authorized tokens or
> does it reflect some rolling count of accesses using an authorized
> token? Or some other calculation?
> 
> If someone uses my app once and then forgets about it, will that
> person continue to be counted as a user since tokens never expire?
> 
> I'm hoping it is a stat that actually tracks how many people are
> actively using your app.
> 
> Thanks.

Re: [twitter-dev] Processing 'dead' users

[Michael Steuer]

Why not simply delete the user from your db as part of your weekly  
process when you get the Could Not Authentica You error in the first  
place?




On Feb 17, 2010, at 12:11 PM, Scott Wilcox  wrote:


Hello,

At tweekly.fm we probably have around 1000-2000 accounts where users  
haven't removed their accounts and have just removed permission for  
the app to run. Once our weekly processes run, they return the  
expected 'Could not authenticate you' errors.


Whats going to be the best way to run through these and remove upon  
no permissions? Run verifyCredentials on each user? Or does anyone  
have any better ideas?


Scott.

Re: [twitter-dev] Tweets is spelled wrong

[Michael Steuer]

Tweeps = Twitter peeps



On Feb 9, 2010, at 4:18 PM, My Network Factory  
 wrote:



On the "List Widget" page the word "tweets" is spelled with a letter
'p'.


List Widget

Put your favorite tweeps into a list! Then show 'em off in a widget.
Also great for moderation.

Re: [twitter-dev] A proposal for delegation in OAuth identity verification

[Michael Steuer]

Hi Raffi,

Very pleased that this went out... I've been pushing for this on this list
for quite a while now...

Let us know if you need any help in any way...

As a side note - TweetPhoto has claimed on this list that they have some
sort of oAuth delegation live?? I haven't played with it yet, but perhaps
someone who has can comment on what it actually is that they've done?

Thanks,

Michael.

On Tue, Feb 9, 2010 at 4:13 PM, Raffi Krikorian  wrote:

> hi all.
>
> i apologise that i'm running behind on getting these out, but i've put out
> the first in a series of blog posts regarding what twitter is doing with
> oauth moving forward -- this one, specifically, is a RFC around "delegation
> in OAuth identity verification".  a total mouthful, i know, so it may help
> to think about it in a concrete example:
>
> You're an OAuth enabled Twitter client, and you've already authorized your
>> user.  You user wants to use a media providing service like TwitPic.
>>  TwitPic, currently, asks for the username and password of your user so it
>> can store the photo on behalf of the Twitter user.  You don't have that
>> username and password, so how do you give the ability to TwitPic to verify
>> the identity of your user?
>
>
> that being said, please check out
> http://mehack.com/a-proposal-for-delegation-in-oauth-identity-v.
>
> thanks!
>
> --
> Raffi Krikorian
> Twitter Platform Team
> http://twitter.com/raffi
>

Re: [twitter-dev] Re: Link to Individual DM

[Michael Steuer]

Considering a DM is always exclusive to 1 single user, enabling the  
ability to share a link to it seems somewhat useless? What's your use  
case?




On Feb 8, 2010, at 7:25 PM, Dewald Pretorius  wrote:


Jesse,

I don't think a DM has a permalink. Even in the Twitter web interface,
there is no way to look at or isolate one individual DM.

On Feb 8, 8:26 pm, Jesse Stay  wrote:
I'm trying to find a format that allows me to link directly to  
individual

DMs on Twitter - is this possible?  Googling isn't finding anything.

Jesse

Re: [twitter-dev] Re: Mobile OAuth fix is LIVE

[Michael Steuer]

And for QA, if you're not able to procure each commercially available  
handset, check out www.deviceanywhere.com. Or if you prefer to  
outsource, hit me up off list, I can give you a list of reputable  
mobile QA houses.




On Feb 6, 2010, at 7:40 AM, Dewald Pretorius  wrote:


Ryan,

Don't know if it will fit in with your architecture, but maybe this
service could be of use to you:

http://wapple.net/


On Feb 6, 12:39 am, Ryan Sarver  wrote:
Ill talk with the team and figure out if it's better to roll it  
back or just

limit it to the known, working user agents

On Fri, Feb 5, 2010 at 3:42 PM, CharlesW  wrote:

That's an amazingly great recommendation, Michael.



-- Charles



On Feb 5, 9:22 am, Michael Steuer  wrote:
In fact, I'd recommend that you only show the new version for  
devices you
have actually tested against... Mobile browser support is a crap  
shoot

and
you really can't assume that something that works on one device,  
works on
another... You need to test each and every one of them (or at  
least each
family of devices, e.g. Series 60 4th Gen, Series 60 5th Gen,  
iPhone OS,
Motorola V3 series, etc.) I've been in mobile development for 15  
years...

Let me know if you need some pointers off list... Happy to assist.



On 2/5/10 8:40 AM, "CharlesW"  wrote:> Ryan,



Thanks for both the attempted fix and the announcement.


Unfortunately, where the previous version was kind of a  
crapshoot for
mobile users because the buttons appeared black (see my  
screenshot in

the bug report athttp://

code.google.com/p/twitter-api/issues/detail?id=395),

this new version doesn't work at all on many mobile browsers.


Because this breaks mobile Twitter support completely for many  
(most?

all?) phones using older browsers, can you please revert to the
previous version, and then stage a new version somewhere else  
that we

can help you test?



-- Charles



On Feb 3, 3:16 pm, Ryan Sarver  wrote:

FINALLY!


An update has just gone live that fixes rendering of the OAuth  
screens

for
most mobile devices. We also fixed a few small nagging things  
like the
default action is now "allow" instead of deny if you just hit  
"go" on

an

iPhone. I've attached two screenshots so you can see the updated

screens.


Please test it out with your various mobile web apps and let us  
know

if you

run into any problems or edge cases.



Ryan



 IMG_0739.png
93KViewDownload



 IMG_0738.png
75KViewDownload

Re: [twitter-dev] Re: Mobile OAuth fix is LIVE

[Michael Steuer]

In fact, I'd recommend that you only show the new version for devices you
have actually tested against... Mobile browser support is a crap shoot and
you really can't assume that something that works on one device, works on
another... You need to test each and every one of them (or at least each
family of devices, e.g. Series 60 4th Gen, Series 60 5th Gen, iPhone OS,
Motorola V3 series, etc.) I've been in mobile development for 15 years...
Let me know if you need some pointers off list... Happy to assist.


On 2/5/10 8:40 AM, "CharlesW"  wrote:

> Ryan,
> 
> Thanks for both the attempted fix and the announcement.
> 
> Unfortunately, where the previous version was kind of a crapshoot for
> mobile users because the buttons appeared black (see my screenshot in
> the bug report at http://code.google.com/p/twitter-api/issues/detail?id=395),
> this new version doesn't work at all on many mobile browsers.
> 
> Because this breaks mobile Twitter support completely for many (most?
> all?) phones using older browsers, can you please revert to the
> previous version, and then stage a new version somewhere else that we
> can help you test?
> 
> -- Charles
> 
> 
> On Feb 3, 3:16 pm, Ryan Sarver  wrote:
>> FINALLY!
>> 
>> An update has just gone live that fixes rendering of the OAuth screens for
>> most mobile devices. We also fixed a few small nagging things like the
>> default action is now "allow" instead of deny if you just hit "go" on an
>> iPhone. I've attached two screenshots so you can see the updated screens.
>> 
>> Please test it out with your various mobile web apps and let us know if you
>> run into any problems or edge cases.
>> 
>> Ryan
>> 
>>  IMG_0739.png
>> 93KViewDownload
>> 
>>  IMG_0738.png
>> 75KViewDownload

Re: [twitter-dev] Re: How Does TwittPic Works ?

[Michael Steuer]

That's awesome. Please let us know when you do!

Michael.



On Feb 4, 2010, at 6:33 PM, Raffi Krikorian  wrote:


i'll be posting our proposal for "oauth delegation" soon as a RFC.

On Thu, Feb 4, 2010 at 3:41 PM, Greg  wrote:
However - will we ever see the ability for 3rd party applications to
talk to eachother using oAuth tokens? For example a custom twitter
oAuth application using TwitPic to publish photos?

On Feb 4, 6:26 pm, Raffi Krikorian  wrote:
> totally.
>
>
>
> On Thu, Feb 4, 2010 at 3:23 PM, Abraham Williams  
<4bra...@gmail.com> wrote:

> > I would imagine that Twitter will require SSL for xAuth calls.
>
> > Abraham
>
> > On Thu, Feb 4, 2010 at 14:44, Dewald Pretorius  
 wrote:

>
> >> Interesting, Abraham.
>
> >> Don't we ever need OAuth Wrap, otherwise that x-auth-password  
will be
> >> sent in clear text, kind of making a mockery of the whole OAuth  
thing.

>
> >> On Feb 4, 6:35 pm, Abraham Williams <4bra...@gmail.com> wrote:
> >> > I poked around Seesmic Look a little and this is what I found:
> >>http://the.hackerconundrum.com/2010/02/sneak-peek-at-twitters-browser 
...

>
> >> > Abraham
>
> >> > On Thu, Feb 4, 2010 at 14:24, Dewald Pretorius  


> >> wrote:
> >> > > Zach,
>
> >> > > There's a soon to be published API method where you can  
silently get
> >> > > the OAuth tokens when you have the account's Twitter  
username and
> >> > > password, meaning the user does not experience any of the  
normal OAuth

> >> > > flow.
>
> >> > > I presume that Seesmic just got early access to that method.
>
> >> > > So, in this case, user-to-app requires Basic Auth  
credentials, but

> >> app-
> >> > > to-Twitter uses OAuth once the app has obtained the tokens  
with the

> >> > > new method.
>
> >> > > On Feb 4, 4:21 pm, Zac Bowling  wrote:
> >> > > > Yes, what magic is this?
>
> >> > > > I'm confused. It takes username and password but then  
uses OAuth?

>
> >> > > > I wonder if they are injecting the username/password into  
the OAuth

> >> form
> >> > > on
> >> > > > the page.
>
> >> > > > Twitter should really randomize that page or require  
captcha or

> >> > > something.
>
> >> > > > Zac Bowling
>
> >> > > > On Wed, Feb 3, 2010 at 11:43 AM, Dewald Pretorius  

>
> >> > > wrote:
> >> > > > > Raffi,
>
> >> > > > > Have you tried it? There is no OAuth flow. I.e., the  
user types in

> >> his
> >> > > > > Twitter username and password. That's it.
>
> >> > > > > If it is indeed using OAuth, does that mean that the  
background
> >> > > > > requesting of tokens when you have the Twitter  
credentials is now
> >> > > > > available? Meaning, I can also now use it to convert  
all existing

> >> > > > > Twitter accounts to OAuth in one fell swoop?
>
> >> > > > > On Feb 3, 3:02 pm, Raffi Krikorian   
wrote:

> >> > > > > > seesmic look, i believe, is using oauth talking to
> >> api.twitter.com.
>
> >> > > > > > On Tue, Feb 2, 2010 at 8:09 PM, Dewald Pretorius <
> >> dpr...@gmail.com>
> >> > > > > wrote:
> >> > > > > > > Raffi,
>
> >> > > > > > > What's going on here?
>
> >> > > > > > > Your credibility is at stake here. You've been  
telling us in

> >> many
> >> > > > > > > posts that new apps must use OAuth to get a source
> >> attribution, and
> >> > > > > > > only old grandfathered apps have source attribution  
with Basic

> >> > > Auth.
>
> >> > > > > > > On Feb 2, 11:18 pm, Dewald Pretorius  


> >> wrote:
> >> > > > > > > > At first I thought they must have changed the old  
Seesmic

> >> source
> >> > > to
> >> > > > > > > > Seesmic Look.
>
> >> > > > > > > > But no.
>
> >> > > > > > > > Here's a recent tweet from Seesmic:
> >> > > > > > >http://twitter.com/CathyBrooks/status/8570217879
>
> >> > > > > > > > And here's a recent one from Seesmic Look:
> >> > > > > > >http://twitter.com/adamse/status/8565271563
>
> >> > > > > > > > Seesmic Look uses Basic Auth.
>
> >> > > > > > > > Does anyone else spot Mt Everest on this level  
playing field

> >> of
> >> > > ours?
>
> >> > > > > > > > On Feb 2, 10:41 pm, Pedro Junior  


> >> wrote:
>
> >> > > > > > > > > *Seesmic Look is old?
> >> > > > > > > > > *
> >> > > > > > > > > -
> >> > > > > > > > > Pedro Junior
>
> >> > > > > > > > > 2010/2/2 Lukas Müller e>

>
> >> > > > > > > > > > Only old apps can do this. New apps cannot  
use it.

>
> >> > > > > > --
> >> > > > > > Raffi Krikorian
> >> > > > > > Twitter Platform Teamhttp://twitter.com/raffi
>
> >> > --
> >> > Abraham Williams | Community Advocate |http://abrah.am
> >> > Project | Out Loud |http://outloud.labs.poseurtech.com
> >> > This email is: [ ] shareable [x] ask first [ ] private.
> >> > Sent from Seattle, WA, United States
>
> > --
> > Abraham Williams | Community Advocate |http://abrah.am
> > Project | Out Loud |http://outloud.labs.poseurtech.com
> > This email is: [ ] shareable [x] ask first [ ] private.
> > Sent from Seattle, WA, United States
>
> --
> Raffi Krikorian
> Twitter Platform Teamhttp://twitter.com/raffi



--
Raffi Krikorian
Twitter Platform Team
http://twitter.co

Re: [twitter-dev] Bulk User Look Up - any progress?

[Michael Steuer]

Thanks Ryan



On Feb 3, 2010, at 6:36 PM, Ryan Sarver  wrote:


Michael,

It is definitely on our near-term roadmap, but we've gotten backed  
up on a few other things. So it is still coming, but I don't have an  
exact date for you. Social graph relief is neigh :)


Best, Ryan

On Wed, Feb 3, 2010 at 3:39 PM, Michael Steuer   
wrote:

Hi Raffi et al,

Is there any word on when we might see a bulk user lookup API, as  
promised repeatedly in this group? For those of us using the social  
graph APIs, it’s incredibly painful to then have to fetch the full u 
ser object based on the ID one-by-one.


Anyway, would just love to know if this is on the horizon or if we  
should all continue to dream about this...


Thanks,

Michael

[twitter-dev] Bulk User Look Up - any progress?

[Michael Steuer]

Hi Raffi et al,

Is there any word on when we might see a bulk user lookup API, as promised
repeatedly in this group? For those of us using the social graph APIs, it¹s
incredibly painful to then have to fetch the full user object based on the
ID one-by-one.

Anyway, would just love to know if this is on the horizon or if we should
all continue to dream about this...

Thanks,

Michael

Re: [twitter-dev] Are geotagged tweets visually apparent?

[Michael Steuer]

Hi Jeffrey,

The Twitter web site does not display geotag information. Use a  
Twitter service that does, such as http://bccth.is, to confirm  
successful tagging of your tweets. Of course, retrieving the tweets in  
question via the API, would also reveal the geotag info.


Best,

Michael



On Feb 2, 2010, at 9:25 PM, Jeffrey Friedl  wrote:


I'm testing geotagging in an app, and the reply to the status update
indicates that the geotagged location was accepted, but when I view
the tweet on twitter.com, I can find no indication that the tweet has
been geotagged. In the end, I can't tell the difference between
failure and success...

I was under the impression that the "not yet available on the web
site" comment was for users geotagging their tweets from twitter.com,
but it seems that geotagging is completely invisible on the web site?

Am I missing something?
Thanks,
Jeffrey
--- 
--- 
--- 
--- 
--

Jeffrey Friedl , Kyoto Japan , http://regex.info/blog/

Re: [twitter-dev] Re: Possibility to link to the user page not by the name but by the id.

[Michael Steuer]

If user  is no longer the same user as the one that posted status  
id , then the link  http://twitter.com//statuses/ would no  
longer be valid (as the NEW user  is not the owner of the status  
id).




On Jan 30, 2010, at 11:40 PM, Ivan Glushkov  wrote:


Actually i can't.
For example, i get some link like
http://twitter.com/AAA/statuses/11, for the message that was
posted month ago. I can't be sure if the current user AAA has the same
guid as the AAA month ago.
If i had the link like http://twitter.com/redirect?id=111&status=222 i
would be sure that it's the same user and the same status for that
user.

Ivan.


On Sun, Jan 31, 2010 at 9:36 AM, Michael Ivey  
 wrote:
You could do this internally in your application, using statuses/ 
show to

make sure you have the correct user info before redirecting.
 -- ivey


On Sat, Jan 30, 2010 at 4:06 AM, Ivan Glushkov   
wrote:


Oh, thanks, Abraham! That's great!

But why isn't it documented anywhere?
And is there any way to redirect to some status of this user?
I mean smth like
http://twitter.com/account/redirect_by_id?id=9436992&status=3
???

Thanks once more,
Ivan.


On Fri, Jan 29, 2010 at 11:37 PM, Abraham Williams <4bra...@gmail.com 
>

wrote:

Actually Twitter does support it.
http://twitter.com/account/redirect_by_id?id=9436992
Abraham

On Wed, Jan 27, 2010 at 06:42, Ivan  wrote:


Hi.

I don't need an application that is able to handle this. Instead i
need changes in the twitter API so i can refer to the users and  
their
statuses using the user id, not the username. This is a problem  
for
the aggregator, and there users (so it become also a problem for  
the

twitter users).

Is there any plan in this direction?

Ivan.


On 21 янв, 06:03, Abraham Williams <4bra...@gmail.com> wrote:

I remember this topic coming up before and it seems like someone
built
an
application that handled this but I can't find any references  
to it.

Maybe
somebody else can?

Abraham



On Wed, Jan 20, 2010 at 06:29, Ivan  wrote:

Hi.



I tried to find the similar question here (in google groups), in
the
FAQ and in the API, but couldn't find anything.



The problem:
Cross-posting the links to the user page and to some his  
statuses

in
the web become more and more popular. But, as i understood, you
can't
guarantee that this links not long after would not change the
logical
destination. For example I create some post about some twitter- 
user

"aaa" and give the link "twitter.com/aaa"
After that user “aaa” changed name to "bbb" and user "dd 
d" changed
name to "aaa". So my old link now points to the different  
person.



This problem becomes more serious for the aggregators that don't
know
what content they might approve after a while.


The simplest decision would be providing the possibility to  
link to

the user not by name but also by id. That pages might be just
redirections to the original user pages, it doesn't matter.



For example
if the user “aaa” have id 11, the following two link 
s should

point
to the same page:
twitter.com/aaa and twitter.com/id/11



This mechanism should also be applied for the statuses:
twitter.com/id/11/statuses/22



Ivan.


--
Abraham Williams | Moved to Seattle | May cause email delays
Project | Intersect |http://intersect.labs.poseurtech.com
Hacker |http://abrah.am|http://twitter.com/abraham
This email is: [ ] shareable [x] ask first [ ] private.
Sent from Seattle, WA, United States




--
Abraham Williams | Moved to Seattle | May cause email delays
Project | Out Loud | http://outloud.labs.poseurtech.com
Hacker | http://abrah.am | http://twitter.com/abraham
This email is: [ ] shareable [x] ask first [ ] private.
Sent from Seattle, WA, United States

Re: [twitter-dev] Re: Rate limit HTTP response

[Michael Steuer]

We see this too now on a bunch of our test accounts.. Does Twitter have a 
resolution time?

It's making the use and development efforts of our application all but 
impossible...


On Jan 28, 2010, at 1:51 PM, Rich wrote:

> Interesting my whitelisted account is still working, but the non
> whitelisted ones are broken over oAuth
> 
> On Jan 28, 9:48 pm, Rich  wrote:
>> Just run it through my debugger, it's absolutely returning an HTTP 400
>> response
>> 
>> On Jan 28, 9:46 pm, Rich  wrote:
>> 
>> 
>> 
>>> Looks like they are in the process of upping the oAuth rate limit as
>>> now I'm getting different results but still a 400 error
>> 
>>> On Jan 28, 9:41 pm, Shelkie  wrote:
>> 
 Are others having trouble with Ratelimits?
>> 
 Suddenly the "X-Ratelimit-Limit" has changed to 0 for several accounts
 I have checked. Here are some sample HTTP headers:
>> 
  [Date] => Thu, 28 Jan 2010 21:27:55 GMT
  [Server] => hi
  [X-Ratelimit-Limit] => 0
  [Status] => 400 Bad Request
  [X-Ratelimit-Remaining] => 0
  [X-Runtime] => 0.02640
  [Content-Type] => application/json; charset=utf-8
  [Content-Length] => 412
  [X-Ratelimit-Class] => api_identified
  [Cache-Control] => no-cache, max-age=300
  [X-Ratelimit-Reset] => 1264716226
>> 
 Notice that X-Ratelimit-Reset is also out of date when compared to
 ["Date"]
>> 
 Any ideas? Could our app have been blacklisted for some reason, or is
 this a more widespread problem?
>> 
 Eric.

Re: [twitter-dev] getting more information than 'Could not authenticate...'

[Michael Steuer]

What language are you developing in? Why are you not using a tried and  
tested Twitter API library (ie. Why reinvent the wheel?)?




On Jan 24, 2010, at 9:33 PM, eco_bach  wrote:


Hi
I've spent the last week getting the OAuth sign-In process to work,
and I've finallly got it to work(verify credentials correctly returns
a user's info), BUT, I am unable to update a user's status.

The server always returns 'Could not authenticate...'
For obvious reasons, Twitter's server can't return a more specific
error message.

Is there any way of communcating directly with someone on Twitter's
server side (ie a real person), so I can pinpoint exactly why I'm not
being authenticated?
might save me another 1-2 weeks of hair pulling...

Re: [twitter-dev] Re: geo tag and direct messages?

[Michael Steuer]

And in_reply_to_dm_id for that matter?



On Jan 22, 2010, at 11:32 AM, Gimme  wrote:


Raffi,

What's road map to implement geo tag in DM?



On Nov 23 2009, 11:55 am, Raffi Krikorian  wrote:

hi!

DMs do not yet have the ability to be geotagged - its on our list!

I sent couple of DMs with mobile to see what geo is populated.  
When I

retrieve DM's from my userID, it says geo_enabled true, but status
does not have coordinates populated? am I missing something?
pls.suggest.


--
Raffi Krikorian
Twitter Platform Team
ra...@twitter.com | @raffi

Re: [twitter-dev] Re: Social Graph API: Legacy data format will be eliminated 1/11/2010

[Michael Steuer]

Ditto


On 1/4/10 7:58 PM, "Jesse Stay"  wrote:

> Ditto PJB :-)
> 
> On Mon, Jan 4, 2010 at 8:12 PM, PJB  wrote:
>> 
>> I think that's like asking someone: why do you eat food? But don't say
>> because it tastes good or nourishes you, because we already know
>> that! ;)
>> 
>> You guys presumably set the 5000 ids per cursor limit by analyzing
>> your user base and noting that one could still obtain the social graph
>> for the vast majority of users with a single call.
>> 
>> But this is a bit misleading.  For analytics-based apps, who aim to do
>> near real-time analysis of relationships, the focus is typically on
>> consumer brands who have a far larger than average number of
>> relationships (e.g., 50k - 200k).
>> 
>> This means that those apps are neck-deep in cursor-based stuff, and
>> quickly realize the existing drawbacks, including, in order of
>> significance:
>> 
>> - Latency.  Fetching ids for a user with 3000 friends is comparable
>> between the two calls.  But as you increment past 5000, the speed
>> quickly peaks at a 5+x difference (I will include more benchmarks in a
>> short while).  For example, fetching 80,000 friends via the get-all
>> method takes on average 3 seconds; it takes, on average, 15 seconds
>> with cursors.
>> 
>> - Code complexity & elegance.  I would say that there is a 3x increase
>> in code lines to account for cursors, from retrying failed cursors, to
>> caching to account for cursor slowness, to UI changes to coddle
>> impatient users.
>> 
>> - Incomprehensibility.  While there are obviously very good reasons
>> from Twitter's perspective (performance) to the cursor based model,
>> there really is no apparent obvious benefit to API users for the ids
>> calls.  I would make the case that a large majority of API uses of the
>> ids calls need and require the entire social graph, not an incomplete
>> one.  After all, we need to know what new relationships exist, but
>> also what old relationships have failed.  To dole out the data in
>> drips and drabs is like serving a pint of beer in sippy cups.  That is
>> to say: most users need the entire social graph, so what is the use
>> case, from an API user's perspective, of NOT maintaining at least one
>> means to quickly, reliably, and efficiently get it in a single call?
>> 
>> - API Barriers to entry.  Most of the aforementioned arguments are
>> obviously from an API user's perspective, but there's something, too,
>> for Twitter to consider.  Namely, by increasing the complexity and
>> learning curve of particular API actions, you presumably further limit
>> the pool of developers who will engage with that API.  That's probably
>> a bad thing.
>> 
>> - Limits Twitter 2.0 app development.  This, again, speaks to issues
>> bearing on speed and complexity, but I think it is important.  The
>> first few apps in any given media or innovation invariably have to do
>> with basic functionality building blocks -- tweeting, following,
>> showing tweets.  But the next wave almost always has to do with
>> measurement and analysis.  By making such analysis more difficult, you
>> forestall the critically important ability for brands, and others, to
>> measure performance.
>> 
>> - API users have requested it.  Shouldn't, ultimately, the use case
>> for a particular API method simply be the fact that a number of API
>> developers have requested that it remain?
>> 
>> 
>> On Jan 4, 2:07 pm, Wilhelm Bierbaum  wrote:
>>> > Can everyone contribute their use case for this API method? I'm trying
>>> > to fully understand the deficiencies of the cursor approach.
>>> >
>>> > Please don't include that cursors are slow or that they are charged
>>> > against the rate limit, as those are known issues.
>>> >
>>> > Thanks.
> 
> 

Re: [twitter-dev] How to retrieve url link written in a tweet please?

[Michael Steuer]

Try regular expressions on the status text...



On Dec 26, 2009, at 9:25 AM, humbucker   
wrote:



Hello,

When I perform a twitter search from a jquery file, I get something
like this :

{"results":[{
"profile_image_url":"http://a1.twimg.com/profile_images/304998018/
icon_128_normal.png",
"created_at":"Sat, 26 Dec 2009 13:05:18 +",
"from_user":"web2feed","to_user_id":null,
"text":"RT @rodrigocunha85: Algu\u00e9m ainda se lembra dos
transferidores e cat\u00e1logos da Letraset? http://twitpic.com/vb1xi
#design #tipografia",
"id":7060359872,"from_user_id":27624855,
"geo":null,"iso_language_code":"pt",
"source":"TwiBots"},

I would like to be able to retrieve the url written in the tweet text,
e.g (here we got a twitpic url)

How can this be achieved please ?

Many many thanks for your help.

Re: [twitter-dev] Re: Social Graph API: Legacy data format will be eliminated 1/11/2010

[Michael Steuer]

+1 - I'm currently relying on retrieving a complete social graph when  
no cursor is passed. Your announcing this change right around Xmas+new  
years to take effect almost immediately thereafter...






On Dec 23, 2009, at 10:00 PM, PJB  wrote:



Why hasn't this been announced before?  Why does the API suggest
something totally different?  At the very least, can you please hold
off on deprecation of this until 2/11/2010?  This is a new API change.

On Dec 23, 7:45 pm, Raffi Krikorian  wrote:
yes - if you do not pass in cursors, then the API will behave as  
though you

requested the first cursor.




Willhelm:


Your announcement is apparently expanding the changeover from page  
to

cursor in new, unannounced ways??



The API documentation page says: "If the cursor parameter is not
provided, all IDs are attempted to be returned, but large sets of  
IDs

will likely fail with timeout errors."


Yesterday you wrote: "Starting soon, if you fail to pass a cursor,  
the

data returned will be that of the first cursor (-1) and the
next_cursor and previous_cursor elements will be included."


I can understand the need to swap from page to cursor, but was  
pleased

that a single call was still available to return (or attempt to
return) all friend/follower ids.  Now you are saying that, in  
addition

to the changeover from page to cursor, you are also getting rid of
this?



Can you please confirm/deny?



On Dec 22, 4:13 pm, Wilhelm Bierbaum  wrote:

We noticed that some clients are still calling social graph methods
without cursor parameters. We wanted to take time to make sure that
people were calling the updated methods which return data with  
cursors

instead of the old formats that do not.



As previously announced in September (http://bit.ly/46x1iL) and
November (http://bit.ly/3UQ0LU), the legacy data formats returned
as a result of calling social graph endpoints without a cursor
parameter are deprecated and will be removed.



These formats have been removed from the API wiki since September.


You should always pass a cursor parameter. Starting soon, if you  
fail
to pass a cursor, the data returned will be that of the first  
cursor
(-1) and the next_cursor and previous_cursor elements will be  
included.


If you aren't seeing next_cursor and previous_cursor in your  
results,
you are getting data back in the old format. You will need to  
adjust

your parser to handle the new format.



We're going to start assuming you want data in the new format
(users_list / users / user or id_list / ids / id) instead of the  
old
format (users / user or ids / id) regardless of your passing a  
cursor

parameter as of 1/11/2010.



* The old formats will no longer be returned after 1/11/2010.
* Start using the new formats now by passing the 'cursor'  
parameter.



To recap, the old endpoints at



   /statuses/friends.xml
   /statuses/followers.xml



returned




  
  
  




or JSON like [{/*user record*/ /*, .../]



whereas



/statuses/friends.xml?cursor=n
/statuses/followers.xml?cursor=n



return data that looks like




  
  
  
  
  
  7128872798413429387
  0




or, the JSON equivalent:



{"users":[{/*user record*/} /*, ...*/], "next_cursor":0,
"previous_cursor":0}



and the old endpoints at



/friends/ids.xml
/followers/ids.xml



returned data that looks like




  1
  2
  3




whereas



/friends/ids.xml?cursor=n
/followers/ids.xml?cursor=n



return data that looks like




  
1
2
3
  
  1288724293877798413
  -1300794057949944903




or, the JSON equivalent:



{"ids":[1, 2, 3], "next_cursor":0, "previous_cursor":0}


If you have any questions or comments, please feel free to post  
them

to twitter-development-talk.



Thanks!



--
Wilhelm Bierbaum
Twitter Platform Team


--
Raffi Krikorian
Twitter Platform Teamhttp://twitter.com/raffi

Re: [twitter-dev] Re: .NET Servers

[Michael Steuer]

I concur, we too got accepted by BizSpark within 2-3 days from  
application...




On Dec 22, 2009, at 7:24 AM, Andrew Badera  wrote:


Hey Shannon,

The application process can be expedited if the network partner knows
you and pushes it. If you want a referral to a reliable partner, hit
me up off-list.

This current project, we applied and got approved <48 hours.

I like the shared DB thought.

--ab


On Tue, Dec 22, 2009 at 10:20 AM, Shannon Whitley
 wrote:
Thanks for the feedback, Andy.  I'll run your thoughts past GoGrid  
and

see what they can do.  I could offer 2008 at the same price as 2003
(if I drop the memory), but in my experience it's not even worth
trying to run 2008 on less than a GB of RAM.

I also want to know more about the ease with which folks can join
BizSpark.  I applied, but haven't heard anything back.  One of my
ideas was to run a shared SQL Server database for multiple developers
under the BizSpark program.

Re: [twitter-dev] Re: Questions about opening the firehose

[Michael Steuer]

Just so we all can guestimate if we're equiped for and financially  
able to consider consumption of the firehose, in average, what's the  
daily data throughput on a firehose stream?


Thanks,

Michael.



On Dec 15, 2009, at 9:38 AM, John Kalucki  wrote:

The other levels of Streaming access are not only considerably more  
cost effective for all parties, they are also (nearly) sufficient  
for the vast majority of applications.


-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.


On Mon, Dec 14, 2009 at 10:16 PM, M. Edward (Ed) Borasky > wrote:

Thanks!! At this point, I'm not sure I'll be using the firehose even
if it is available -I don't think I can afford the pipe width to
consume it. ;-)

On Dec 14, 9:59 pm, John Kalucki  wrote:
> There will be further announcements about Streaming API access  
early next

> year.
>
> -John Kaluckihttp://twitter.com/jkalucki
> Services, Twitter Inc.
>
> On Mon, Dec 14, 2009 at 9:09 PM, M. Edward (Ed) Borasky  
wrote:

>
> > Last week at Le Web, Twitter's Platform Director, Ryan Sarver,
> > announced that Twitter will be "opening the firehose to all
> > developers." As I recall, there were a number of reasons why  
Twitter

> > kept the firehose restricted. Some of these were "legal reasons".
>
> > I'm starting to put together an action plan for 2010, and I'm  
really
> > curious - what has changed legally since then that would allow  
Twitter

> > to open the firehose to "all developers?" What legal agreements /
> > licenses / contracts must a developer commit to in order to gain
> > access to the firehose?
>
> > --
> > M. Edward (Ed) Borasky
> >http://borasky-research.net
>
> > "I've always regarded nature as the clothing of God." ~Alan  
Hovhaness

Re: [twitter-dev] Direct message Ids

[Michael Steuer]

I don't know for sure but as tweet id's are sequential and the current  
dm id counter is way lower than the current tweet id, I would assume  
they're separate sets...





On Dec 13, 2009, at 10:25 PM, Harshad RJ  wrote:


Hi,

Are the DM ids unique within {DMs + Tweets} set or only in the {DM}  
set?


In other words, if I am storing a collection of DMs and Tweets in a  
DB, can I index it safely using DM.id and Tweet.id ?


thanks,
--
Harshad RJ
http://hrj.wikidot.com

Re: [twitter-dev] extract all @replies for a user

[Michael Steuer]

Check out the statuses/mentions API



On Dec 11, 2009, at 3:19 PM, Baron  wrote:


hello,

I want to get all the @replies for a user using the API. I tried using
search (http://apiwiki.twitter.com/Twitter-Search-API-Method:-search)
but it only gives me access to the last 7 days of tweets. Is it
possible to access all @replies for a user, or atleast more than 7
days worth?

regards,
Baron

Re: [twitter-dev] Re: A New API For Browserless Apps?

[Michael Steuer]

I agree with Duane... A lot of us have implemented oAuth on Twitter's strong
urging and continue to be "punished" for it by none other than Twitter... Of
course consumers will prefer clients with the easier log in flow, giving
unfair benefit to apps that just request the un/pw instead of redirecting to
Twitter (realize that though we all know that it's not advisable to give
your Twitter credentials to a third party site, however 90% of the consumers
out there wouldn't think twice about it and will make their choice based on
ease of use). And secondly, yes I am a broken record on this topic, the
inability to consume or provide 3rd party APIs from/to apps that rely on
oAuth, as delegation isn't supported (though Raffi confirmed this morning
that sometime between now and when hell freezes over, Twitter will provide a
solution to this). 

If it's now Twitter's stance that it's okay to ask your users for their
Twitter un/pw, then let's all switch to that immediately... It'll allow me
to consumer and/offer 3rd party APIs, I can use basic auth for the next 6.5
months, and then switch to this proposed fake oauth in June by requesting
tokens using the user's username/password...


On 12/10/09 10:40 AM, "Duane Roelands"  wrote:

> Many of us in the developer community have been strongly pushing the
> point of view that third-party apps should never be asking for user
> credentials.  We did so because we believed that Twitter was firmly
> committed to the security of the ecosystem and protecting the accounts
> of its users.  It now appears that this belief was in error.
> 
>   This decision is going to actively hurt developers who chose the
> more secure implementation.  Application A just lets me log in with my
> Twitter credentials, but Application B wants me to go through this
> harder process.  Most users will choose option A, and the more-secure
> application B loses users.  this decision punishes developers who
> chose the more secure model.  It's disappointing, because a lot of
> developers have worked very hard to bring OAuth implementations to the
> community that were robust and secure and **didn't require a user to
> hand over their Twitter credentials**.
> 
> There was a great opportunity here for Twitter to be a security leader
> in the social network space by saying "We don't want our users giving
> their Twitter credentials to anyone except Twitter".  It's a shame
> they didn't stick to their gun; the result is going to be a less-
> secure ecosystem.

Re: [twitter-dev] Re: A New API For Browserless Apps?

[Michael Steuer]

Great to hear it¹s on your radar and you¹re actively working on it. Any
chance you¹ll involve the dev community prior to presenting the solution as
a fait-accompli? And do you have an idea around timing for this solution?


On 12/10/09 9:55 AM, "Raffi Krikorian"  wrote:

> we're not unwilling to answer the question.  it is something we're actively
> working on, and we're just not in a state to release anything yet.
> 
> On Thu, Dec 10, 2009 at 9:52 AM, Michael Steuer  wrote:
>> Raffi - can someone at Twitter PLEASE comment on the delegation question? If
>> your app uses the web oauth flow, as strongly recommended by Twitter and
>> reiterated in your statement below, how do you see consumption of 3rd party
>> APIs happening when you don't have the user's un/pw? I don't understand why
>> you're so unwilling to address that question?
>> 
>> 
>> On 12/10/09 7:42 AM, "Raffi Krikorian"  wrote:
>> 
>>> > don't be evil.  in a web scenario, send them to twitter.com
>>> <http://twitter.com>  for the
>>> > oauth workflow.  in the case that you can't do that, do not store the
>>> > username and password - simply pass them through and store the tokens
>>> > instead.
>>> >
>>>> >> @ michael
>>>> >> " The web case is different - a web site doesn't have the user's
>>>> credentials
>>>> >> unless they explicitly provide them."
>>>> >> With the new  oAuth implementation even web apps will be allowed to
>>>> collect
>>>> >> user's credentials. There is no way to enforce webapps to delegate
>>>> >> authentication
>>>> >>
>>>> >>
>>>> >> On Thu, Dec 10, 2009 at 8:42 PM, Michael Ekstrand 
>>>> >> wrote:
>>>>> >>>
>>>>> >>> John Meyer wrote:
>>>>>> >>>> okay, forgive me if I'm wrong, but wasn't the whole point of oAuth
>>>>>> >>>> that the application didn't need to know the username/password?
>>>>>>  That
>>>>>> >>>> the user would grant access to the application and then the
>>>>>> >>>> application would store that rather than the actual
>>>>>> >>>> username/password.  Or am I missing the point of going to an oAuth
>>>>>> >>>> system?
>>>>> >>> Yes, that's the point of OAuth.  However, the dynamics of a web-based
>>>>> >>> application vs. a desktop application complicate things.  If the user
is
>>>>> >>> trusting an application to run natively on their desktop, that
>>>>> >>> application already has access to their username and password (it can
>>>>> >>> read them from config files, do a keyboard grab when it spawns the
>>>>> >>> browser, go snooping around in Firefox's memory space, any number of
>>>>> >>> things).  Thus, in the desktop application case, allowing the user to
>>>>> >>> input their username and password does not decrease security except
>>>>> >>> perhaps by not always enforcing "don't give away your password".  The
>>>>> >>> web case is different - a web site doesn't have the user's credentials
>>>>> >>> unless they explicitly provide them.
>>>>> >>>
>>>>> >>> I'm ignoring for the present sandboxed or sandboxable environments
>>>>> such
>>>>> >>> as Java and AIR.  The runtime may prevent the local application from
>>>>> >>> having access to the username/password as used by other applications.
>>>>> >>>
>>>>> >>> - Michael
>>>>> >>>
>>>>> >>> --
>>>>> >>> mouse, n: A device for pointing at the xterm in which you want to
>>>>> type.
>>>>> >>> Confused by the strange files?  I cryptographically sign my messages.
>>>>> >>> For more information see <http://www.elehack.net/resources/gpg>.
>>>>> >>>
>>>>> >>>
>>>> >>
>>>> >>
>>> >
>>> >
>> 
>> 
> 
> 

Re: [twitter-dev] Re: A New API For Browserless Apps?

[Michael Steuer]

Raffi - can someone at Twitter PLEASE comment on the delegation question? If
your app uses the web oauth flow, as strongly recommended by Twitter and
reiterated in your statement below, how do you see consumption of 3rd party
APIs happening when you don't have the user's un/pw? I don't understand why
you're so unwilling to address that question?


On 12/10/09 7:42 AM, "Raffi Krikorian"  wrote:

> don't be evil.  in a web scenario, send them to twitter.com for the
> oauth workflow.  in the case that you can't do that, do not store the
> username and password - simply pass them through and store the tokens
> instead.
> 
>> @ michael
>> " The web case is different - a web site doesn't have the user's credentials
>> unless they explicitly provide them."
>> With the new  oAuth implementation even web apps will be allowed to collect
>> user's credentials. There is no way to enforce webapps to delegate
>> authentication
>> 
>> 
>> On Thu, Dec 10, 2009 at 8:42 PM, Michael Ekstrand 
>> wrote:
>>> 
>>> John Meyer wrote:
 okay, forgive me if I'm wrong, but wasn't the whole point of oAuth
 that the application didn't need to know the username/password?  That
 the user would grant access to the application and then the
 application would store that rather than the actual
 username/password.  Or am I missing the point of going to an oAuth
 system?
>>> Yes, that's the point of OAuth.  However, the dynamics of a web-based
>>> application vs. a desktop application complicate things.  If the user is
>>> trusting an application to run natively on their desktop, that
>>> application already has access to their username and password (it can
>>> read them from config files, do a keyboard grab when it spawns the
>>> browser, go snooping around in Firefox's memory space, any number of
>>> things).  Thus, in the desktop application case, allowing the user to
>>> input their username and password does not decrease security except
>>> perhaps by not always enforcing "don't give away your password".  The
>>> web case is different - a web site doesn't have the user's credentials
>>> unless they explicitly provide them.
>>> 
>>> I'm ignoring for the present sandboxed or sandboxable environments such
>>> as Java and AIR.  The runtime may prevent the local application from
>>> having access to the username/password as used by other applications.
>>> 
>>> - Michael
>>> 
>>> --
>>> mouse, n: A device for pointing at the xterm in which you want to type.
>>> Confused by the strange files?  I cryptographically sign my messages.
>>> For more information see .
>>> 
>>> 
>> 
>> 
> 
> 

Re: [twitter-dev] Announcements

[Michael Steuer]

I have the same question and have posed it repeatedly via various
channels... For some reason Twitter refuses to comment on it...


On 12/9/09 1:01 PM, "Damon Clinkscales"  wrote:

> On Wed, Dec 9, 2009 at 12:23 PM, Isaiah Carew  wrote:
>> From the announcement I read here:
>> 
>> http://www.techcrunch.com/2009/12/09/twitter-le-web-2009/
>> 
>> 
>> 3) ... starting Basic Auth decprecation in June 2010.
> 
> My question is...how do you drop Basic Auth support without OAuth
> delegation.  Otherwise, how do third-party sites like TwitPic ever
> work with clients w/o the password.
> 
> Thanks,
> -damon
> --
> http://twitter.com/damon

Re: [twitter-dev] Basic Auth deprecation coming

[Michael Steuer]

They can force oauth authentication for authenticated API calls. If  
the API stops looking at the HTTP_AUTH_USER to determine who the user  
is, basic auth has been deprecated...




On Dec 9, 2009, at 6:24 AM, "Dean Collins"  wrote:



How are they going to stop basic auth?

If a website already have the username/passwords doesn't that mean  
they

can log in on a users behalf until they change the password via the
twitter.com website?





Cheers,

Dean




-Original Message-
From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of  
Patrick

Kennedy
Sent: Wednesday, December 09, 2009 9:12 AM
To: twitter-development-talk@googlegroups.com
Subject: [twitter-dev] Basic Auth deprecation coming

With Basic Auth deprecation coming in June 2010, will developers have
a "sand box" way to use Basic Auth?  I mean, it's handy to develop and
understand code with Basic Auth, and then cut it over to oAuth. Any
ideas?

Re: [twitter-dev] Seeking some assistance with my twitter account

[Michael Steuer]

It sounds like the followers/following ratio constraint...



On Dec 8, 2009, at 9:49 PM, Mark McBride  wrote:


What limit does it tell you you've hit?  The API request/hr limit?

On Tue, Dec 8, 2009 at 9:46 PM, steve8004  
 wrote:

Hello:

I use to third party twitter apps

1. Seemic for Windows
2. Tweetdeck

Both are running throughout the day while I work on other
applications. However, when trying to follow someone new and add them
to my follower list, it tells me I have hit my limit.

Is there an automated way to send a message to folks not following  
you

and give them a chance to do so prior to un-following them?

Many thanks,
Steve





--
  ---Mark

http://twitter.com/mccv

[twitter-dev] Re: /favorites/create not versioned?

[Michael Steuer]

Never mind, the error was on my side... It's working now (and in case
you're wondering, the API is versioned and available at /1/favorites/
create

On Dec 8, 2:29 pm, Michael Steuer  wrote:
> When I POST tohttp://api.twitter.com/1/favorites/create/id.jsonI get a 404
> not found HTML page returned... Is the favorites/create API not versioned?
> The APIWiki still says:http://twitter.com/favorites/create/id.format, 
> nothttp://api.twitter.com/1/favorites/create/id.format
> Which is it???
>
> Thanks

[twitter-dev] /favorites/create not versioned?

[Michael Steuer]

When I POST to http://api.twitter.com/1/favorites/create/id.json I get a 404
not found HTML page returned... Is the favorites/create API not versioned?
The APIWiki still says: http://twitter.com/favorites/create/id.format, not
http://api.twitter.com/1/favorites/create/id.format
Which is it???

Thanks

Re: [twitter-dev] Twitter REST API Method: favorites

[Michael Steuer]

On that note, are there any plans to bring the favorites API in line with
other statuses APIs, ie. deprecate the page parameter, allow 'since_id',
'max_id' and 'count', etc.?


On 12/8/09 11:28 AM, "Raffi Krikorian"  wrote:

> that seems to be a deficiency in the format we chose to notate whether
> the endpoint requires authentication.
> 
> if you are calling
> 
> api.twitter.com/1/favorites/raffi.json
> 
> for example, then you don't need to authenticate because my favorites
> are public.  however, if you were to call
> 
> api.twitter.com/1/favorites.json
> 
> then authentication is required so we know "who you are".  in
> addition, authentication may also be required depending on whether the
> user you are requesting from is protected.
> 
> On Tue, Dec 8, 2009 at 11:23 AM, Daniel Silva
>  wrote:
>> authentication is required for this method? they say yes, but i already
>> tried without authentication with sucess.
>> 
>> --
>> best regards,
>> Daniel
>> 
> 
> 

[twitter-dev] Twitter Photo service for oauth clients

[Michael Steuer]

Hi all,

Are any of you aware of a photo service that allows picture uploads  
from my oauth based Twitter client? The Api for all the usual suspects  
(twitpic, yfrog, tweetphoto, etc) requires  passing of the user's  
Twitter username and password, but being an oauth client, I don't have  
the user's password available to me. How are other oauth based clients  
dealing with this? It seems my only option is building my own, but I'd  
rather hook into an existing service.


Looking forward to your feedback!

Thanks,

Michael

[twitter-dev] /statuses/retweet

[Michael Steuer]

Is statuses/retweet down? I¹m getting 404s 100% of the time, for perfectly
valid tweet ids.

Anyone else?

Re: [twitter-dev] Re: Retweeted statuses broken

[Michael Steuer]

Are retweets fully working again?

I'm trying to use statuses/retweet and POST a perfectly valid tweet ID, but
it always returns 404 for me.

Is the statuses/retweet API broken???




On 12/3/09 12:18 AM, "Rich"  wrote:

> Can I ask why is the status and @twitterapi not updated informing us
> rather than waiting for us to get a stream of complaints?
> 
> On Dec 3, 8:07 am, Abraham Williams <4bra...@gmail.com> wrote:
>> The retweet features were turned off a few hours ago.
>> 
>> Abraham
>> 
>> On Thu, Dec 3, 2009 at 01:49, Rich  wrote:
>>> Hi
>> 
>>> is it just me or since the problems last night the retweeted to me, by
>>> me and of me api calls are returning 404s?
>> 
>> --
>> Abraham Williams | Community Evangelist |http://web608.org
>> Hacker |http://abrah.am|http://twitter.com/abraham
>> Project | Awesome Lists |http://twitterli.st
>> This email is: [ ] blogable [x] ask first [ ] private.
>> Sent from Madison, WI, United States

Re: [twitter-dev] Getting retweets in user timelines

[Michael Steuer]

> Also, it would be awesome if we could get through the API that a
> status has been retweeted when making requests to a user's timeline.
> This would avoid the overhead of going through each tweet and making a
> statuses/retweets call.

+1

Re: [twitter-dev] Re: Quick question re ReTweets

[Michael Steuer]

So the API doesn't give me any indication which tweets in my home timeline I
have already retweeted, so I could retweet a tweet I retweeted previously?


On 12/3/09 12:59 AM, "Rich"  wrote:

> From the way I've seen it work, if the orginal tweet is already in
> your home_timeline you will not see any retweets of it, including
> yours.  However if you retweet a message not in your home_timeline
> then it will appear.
> 
> I'm not sure if that IS how it works, just what I've observed.
> 
> On Dec 2, 11:30 pm, Michael Steuer  wrote:
>> So when a user is looking at his own home_timeline, and decides to retweet a
>> status from someone else ­ the next time that home_timeline is loaded, will
>> it show both statuses (the original tweet and the retweet by the user), or
>> one or the other? My understanding is that the new retweet functionality is
>> supposed to ensure that a status only shows up once, I¹m just not sure how
>> this is reflected in what the home_timeline API returns...
>> 
>> Thanks for letting me know!
>> 
>> Michael.

[twitter-dev] Quick question re ReTweets

[Michael Steuer]

So when a user is looking at his own home_timeline, and decides to retweet a
status from someone else ­ the next time that home_timeline is loaded, will
it show both statuses (the original tweet and the retweet by the user), or
one or the other? My understanding is that the new retweet functionality is
supposed to ensure that a status only shows up once, I¹m just not sure how
this is reflected in what the home_timeline API returns...

Thanks for letting me know!

Michael.

Re: [twitter-dev] Are lists having problems?

[Michael Steuer]

Thanks...

There error/problem however was on my end... Fixed it... Sorry to have
bothered you...

Michael.

On 12/2/09 2:33 PM, "shiplu"  wrote:

> The error is 
> 
> "Something is technically wrong. Thanks for noticing we're going to fix it up
> and have things back to normal soon"
> 

[twitter-dev] Are lists having problems?

[Michael Steuer]

I¹m getting HTML errors back  (see below) when trying to get a lists
statuses... Are there issues that haven¹t been announced?

Thanks,

Michael

Here¹s the HTML that Twitter API returns to me:

\\
n\\n  \\n\\n\\n
Twitter \\/ Error<\\/title>\\n\\n\\n

Re: [twitter-dev] Re: Authorizing users for my app's API

[Michael Steuer]

And again this discussion dies off... I really don't understand why Twitter
and most developers are so quiet about this. What's the plan for supporting
3rd party APIs via Oauth? Right now for those of us already exclusively
Oauth based on Twitter's recommendation, or for the rest of you in the near
future when basic auth is deprecated?

Sticking our heads in the sand isn't going to lead to an answer...


On 11/30/09 5:43 PM, "Dewald Pretorius"  wrote:

> I know some people will kick my shins over this, but I would not
> recommend using Twitter OAuth (or Facebook Connect for that matter) as
> the primary mechanism for logins to your own site.
> 
> Why would one expose your site to the stability, availability,
> temperament, and good graces of another service over which you have no
> control? If they are down, or for some reason they blocked you, your
> app is dead in the water (nobody can login), even if there is
> functionality that does not depend on API calls to the external
> service. You may have a lot of things cached so that your site can
> function even when Twitter OAuth is on the blink. That helps you
> nothing if you depend on Twitter OAuth for user logins to your site.
> 
> On Nov 30, 9:03 pm, Michael Steuer  wrote:
>> To all who are wondering about this - I raised this issue and some
>> suggestions a while back, got 1 response from Twitter, but when I asked the
>> dev community who else struggles with this, it was awfully silent (perhaps
>> people hoping Twitter would never deprecate basic auth)... See this thread:
>> 
>> http://groups.google.com/group/twitter-development-talk/browse_frm/th...
>> 563255efcb
>> 
>> On 11/30/09 4:48 PM, "Brian Morearty"  wrote:
>> 
>>> Thanks for asking. I was just wondering the same thing. :-)
>> 
>>> On Nov 30, 3:19 pm, "LeeS - @semel"  wrote:
>>>> Here's the situation:
>> 
>>>> My app lets users OAuth via Twitter as their login.  Simple and
>>>> standard.
>> 
>>>> Now, I've created an API for my app.  I want other apps, say Twitter
>>>> clients, to be able to use my app, as if they are one of my app's
>>>> users.  What's the best way to let the user authorize that app to use
>>>> my app?  Do I have to implement OAuth myself, and then have the user
>>>> OAuth twice, once into my app and once into Twitter via my app to let
>>>> my app access Twitter?  That's a lot of screens for the user to go
>>>> through.
>> 
>>>> I'm curious how you'd handle this, and if there's a simpler solution.
>> 
>>>> Lee

Re: [twitter-dev] Re: Authorizing users for my app's API

[Michael Steuer]

While that may be true in a more generic sense, I think that for most of us
on this mailinglist, the core functionality of our apps depends on Twitter
being up and available... So for me there's really little point in
authenticating users when Twitter is down and my app doesn't provide its
core functionality...

But anyways, this is all slightly OT.

The reality is, oAuth is Twitter's preferred authentication protocol, it
will soon be the only one, and it lacks delegation, ie. anyone who's
providing APIs to 3rd parties (twitpic, twitvid, yfrog, anyone!) are going
to be SOL once basic auth is deprecated unless Twitter provides some form or
oAuth delegation... And for those of us not providing basic autha and
already using oauth exclusively, we're already SOL, as we can't provide, nor
consume APIs that require basic authentication.

Time to re-start this discussion please...


On 11/30/09 5:43 PM, "Dewald Pretorius"  wrote:

> I know some people will kick my shins over this, but I would not
> recommend using Twitter OAuth (or Facebook Connect for that matter) as
> the primary mechanism for logins to your own site.
> 
> Why would one expose your site to the stability, availability,
> temperament, and good graces of another service over which you have no
> control? If they are down, or for some reason they blocked you, your
> app is dead in the water (nobody can login), even if there is
> functionality that does not depend on API calls to the external
> service. You may have a lot of things cached so that your site can
> function even when Twitter OAuth is on the blink. That helps you
> nothing if you depend on Twitter OAuth for user logins to your site.
> 
> On Nov 30, 9:03 pm, Michael Steuer  wrote:
>> To all who are wondering about this - I raised this issue and some
>> suggestions a while back, got 1 response from Twitter, but when I asked the
>> dev community who else struggles with this, it was awfully silent (perhaps
>> people hoping Twitter would never deprecate basic auth)... See this thread:
>> 
>> http://groups.google.com/group/twitter-development-talk/browse_frm/th...
>> 563255efcb
>> 
>> On 11/30/09 4:48 PM, "Brian Morearty"  wrote:
>> 
>>> Thanks for asking. I was just wondering the same thing. :-)
>> 
>>> On Nov 30, 3:19 pm, "LeeS - @semel"  wrote:
>>>> Here's the situation:
>> 
>>>> My app lets users OAuth via Twitter as their login.  Simple and
>>>> standard.
>> 
>>>> Now, I've created an API for my app.  I want other apps, say Twitter
>>>> clients, to be able to use my app, as if they are one of my app's
>>>> users.  What's the best way to let the user authorize that app to use
>>>> my app?  Do I have to implement OAuth myself, and then have the user
>>>> OAuth twice, once into my app and once into Twitter via my app to let
>>>> my app access Twitter?  That's a lot of screens for the user to go
>>>> through.
>> 
>>>> I'm curious how you'd handle this, and if there's a simpler solution.
>> 
>>>> Lee

Re: [twitter-dev] Re: Authorizing users for my app's API

[Michael Steuer]

To all who are wondering about this - I raised this issue and some
suggestions a while back, got 1 response from Twitter, but when I asked the
dev community who else struggles with this, it was awfully silent (perhaps
people hoping Twitter would never deprecate basic auth)... See this thread:

http://groups.google.com/group/twitter-development-talk/browse_frm/thread/ac
563255efcb




On 11/30/09 4:48 PM, "Brian Morearty"  wrote:

> Thanks for asking. I was just wondering the same thing. :-)
> 
> 
> On Nov 30, 3:19 pm, "LeeS - @semel"  wrote:
>> Here's the situation:
>> 
>> My app lets users OAuth via Twitter as their login.  Simple and
>> standard.
>> 
>> Now, I've created an API for my app.  I want other apps, say Twitter
>> clients, to be able to use my app, as if they are one of my app's
>> users.  What's the best way to let the user authorize that app to use
>> my app?  Do I have to implement OAuth myself, and then have the user
>> OAuth twice, once into my app and once into Twitter via my app to let
>> my app access Twitter?  That's a lot of screens for the user to go
>> through.
>> 
>> I'm curious how you'd handle this, and if there's a simpler solution.
>> 
>> Lee

Re: [twitter-dev] Twitter OAuth works fine in my app then I get error when trying to login to Twitter.com site

[Michael Steuer]

Yes I experience the same. Not sure what causes it...



On Nov 28, 2009, at 11:46 AM, JimJty  wrote:


OAuth works fine in my application but then when I open a new tab to
login to twitter, I login and I get this message:

"Woah there!
This page requires some information that was not provided. Please
return to the site that sent you to this page and try again … it was
probably an honest mistake."

When I hit back on the browser, the error message goes away and I am
at my home page.

This looks to be a bug with Twitter's OAuth. Here are the steps to
reproduce:

1) Make sure you are logged out of twitter.com
2) Use a third party app to login to twitter: (you can use this demo:
http://twitteroauth.appspot.com/)
3) Open a second tab, go to twitter.com and login. You should get the
error message above?

I am not too familiar with OAuth but I have used a few different code
libraries for python and they all seem to have the same issue.
Any one experience similar?

Re: [twitter-dev] Re: Twitter PHP + CentOS

[Michael Steuer]

Create a page that prints out phpinfo(). See if the curl module is  
active in your php




On Nov 25, 2009, at 5:19 PM, aztroboy  wrote:


Thank you for your reply,

[r...@twirelezz ~]# php -version
PHP 5.1.6 (cli) (built: Apr  7 2009 08:00:04)
Copyright (c) 1997-2006 The PHP Group
Zend Engine v2.1.0, Copyright (c) 1998-2006 Zend Technologies


Not bad, now I updated PHP to its lastest version:

[r...@twirelezz ~]# php -v
PHP 5.3.1 (cli) (built: Nov 20 2009 17:51:14)
Copyright (c) 1997-2009 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2009 Zend Technologies


However, I'm getting the same response: twitter won't give me the
auth_token :( (or at least, it's giving me a null response)

On 25 nov, 18:36, jmathai  wrote:

Check the versions of software you're using. CentOS likes to make you
jump through hoops in order to get newer software.

Namely, check your PHP version.

On Nov 25, 9:08 am, aztroboy  wrote:

Hello there! I'm using a PHP Twitter OAuth library  
(twitter.abrah.am),
and it works perfect on Windows: the php script looks asks twitter  
for

an auth token. However, as soon as I put the same script on CentOS
(with its default httpd service), it won't give any auth tokens at
all.



The script uses cURL to get the token from twitter. I've used cURL
(curlwww.google.com) and it works fine in console.



What could be going wrong here? Is there something I should add of
change first in order to receive the tokens? By the way, I got the
CentOS default FW set allowing traffic on port 80 and SSH only.



I would like to ask for a hint about what should I do, I'm kinda
newbie on CentOS.



thank you in advance

Re: [twitter-dev] Re: Twitter app marked "inactive"?

[Michael Steuer]

Thanks for providing all 4 links Brian...

So why was Listerine blocked? I tried out the app once and didn't
necessarily see any behavior that was objectionable based on the link you
sent?


On 11/24/09 10:11 AM, "Brian Sutorius"  wrote:

> OAuth tokens are suspended when the applications break our API Rules,
> API Terms of Service, Twitter Rules, or Twitter Terms of Service. I
> understand that four separate documents can be a lot to keep up with,
> but I've put them at the bottom of this post for your convenience. To
> ask any questions about these rules as they apply to application
> behavior, simply email a...@twitter.com .
> 
> Thanks!
> Brian
> 
> http://twitter.com/apirules
> http://apiwiki.twitter.com/Terms-of-Service
> http://help.twitter.com/forums/26257/entries/18311
> http://twitter.com/terms
> 
> On Nov 23, 5:34 pm, Andrew Badera  wrote:
>> Could you help educate the rest of the community as to what might
>> cause that to happen, so we can avoid it?
>> 
>> Thanks-
>> ƒ Andy Badera
>> ƒ +1 518-641-1280 Google Voice
>> ƒ This email is: [ ] bloggable [x] ask first [ ] private
>> ƒ Google me:http://www.google.com/search?q=andrew%20badera
>> 
>> 
>> 
>> On Mon, Nov 23, 2009 at 12:46 PM, Brian Sutorius 
>> wrote:
>>> Hey Luis,
>>> Your OAuth token has been suspended. For more information about this,
>>> please write to a...@twitter.com and I'll be happy to talk with you.
>> 
>>> Brian
>> 
>>> On Nov 21, 6:28 pm, "luis, syndeomedia"  wrote:
 Hey all,
>> 
 My Twitter app "Listerine" has been marked "inactive" in my
 oauth_clients page and I don't know why. (http://twitter.com/
 oauth_clients/details/45072) Could someone shed some light on this
 please?
>> 
 :luis

Re: [twitter-dev] Re: White Listing and Rate Limiting

[Michael Steuer]

Are you sure your checking your rate with an authenticated call? If  
you don't, you'd get the rate for your IP




On Nov 23, 2009, at 7:02 PM, mtruth   
wrote:



I whitelisted my account.  My IP would change depending on where I am
doing my work.

On Nov 23, 10:43 pm, shiplu  wrote:
On Mon, Nov 23, 2009 at 9:41  
AM,mtruth wrote:

Hi,



I'm creating an application in VB.Net, I've been white listed.  Yet
when I get my rate in VB.Net it shows that am I am only getting 150
request.  When I check my available requests, I am using my username
and password.


Yet, when I run Tweetdeck, I am shown that I get my full white  
listed

rate limit.


What did you whitelist? your account or IP?

--
A K M Mokaddim
My talks,http://talk.cmyweb.net
Follow me,http://twitter.com/shiplu
SUST Programmers,http://groups.google.com/group/p2psust
বাংলিশ লেখার চাইতে বাংলা  
লেখা অনেক ভাল

Re: [twitter-dev] Is it possible to recreate Twitter's followers screen?

[Michael Steuer]

Or you could simply fetch followers/ids to get a list of all of a  
user's followers




On Nov 23, 2009, at 9:08 AM, Chris Thomson  wrote:

There seems to be a `following` boolean attribute returned for each  
user in /statuses/followers.xml (and .json)... is that what you're  
looking for?


--
Chris Thomson

On 2009-11-23, at 11:16 AM, Ryan Bell wrote:

I would like to completely recreate Twitter's followers screen.   
After

some research, we aren't sure its possible without being inefficient
with the API.

We're unable to determine if a user is a following the logged in user
in a bulk fashion.This information is needed in order to determine
which options to include next to each follower. ex) should you show
'follow' or 'unfollow' button?

Twitter returns your followers information, but does not include
information as to whether you are also following that user.  It seems
that the only way to get this additional information is on a 1-by-1
basis by checking to see if each of your followers is being followed
by you.

QUESTION:
Is there a better way to determine in bulk if users are being  
followed

by you?  It seems that this functionality must exist in order for an
application to mimic Twitter's Followers page.

Thanks in advance for any assistance,

Ryan

Re: [twitter-dev] Rate Limit & Whitelisting Change

[Michael Steuer]

Youre seeing rate limit errors for unauthenticated calls from that ip  
address, or when you authenticated calls for a user that's not  
whitelisted?




On Nov 23, 2009, at 10:30 AM, Stas  wrote:


We have received whitelisting approval from Twitter, but seems it is
applicable to the @name and the IP.
Given that we still get "rate limit" errors, should we just whitelist
the IP?

If so, what is the process of changing the whitelisting options?

Thank you,
-Stas

Re: [twitter-dev] Re: Is it possible to recreate Twitter's followers screen?

[Michael Steuer]

And what's prohibiting you from doing this?


On 11/23/09 9:38 AM, "Duane Roelands"  wrote:

> I would get a list of the current user's followers and maintain it in
> a cache.  Then, when displaying an arbitrary list of users, check each
> user to see if that user exists in the cache.  They they do, show the
> "Unfollow" button.  If they don't, show the "Follow" button.
> 
> On Nov 23, 12:08 pm, Chris Thomson  wrote:
>> There seems to be a `following` boolean attribute returned for each user in
>> /statuses/followers.xml (and .json)... is that what you're looking for?
>> 
>> --
>> Chris Thomson
>> 
>> On 2009-11-23, at 11:16 AM, Ryan Bell wrote:
>> 
>>> I would like to completely recreate Twitter's followers screen.  After
>>> some research, we aren't sure its possible without being inefficient
>>> with the API.
>> 
>>> We're unable to determine if a user is a following the logged in user
>>> in a bulk fashion.This information is needed in order to determine
>>> which options to include next to each follower. ex) should you show
>>> 'follow' or 'unfollow' button?
>> 
>>> Twitter returns your followers information, but does not include
>>> information as to whether you are also following that user.  It seems
>>> that the only way to get this additional information is on a 1-by-1
>>> basis by checking to see if each of your followers is being followed
>>> by you.
>> 
>>> QUESTION:
>>> Is there a better way to determine in bulk if users are being followed
>>> by you?  It seems that this functionality must exist in order for an
>>> application to mimic Twitter's Followers page.
>> 
>>> Thanks in advance for any assistance,
>> 
>>> Ryan

[twitter-dev] Question and/or Feature Request: in-reply-to-direct-message-id for DMs

[Michael Steuer]

Hi Twitter, Twitter Developers,

Let me start with the question: is there a good reason why the  
payload for direct_messages doesn’t have a “in-reply-to-direct- 
message-id”, just like the “in-reply-to-status-id” for status  
updates? I know that for my use cases, and I’m sure for some of your 
s, it’d be helpful to know if a DM was a reply to an earlier one, or 
 a new DM to the recipient.


So here’s the feature request: can we pretty please have a “in- 
reply-to-direct-message-id” in the DM API payload? And if you consid 
er this a reasonable request, how long do you think that would take ;)


THANK YOU!

Michael.

[twitter-dev] Re: Moderators, can you trim this address from list?

[Michael Steuer]

Yes it has


On 11/13/09 10:54 AM, "Cameron Kaiser"  wrote:

> 
>> Yes I'm getting the same thing. Kind of annoying.
> 
> But has it stopped?

[twitter-dev] Re: Moderators, can you trim this address from list?

[Michael Steuer]

I'm getting them too, and I haven't sent anything... I think they're going
to everyone on the list


On 11/13/09 9:23 AM, "Cameron Kaiser"  wrote:

> 
>> I've been hit with NDRs on this address numerous times recently. If
>> you could unsubscribe that address, it would be great.
>> 
>> User: if you're actually active on list, please use a reliable email
>> server, and not that box in your mom's basement.
> 
> I can pull it, but why are you getting a bounce message? Are you sending a
> copy to them as well as to the list?

[twitter-dev] Re: Dynamic redirect URL after OAuth login

[Michael Steuer]

Please read the documentation and look for the oauth_callback parameter...

Don't forget to pass the oauth_verifier...


On 11/11/09 11:16 PM, "Amitab"  wrote:

> 
> Hi,
> 
> Is there a way to support dynamic URLs being loaded after OAuth login?
> 
> My website has multiple URLs from where a user can sign-in. I want the
> user to come back to same Url where they were before clicking on the
> Sign_in button. Can I ask Twitter OAuth to redirect to an Url of my
> choice by supplying it as a parameter in my OAuth login request.
> 
> Thanks,
> Amitabh
> 
> Follow Twaller @mytwaller

[twitter-dev] Re: Oauth and (lack) delegation

[Michael Steuer]

Hey Marcel,

Good to hear Twitter is thinking about this issue. It sounds like timing is
kind of open ended at this point? I would obviously love to be part of the
conversation and help test things out etc. I did find a couple interesting
discussions/ideas while researching this issue, that you may or may not yet
be aware of:

http://groups.google.com/group/oauth/browse_thread/thread/bdf8b99e84a8aaef/7
7409186172e23ba?#77409186172e23ba

http://hueniverse.com/2009/03/taking-oauth-beyond-the-3rd-leg/

>From my perspective, and I'm not a security expert, oauth expert or any
other kind of relevant expert, I could imagine a workflow where an app can
request a one-time-use-only token from Twitter that it can pass on to
another 3rd party app for one time use. So, for example, you have a Twitter
client, let's call it Tweetie, and a 3rd party service with API, let's call
it TwitPic (I'm not related to either)...

- Tweetie requests a one-time token from Twitter. The one-time token is
restricted to the user it is requested for, and the application it is
requested for.
- Tweetie performs an API request to TwitPic, passing on the one-time token.
- In turn, TwitPic can perform an API request to Twitter on behalf of the
Tweetie user (e.g. Post a picture), using the one-time token as an
additional oauth parameter.

One-time tokens are expired upon use or within X minutes after been granted.
A new one-time-token for a App1/App2/User combination cannot be granted
until an earlier granted token has either expired or been used. And since
such one-time tokens are specific to Requesting App, Receiving App and the
User, abuse is not likely as any of the 3 parties could restrict one of the
other 2 parties from requesting or receiving a token... Also, since both the
Requesting App and Receiving App are tied to the token, Twitter can display
a combined client attribute with the resulting tweets (e.g. "1 minute ago
from Tweetie via TwitPic")

Anyway - I'm sure there are plenty of drawbacks, other concerns or things
I'm overlooking - but just wanted to get the conversation started...

What other, perhaps equally high level options has Twitter or anyone else
come up with?

Thanks,

Michael.


On 11/5/09 4:55 PM, "Marcel Molina"  wrote:

> 
> We've got a project lined up to come up with an answer for OAuth app
> delegation problem. We haven't done a deep dive into what the approach
> might be yet so we don't have any ideas yet. Would be glad to have the
> conversation with those who are interested and have ideas.
> 
> On Thu, Nov 5, 2009 at 4:20 PM, Michael Steuer  wrote:
>> Does Twitter (or anyone else) have thoughts around the lack of delegation in
>> Oauth and the announced deprecation of basic authentication? Currently, to
>> enable an API that allows web services to interact with Twitter on its
>> behalf (e.g. TwitPic, yFrog, etc.) one has to rely on basic authentication
>> (the twitter client passing the user¹s username & password to the web
>> services API), as delegation is not possible via Oauth... If a user
>> authenticates with my application via Oauth, there¹s no way I can have a 3rd
>> party API do anything on behalf of that user...
>> 
>> Similarly, if I want to develop an API to my Twitter web service, I would
>> have to develop that with basic authentication, but what¹s the point:
>> 
>> knowing that basic auth is going to be deprecated in the (near) future
>> so many apps are now based on oauth and wouldn¹t be able to use my API
>> because they can¹t authenticate
>> 
>> I¹m sure other devs have run into this. Does Twitter have any thoughts
>> around this? How do you expect to maintain a 3rd party app/API eco system
>> after basic auth deprecation?
>> 
>> Looking forward to everyone¹s feedback..
> 
> 

[twitter-dev] Oauth and (lack) delegation

[Michael Steuer]

Does Twitter (or anyone else) have thoughts around the lack of delegation in
Oauth and the announced deprecation of basic authentication? Currently, to
enable an API that allows web services to interact with Twitter on its
behalf (e.g. TwitPic, yFrog, etc.) one has to rely on basic authentication
(the twitter client passing the user¹s username & password to the web
services API), as delegation is not possible via Oauth... If a user
authenticates with my application via Oauth, there¹s no way I can have a 3rd
party API do anything on behalf of that user...

Similarly, if I want to develop an API to my Twitter web service, I would
have to develop that with basic authentication, but what¹s the point:
* knowing that basic auth is going to be deprecated in the (near) future
* so many apps are now based on oauth and wouldn¹t be able to use my API
because they can¹t authenticate

I¹m sure other devs have run into this. Does Twitter have any thoughts
around this? How do you expect to maintain a 3rd party app/API eco system
after basic auth deprecation?

Looking forward to everyone¹s feedback..

[twitter-dev] Re: "Incorrect signature" returned for Lists API

[Michael Steuer]

Hi Jaisen,

Doesn't Nelu's use of strtolower take care of your camel case concern?

I just posted a comment on your blog - it'd be great if you could publish a
couple lines around usage of your lib with the new lists URL structure etc.

Thanks so much, 

Michael.


On 11/2/09 9:51 PM, "jmathai"  wrote:

> 
> Nelu,
> 
> While that works, I suggest using the ID over the username since a
> username with camel case will break the path regex.  This should work
> with the newest version of the library from Github.
> 
> I'm considering including an option to pass in the url as a string in
> the 2.0 version of the library.
> 
> Jaisen
> 
> On Nov 2, 7:53 am, Nelu Lazar  wrote:
>> Figured the answer for the issue above, for @jmathai's EPITwitter
>> library, here is the call code that works:
>> 
>> $twitterOAuthObj->{'get_'.(string)strtolower
>> ($username).'ListsMemberships'}(array(...));
>> 
>> - @NeluLazar
>> 
>> On Nov 2, 10:37 am, Nelu Lazar  wrote:
>> 
>>> I am experiencing "Incorrect signature" responses while requesting any
>>> Lists API XMLs.
>> 
>>> 
>>>   /tweetvisor/lists/subscriptions.xml
>>>   Incorrect signature
>>> 
>> 
>>> I tried various methods, with no success: POST, GET, HTTPS (default),
>>> HTTP. It only happens to Lists API calls, all other released API calls
>>> are working fine.
>> 
>>> If anyone know what's going on, please advise. Thanks,
>> 
>>> - @NeluLazar

[twitter-dev] Re: Lists API

[Michael Steuer]

Well, I¹m in no beta, but it all seems to be accessible and working..
According to Marcel Molina, the API went public/open last Thursday. I guess
it wasn¹t announced (not on the group at least).


On 11/2/09 9:57 AM, "Sean Scott"  wrote:

> List API is in Beta.  If you're in the beta you can play with it.  If you're
> not in the Beta you can't play with it just yet
> 
> On Mon, Nov 2, 2009 at 9:48 AM, Michael Steuer  wrote:
>> With all the discussions on this mailing list about the Lists API, can
>> someone please confirm, is the API now available to all developers or all of
>> you in some sort of preferred position?
>> 
>> Thanks,
>> 
>> Michael. 
> 
> 

[twitter-dev] Re: Is image shrinking broken?

[Michael Steuer]

I have noticed the same recently. This should probably be logged as a bug?
It's a core twitter bug though, not with the API...


On 11/2/09 9:25 PM, "TCI"  wrote:

> 
> I am noticing an increase in the number of avatar images which do not
> get shrinked in the smaller versions. It is most noticeable in the
> twitter.com homepage as the images load very slowly from top to
> bottom. How are your clients handling this? In my case I am assuming
> the shrinking is working and therefore my page load times are being
> affected.
> 
> Example:
> 
> http://a3.twimg.com/profile_images/506101471/Copy__2__of_Francesca__4__bigger.
> jpg
> http://a3.twimg.com/profile_images/506101471/Copy__2__of_Francesca__4__normal.
> jpg
> 
http://a3.twimg.com/profile_images/506101471/Copy__2__of_Francesca__4__mini.jp>
g
> 
> are all the same...

[twitter-dev] Re: Lists API

[Michael Steuer]

Ah, great... I must have missed that announcement!

Thanks,

Michael.


On 11/2/09 10:05 AM, "Marcel Molina"  wrote:

> 
> It's available to all developers and has been since last Thursday.
> 
> There are still some tweaks to be made but everything that works now
> should continue to be supported along side the changes and additions
> that will be introduced.
> 
> On Mon, Nov 2, 2009 at 9:48 AM, Michael Steuer  wrote:
>> With all the discussions on this mailing list about the Lists API, can
>> someone please confirm, is the API now available to all developers or all of
>> you in some sort of preferred position?
>> 
>> Thanks,
>> 
>> Michael.
> 
> 

[twitter-dev] Lists API

[Michael Steuer]

With all the discussions on this mailing list about the Lists API, can
someone please confirm, is the API now available to all developers or all of
you in some sort of preferred position?

Thanks,

Michael.

[twitter-dev] Re: PHP Libraries for OAuth

[Michael Steuer]

+1

I too started with Abraham's, but as you pointed out, that project is  
more or less stagnant and Abraham is working on other things. Totally  
understandable.


Jmathai's library is technically very sound, extremely well thought  
out and continuously being improved. Moreover, jmathai is very helpful  
and responds to questions/requests etc within hours.


Big fan.

Plus, you get the advantage of asynchronous calls...



On Nov 1, 2009, at 12:37 PM, Scott Wilcox  wrote:



I much prefer using http://wiki.github.com/jmathai/twitter-async

Scott.

On 1 Nov 2009, at 19:57, Michael Mokrysz wrote:



Hi,

I've been messing around with the API for a while now and I've been
wondering whether there's any particular consensus over the best
library to use with PHP? Up to now I've been using Abraham Williams'
TwitterOAuth library, however since on github it seems there's been  
no

updates for many months I thought I'd better check whether that's
because there's no major bugs or because there's better libraries
available?

Best wishes,
Michael Mokrysz

[twitter-dev] Re: Twitter API Returning Nothing

[Michael Steuer]

Hi Jesse,

Not sure if this is it, but looking at your code you're making a POST  
request to Twitter but sending the status parameter as a GET request  
parameter as part of the URL instead of a POST parameter. Send the  
data via POST too, see if that helps.




On Oct 31, 2009, at 11:23 AM, Jesse Bunch  wrote:



Hello, here is my cURL output from the response. Its empty! I am
attaching both the code used and the response. I have been at this for
hours and cannot find out why this is happening. Thanks for your help.

TWITTER API CURL RESPONSE
url :: http://twitter.com/statuses/update.xml?status=test+agasdf
content_type ::
http_code :: 0
header_size :: 0
request_size :: 0
filetime :: -1
ssl_verify_result :: 0
redirect_count :: 0
total_time :: 0
namelookup_time :: 0.060027
connect_time :: 0
pretransfer_time :: 0
size_upload :: 0
size_download :: 0
speed_download :: 0
speed_upload :: 0
download_content_length :: -1
upload_content_length :: -1
starttransfer_time :: 0
redirect_time :: 0

CODE USED TO SEND REQUEST TO TWITTER
http://twitter.com/statuses/update.xml?status=".urlencode
(stripslashes(urldecode($message)));

   $ch = curl_init();
   curl_setopt($ch, CURLOPT_URL, $host);
   curl_setopt($ch, CURLOPT_VERBOSE, 1);
   curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
   curl_setopt($ch, CURLOPT_USERPWD, "$username:$password");
   curl_setopt($ch, CURLOPT_HTTP_VERSION, CURL_HTTP_VERSION_1_1);
   curl_setopt($ch, CURLOPT_POST, 1);

   $result = curl_exec($ch);
   // Look at the returned header
   $resultArray = curl_getinfo($ch);

   curl_close($ch);

   if($resultArray['http_code'] == "200"){
$twitter_status='Your message has been sent! See your profile';
   } else {
$twitter_status="Error posting to Twitter. Retry";
   foreach ($resultArray as $key => $value) {
   $twitter_status .= $key . " :: " . $value . "";
   }
   }
   return $twitter_status;
}
?>

[twitter-dev] Re: [twitter-api-announce] Updates to the List API (list descriptions, cursoring lists of lists, finding by list id rather than slug & more consistent names)

[Michael Steuer]

+1


On 10/28/09 1:11 PM, "Jesse Stay"  wrote:

> Maybe a little more appropriate to post this to a private list (no pun
> intended) for beta users?  I admit I feel a little jealous every time I see
> one of these updates, unless there's some way to get into the beta.
> 
> Thanks,
> 
> Jesse
> 
> On Wed, Oct 28, 2009 at 2:00 PM, Marcel Molina  wrote:
>> 
>> Two additions and two changes to the List API will be deployed in the
>> next few days:
>> 
>> * List descriptions
>> We're adding a description to every list. You'll be able to specify a
>> description when you create or update a list and the description will
>> be included in the payload.
>> 
>> * Cursoring through lists of lists
>> All resources that return a list of lists will include next and
>> previous cursors and will accept a :cursor parameter.
>> 
>> * Finding by list id rather than slug
>> When you change the name of a list, the slug will be updated to
>> reflect that change. That means using the slug in the url for
>> resources to operate on lists requires the onerous task of validating
>> that the slug for the list you are about to do something with hasn't
>> been updated since the last time you stored its slug. What a nightmare
>> :-)
>> 
>> Every list also has an id. This value won't change. We'll be changing
>> the API to replace all instances of a list slug in urls to be list ids
>> instead.
>> 
>> * Consistent names
>> The terminology we've used thus far for people you follow with a list
>> is members. The terminology for people who are following a list is
>> subscribers. We're going to mirror the terminology used for users and
>> change it to followers and following respectively.
>> 
>> So:
>> 
>> /:user/lists/:list_id/memberships becomes /:user/lists/:list_id/followers
>> 
>> /:user/lists/:list_id/subscribers becomes /:user/lists/:list_id/following
>> 
>> As we deploy these changes we'll send out a heads up on the dev list
>> and @twitterapi.
>> 
>> --
>> Marcel Molina
>> Twitter Platform Team
>> http://twitter.com/noradio
>> 
>> 
> 
> 

[twitter-dev] Re: No Cursor Data Returned

[Michael Steuer]

Are you sure that's where the cursor=-1 is supposed to go? Isn't the  
array meant to contain all the options you want to pass? Perhaps your  
library is cleaning up your URL to make sure it has no request  
parameters and only passing the parameters in the array that you're  
passing as a 2nd parameter to your oAuthRequest function.




On Oct 27, 2009, at 12:32 PM, TylerC  wrote:



Further moor I edited the OAuth script for some debugging and output
the exact string returned by the CURL call and there is still no
next_cursor showing up.

On Oct 27, 1:52 pm, TylerC  wrote:
Idk the OAuth files just return all the data from the CURL query  
there

is not any parsing done to it from what I can see. It just gives you
whatever it gets from Twitter which leads me to believe I am missing
some kind of parameter or there is a bug with the API and OAuth.

On Oct 27, 1:46 pm, JDG  wrote:

The cursor stuff is still somewhat new. Just because it's on the  
wiki
doesn't mean it was provided by Twitter (it's not). It may not  
have been
updated to handle cursors. You should do a dump via a network  
monitoring
tool, like wireshark or even just curl, to see what's sent to the  
oAuth
class. I can't imagine the HTTP response being that different,  
unless

they're doing stuff with User-Agents.



On Tue, Oct 27, 2009 at 11:44, TylerC  wrote:



Its the standard OAuth class provided from the Twitter wiki...



When I dump it, even with var dump or print it begins with :







But then right after the  tag the data ends. Its very odd  
and

its driving me nuts.



On Oct 27, 1:40 pm, JDG  wrote:
are you sure they're not returned via the script? did you dump  
the data

you
received using wireshark or some other network monitoring tool?  
it could

be

that the $oauth class is simply not parsing it correctly.



On Tue, Oct 27, 2009 at 11:31, TylerC  wrote:


I really don't get it now... I am making a call to get all my  
friends
and I am only getting data between the  tags. I  
need to
get cursors and while they are returned when going through the  
browser

they do not show up when ran from my script. wtf...



   $users = $oauth->oAuthRequest(
   "

http://twitter.com/statuses/friends.xml?cursor=-1

",
   array(), "GET"
   );



   $xml = simplexml_load_string($users);
   $next_page = $xml->next_cursor;



Its like the only data returned is the user array...



--
Internets. Serious business.



--
Internets. Serious business.

[twitter-dev] Re: XML parsing error when using JSON search.twitter.com/search.json?

[Michael Steuer]

You're getting 403 errors from Twitter. You're being rate limited  
because you're not passing a user agent. From the search API wiki:


Applications must have a meaningful and unique User Agent when using  
this method. A HTTP Referrer is expected but not required. Search  
traffic that does not include a User Agent will be rate limited to  
fewer API calls per hour than applications including a User Agent  
string.
Try using curl instead of file_get_contents to set a meaningful user  
agent




On Oct 25, 2009, at 10:20 AM, TrixJo  wrote:



I have used the ampersand which is displayed in my code here:

http://pastebin.com/m51f7a9dd

are there any other takers who can give me advice on why I get the
errors:

failed to open stream: HTTP request failed! HTTP/1.1 403 Forbidden





On Oct 24, 1:23 pm, Mark Mcbride  wrote:

If you're embedding that URL in XML you will need to XML encode it...
In this specific case the ampersand (&q=...) needs to be replaced  
with

&

Sent from mobile device

On Oct 24, 2009, at 10:19 AM, JDG  wrote:




You sure that's where the error is? there have been numerous
reported problems with PHP's JSON decoder that it doesn't handle the
very large numbers of Twitter's IDs well.



On Sat, Oct 24, 2009 at 11:11, TrixJo  wrote:



Hello



I am trying to search twitter content using a mySQL/PHP entry in a
table:



$contents = file_get_contents(
   "http://search.twitter.com/search.json?
lang=en&rpp=5&q=".urlencode($row[topicTitle]));



$json = json_decode($contents);



I am returning the results via AJAX as an XML file



The problem that I get is:



XML Parsing Error: not well-formed
Location:http://www.domain.com/path/to/my/script.php?&id=2765
Line Number 77, Column 44:[refresh_url] => ?
since_id=5126537872&q=Indonesia



where "Indonesia" happens to be the value of $row[topicTitle]



The problem is with the value of $row[topicTitle]  -- doesn't matter
if the term is "Indonesia" or any other word or phrase (I tried a
bunch) -- I keep getting that XML error



I also tried enclosing it with single quotes, same error



help please?



--
Internets. Serious business.

[twitter-dev] Re: Connection Reset by Peer

[Michael Steuer]

Rate limits generate specific http error codes when met, not  
connection resets... I'm assuming you, Twitter or someone in the  
middle is experiencing some sort of network related issue. Have you  
tried tracerouting to Twitter and see if you hit any roadblocks on the  
way?




On Oct 24, 2009, at 10:02 PM, Jesse Stay  wrote:

This is a whitelisted account on a whitelisted IP so I don't see how  
it could be a rate-limit.  It's using basic auth - is there an easy  
way to use oAuth for whitelisted accounts?  This has worked for the  
last year or so up until today.


Jesse

On Sat, Oct 24, 2009 at 10:20 PM, Atul Kulkarni > wrote:
Are you using Basic Auth? Are you using the same account to tweet  
and are u tweeting simultaneously while working? If none of the  
above then u have reached ur rate limit. Wait for an hour and try  
again. Else I don't understand what could have happened. I had this  
a few days back and reason was rate limit.


On Sat, Oct 24, 2009 at 11:16 PM, Jesse Stay   
wrote:
I'm seeing constant Connection Reset by Peer errors on one of my  
servers.  Is anyone else seeing this?  Have I hit a limit of some  
sort?  It's been happening all day long it seems.


Jesse



--
Regards,
Atul Kulkarni
www.d.umn.edu/~kulka053

[twitter-dev] Re: Net::Twitter dev release with Lists API support

[Michael Steuer]

+1 - would really like to start implementing.



On Oct 23, 2009, at 11:31 PM, Jesse Stay  wrote:

How do I get on the List beta?  I'd really like to use it.  Who do I  
pay and how much?


Jesse

On Fri, Oct 23, 2009 at 10:47 PM, Marc Mims   
wrote:


I uploaded a development release of Net::Twitter to CPAN with Lists  
API

support.  If you're a perl developer and you're on the Lists beta,
please test it and give me some feedback.

Download it here:
http://search.cpan.org/~mmims/Net-Twitter-3.07999_01/

For documentation see:

   perldoc Net::Twitter::Role::API::Lists

You'll need to include the API::Lists trait:

   my $nt = Net::Twitter->new(traits => ['API::Lists', ...], ...);

You can always use the "user" parameter as the first placeholder
argument to any of the API calls.  Any or all of the parameters  
included

in the API URL can be passed as placeholder arguments.  Additional
arguments are passed by name in a HASH ref as the final argument.  Any
or all parameters can be passed in the HASH ref.

For example, these calls are equivalent:

   my $list = $nt->create_list(perl_api =>
   { name => 'test', mode => private }
   );

   my $list = $nt->create_list({
   user => 'perl_api',
   name => 'test',
   mode => 'private',
   });

In my own testing, I've noticed that the update_list call always  
returns

a 500 status, even though it succeeds.  That's probably a Twitter bug
that will be worked out.

The Lists API support is experimental.  It will very likely change
before a final release.  Feedback welcome.

   -Marc

[twitter-dev] Re: API Proposal : Bulk fetch of user details

[Michael Steuer]

I don't see why the data size would make a difference. I currently  
request the same amount of data in 100 calls of 1 user, as I would in  
1 call of 100 users. My application does require a little more info  
than yours apparently, and I'm sure every app requires a different  
subset, so a user object should remain a user object and return all  
info.


Other than that, totally in favor of the bulk API, as expressed  
repeatedly before...




On Oct 22, 2009, at 7:06 PM, Harshad RJ  wrote:


Thanks Tim for the reference, I have starred it.

That issue suggests bulk-id support, but there is no proposal for a  
compromise on the size of the data. It might be a crucial difference  
to Twitter.



On Fri, Oct 23, 2009 at 5:00 AM, Tim Haines   
wrote:

http://code.google.com/p/twitter-api/issues/detail?id=1078



--
Harshad RJ
http://hrj.wikidot.com

[twitter-dev] Oauth_token and oauth_token_secret length

[Michael Steuer]

Is there a fixed max length for the oauth_token and the oauth_token_secret?
What kind of fields are you guys using to store these in your databases?
Varchar? And yes, please let me know what the max length to expect is for
each... The docs on twitter.com as well as oauth.net are somewhat unclear
about this (at least to me).

Thanks!

Michael.

[twitter-dev] Re: Very slow response with API from Slicehost

[Michael Steuer]

No, seeing the same since Saturday. @rsarver said on Sunday morning he would
post information to the group once they knew what was causing all this, but
I guess 4 days later they still don't know, as we haven't heard anything...




On 10/21/09 9:05 AM, "RandyC"  wrote:

> 
> I have been seeing enormous numbers of 502's and 500's for API calls
> from Qwest DSL business, Rackspace, and Amazon Cloud instances since
> Saturday through today.  Working through the UI to log into accounts
> is equally painful with constant fail whales after two to three
> attempts.  Seems like a couple of bad hair days so far and very
> difficult to get much done.  I'm surprised more people aren't talking
> about this unless we're the only ones affected.

[twitter-dev] Re: New cursor methods are way too slow

[Michael Steuer]

Hi,

The reason why I¹m using followers/ids and then users/show is efficiency:

I¹m maintaining a local cache of my users social graph. I¹m also maintaining
local user objects for my users and for their followers. Since both the
social graph and user info are subject to change, both need periodic
updating... They way I¹m doing that now is as follows:

1. I request followers/ids for each of my users
2. If I detect new followers I add them to my users social graph / If I
detect followers removed, I remove them from my users social graph

Subsequently I parse my user object table for users whose:
1. info hasn¹t been updated in X days
2. have no info because they were added as numeric IDs only via the
followers/ids method described above

I then request users/show for each user matching condition 1 or 2 above.

This way, I only get an updated user object for each unique user once, when
they¹re first added, or when I expire a previous update to their info. When
I get the followers of another new user, chances are I already know the
majority of his followers user information.

I¹m not using statuses/followers because I would be getting the same
information over and over and over and over again... Especially when you¹re
talking about users with a lot of followers, it¹s really inefficient
considering you probably already store user info on most of the user¹s
followers... It would be an equally efficient method if overlap in followers
didn¹t exist... Since it does, I believe my approach is more efficient, and
faster over time, as your user database grows and your basically just
querying the social graph...

ALL THAT SAID ­ I would LOVE to have a method that allows me to get user
objects in batch... If I could request 100 user objects by numeric id in one
API call, the above would be exponentially efficient and result in far fewer
calls to Twitter.

I am definitely interested in your feedback on my logic above and if you
think it holds...

Thanks!

Michael.


On 10/15/09 7:02 PM, "Tim Haines"  wrote:

> FYI, My backend cares.  
> 
> On Fri, Oct 16, 2009 at 2:07 PM, jmathai  wrote:
>> 
>> I'm curious why you're using followers/ids and then users/show for
>> each id?  I tried using that and using statuses/followers and found
>> that the total times were in the same ballpark.  statuses/followers
>> requires far fewer api calls if you're interested in user objects.
>> 
>> FYI, I do want to add and say I agree that either method is EXTREMELY
>> inefficient.  Regardless what the argument against pages and for
>> cursors are...the current implementation is painful from an end user
>> perspective.  Our backend doesn't really care, but our users don't
>> like to wait 10-30 minutes for a web page to gather a social graph.
>> 
>> I wish instead of a cursor I could get a snapshot id, # of pages and a
>> page parameter.  I don't know how it's implemented, but the ability to
>> deterministically parallelize the calls - is such a benefit to the end
>> user.  Pages let me do that.
>> 
>> On Oct 15, 9:17 am, Michael Steuer  wrote:
>>> > That's great!! I'm currently using the suggested method (get IDs, then do
>>> > users/show for each of them) and it's horrendously slow and cumbersome.
>>> It'd
>>> > be great if you could get a 100 user objects at the time, based on 100 ids
>>> > you provide..
>>> >
>>> > On 10/14/09 7:30 PM, "Chad Etzel"  wrote:
>>> >
>>> >
>>> >
>>>> > > I agree. I'm lobbying the team for something like this.
>>>> > > -Chad
>>> >
>>>> > > On Wed, Oct 14, 2009 at 10:21 PM, Josh Roesslein 
>>>> wrote:
>>> >
>>>>> > >> Yeah we really need a way to bulk request user payloads by giving a
>>>>> list of
>>>>> > >> IDs.
>>> >
>>>>> > >> On Wed, Oct 14, 2009 at 9:19 PM, Tim Haines 
>>>>> wrote:
>>> >
>>>>>> > >>> Are you suggesting I should retrieve the 2k users 1 at a time from
>>>>>> > >>> users/show once I have the ids?  I'd essentially like to do this,
but
>>>>>> > >>> 100 at a time.
>>> >
>>>>>> > >>> I know I can get the 7000 ids in 2 calls (1 even without the
>>>>>> cursors)
>>>>>> > >>> - but I actually want the whole user objects..
>>> >
>>>>>> > >>> Tim.
>>> >
>>>>>> > >>> On Oct 15, 2:56 pm, Chad Etzel  wrote:
>>>&

[twitter-dev] Re: 502 error for public timeline

[Michael Steuer]

I've been seeing fail whales on the site as well.. Something must be going
on...


On 10/19/09 3:03 PM, "Scott Haneda"  wrote:

> 
> I am calling the public timeline once every 60 seconds.  Today has
> been a bad day, 26 total 502 errors since 12:21 PST to now.  http
> public timeline is fine on the website.  Any ideas when this is going
> to be resolved, or if it is even something that Twitter is aware of?
> If not, heads up :)

[twitter-dev] Re: Problems Connecting to the API

[Michael Steuer]

Hi All,

While it's not complete unreachability like yesterday morning, I'm again
experiencing, let's call it spotty reachability this morning... Requests
time out or are really slow to complete... Anyone else seeing this?

Thanks,

Michael.


On 10/19/09 9:45 AM, "John Kalucki"  wrote:

> 
> Dewald, are you down, getting weird headers, or OK?
> 
> If you can't connect at all, traceroutes are best. If you get weird
> headers, a copy of the header (and your IP address) are best.
> 
> Thanks.
> 
> On Oct 18, 7:23 am, Dewald Pretorius  wrote:
>> traceroute to twitter.com (168.143.162.100), 30 hops max, 40 byte
>> packets
>>  1  81.b5.85ae.static.theplanet.com (174.133.181.129)  1.351 ms  1.439
>> ms  1.464 ms
>>  2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.198 ms  0.229
>> ms  0.266 ms
>>  3  et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.444 ms
>> et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
>> 0.224 ms et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.466 ms
>>  4  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.519 ms
>> et1-2.ibr02.hstntx2.theplanet.com (70.87.253.169)  0
>> .454 ms  0.522 ms
>>  5  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  167.161 ms
>> 167.045 ms  167.206 ms
>>  6  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.185 ms
>> 1.164 ms  1.180 ms
>>  7  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.424
>> ms  6.331 ms  6.358 ms
>>  8  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.400 ms
>> 6.451 ms  6.489 ms
>>  9  * * *
>> 
>> --
>> 
>> traceroute to twitter.com (168.143.162.116), 30 hops max, 40 byte
>> packets
>>  1  81.b5.85ae.static.theplanet.com (174.133.181.129)  0.387 ms  0.432
>> ms  0.475 ms
>>  2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.211 ms  0.257
>> ms  0.273 ms
>>  3  et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.472 ms
>> et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
>> 0.221 ms  0.249 ms
>>  4  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.404 ms  0.466
>> ms  0.553 ms
>>  5  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  107.597 ms
>> 107.679 ms  107.742 ms
>>  6  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.136 ms
>> 1.114 ms  1.035 ms
>>  7  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.293
>> ms  8.708 ms  6.335 ms
>>  8  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.433 ms
>> 6.486 ms  6.535 ms
>>  9  * * *
>> 
>> -
>> 
>> traceroute to twitter.com (168.143.162.36), 30 hops max, 40 byte
>> packets
>>  1  81.b5.85ae.static.theplanet.com (174.133.181.129)  0.429 ms  0.515
>> ms  0.567 ms
>>  2  et2-5.ibr02.hstntx1.theplanet.com (207.218.245.5)  8.956 ms  8.986
>> ms  9.024 ms
>>  3  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.439 ms  0.493
>> ms  0.546 ms
>>  4  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  1.156 ms
>> 1.206 ms  1.254 ms
>>  5  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.114 ms
>> 1.113 ms  1.131 ms
>>  6  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.280
>> ms  6.256 ms  6.717 ms
>>  7  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.377 ms
>> 6.444 ms  6.499 ms
>>  8  * * *
>> 
>> On Oct 18, 11:14 am, John Kalucki  wrote:
>> 
>>> I don't see any operational issues from here, but I'm not an
>>> operational guy. At first glance the system looks fine, and the
>>> operational team isn't in response mode. This is puzzling.
>> 
>>> Seems like a connectivity issue upstream from twitter. At lest a few
>>> developers: please send a traceroute to this list. Also, if you aren't
>>> timing out, but rather are getting an HTTP error, send the response
>>> headers. After say 4 or 5 responses, they'll probably have enough info
>>> to triage this.
>> 
>>> -John Kaluckihttp://twitter.com/jkalucki
>>> Services, Twitter Inc.
>> 
>>> On Oct 18, 6:40 am, Dewald Pretorius  wrote:
>> 
 Does anyone else have problems connecting to the API at the moment
 (Sunday morning October 18)?
>> 
 Dewald

[twitter-dev] Re: Draft of List API documentation

[Michael Steuer]

+1 for referring to lists by id and a bulk add feature. But as bulk  
features go, my highest priority is still the one discussed under the  
"cursors are slow" thread, ie. retrieving user objects based on id in  
bulk (vs doing users/show for each individual id retrieved via the  
social graph methods).




On Oct 19, 2009, at 12:40 AM, Tim Haines  wrote:

I'll +1 the requests for using the list id instead of the slug (and  
user id instead of screen name), and for a bulk add feature - I've  
already asked for a bulk remove feature...


Tim.

On Sun, Oct 18, 2009 at 5:34 PM, Beier  wrote:

I'm just wondering why can't we use list 'id' to call API functions
such as update, delete, timelines?

I found out that list_slug can change when you update list name. This
will give 3rd party apps lots of headaches. For example, right now my
app has group features and I'm planning to migrate it to list. But if
a user changes the list name on twitter.com or another app, then I'll
have no idea and the list url I stored in database won't be valid
anymore.

On Oct 16, 12:04 am, Marcel Molina  wrote:
> Hey folks. As some of you have likely read we're starting to do some
> private beta testing of our new lists feature. We're not quite ready
> to open it up to everyone but we've made some headway on the API and
> wanted to share some details of what we've got so far.
>
> There are a handful of things on our todo lists so don't consider  
this

> signed and sealed just yet.
>
> You may notice this API is a bit of a departure from the rest of the
> API. It's a bit more, errr, REST than the rest.
>
> First off, here's the current payload for a list:
>
> 
> 
>   1416
>   tall people
>   @noradio/tall-people
>   tall-people
>   0
>   3
>   /noradio/tall-people
>   public
>   
> 3191321
> Marcel Molina
> noradio
> San Francisco, CA
> Engineer at Twitter on the @twitterapi team,  
obsessed
> with rock climbing & running. In a past life I was a member of  
the

> Rails Core team.
> http://a3.twimg.com/profile_images/53473799/marcel-euro-rails-conf_no 
...

> http://project.ioni.st
> false
> 40059
> 9AE4E8
> 33
> 0084B4
> DDFFCC
> BDDCADprofile_sidebar_border_color>

> 354
> Mon Apr 02 07:47:28 + 2007
> 131
> -28800
> Pacific Time (US & Canada)
> http://a1.twimg.com/profile_background_images/18156348/jessica_tiled 


> true
> 3472
> false
> true
> false
> false
>   
> 
>
> === Lists ===
>
> POST '/:user/lists.:format'
> Creates a new list for the authenticated user.
>
> Parameters:
>  * name: the name of the list. (required)
>  * mode: whether your list is public of private. Values can be
> 'public' or 'private'. Public by default if not specified.  
(optional)

>
> Usage notes:
>  ":user" in the url should be the screen name of the user making the
> request to create the list
>
> Supported formats:
> xml, json
>
> e.g.
>  curl -u USERNAME:PASSWORD -d "name=tall 
people&mode=private"http://twitter.com/noradio/lists.xml
>
> POST/PUT '/:user/lists/:list_slug.:format'
> Updates the specified list.
>
> Takes the same parameters as the create resource at POST
> '/:user/lists.:format' (:name and :mode).
>
> Supported formats:
> xml, json
>
> e.g.
>  curl -u USERNAME:PASSWORD -d 
"name=giants&mode=public"http://twitter.com/noradio/lists/tall-people.xml
>
> GET '/:user/lists.:format'
> Lists your lists.
>
> Supported format:
> xml, json
>
> e.g.
>  curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists.xml
>
> GET '/:user/lists/memberships.:format'
> List the lists the specified user has been added to.
>
> Supported formats:
> xml, json
>
> e.g.
>  curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists/ 
memberships.xml

>
> DELETE '/:user/lists/:list_slug.:format'
> Delete the specified list owned by the authenticated user.
>
> Parameters:
>  * list_slug: the slug of the list you want to delete. (required)
>
> Supported formats:
> xml, json
>
> e.g.
>  curl -u USERNAME:PASSWORD -X DELETEhttp://twitter.com/noradio/ 
lists/tall-people.xml

>
> GET '/:users/lists/:list_slug/statuses.:format'
> Show tweet timeline for members of the specified list.
>
> Parameters:
>  * list_slug: the slug of the list you want the member tweet  
timeline

> of. (required)
>  * next/previous_cursor: used to "page" through results (optional)
>
> Supported formats:
> xml, json
>
> e.g.
>  curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists/tall- 
people/statuses.xml

>
> GET '/:users/lists/:list_slug.:format'
> Show a specific list you can use the new resource.
>
> Supported formats:
> xml, json
>
> e.g.
>   curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists/tall- 
people.xml

>
> === List members ===
>
> POST '/:user/:list_slug/members.:format'
> Add a member to a list.
>
> Parameters:
>  * id: the id of the user you want to add as a member to the list.  
(required)

>
> Usage notes:
> The :list_slug portion of the request path sho

[twitter-dev] Re: Problems Connecting to the API

[Michael Steuer]

It is working for me. Would you mind sharing with the group what  
exactly happened?


Thanks.

Michael



On Oct 18, 2009, at 10:53 AM, Atul Kulkarni   
wrote:



Works Fine... Duluth, MN.

On Sun, Oct 18, 2009 at 12:51 PM, Ryan Sarver   
wrote:


I wanted to check in and see if everyone is back to normal? We think
things have been fixed but its hard to confirm without your help.

Let me know if you are still experiencing any issues and if so, where
you are located.

Best, Ryan

On Sun, Oct 18, 2009 at 10:48 AM, Dewald Pretorius  
 wrote:

>
> Same here. Can connect again.
>
> On Oct 18, 2:46 pm, Michael Steuer  wrote:
>> The situation seems to have been resolved, at least for me, as of a
>> few minutes ago. My Rackspace hosted servers can reach the API  
again...

>>
>> On Oct 18, 2009, at 10:35 AM, Dewald Pretorius   
wrote:

>>
>>
>>
>> > I don't really blame Twitter Ops for not knowing. It's probably  
a new

>> > edge defense that was installed by their service provider during
>> > Sunday night.
>>
>> > However, a while ago Alex said the Platform team were working  
on an
>> > external monitoring solution. Hopefully Ryan, who is now  
Director of

>> > the Platform team, will quickly move this forward to completion.
>>
>> > Dewald
>>
>> > On Oct 18, 1:30 pm, Michael Steuer  wrote:
>> >> Amen to that. I find it kind of curious that as per John K., 5-6
>> >> hours
>> >> into this issue, the Twitter ops team was still blissfully  
unaware of
>> >> anything going on... Also weird that they apparently are  
unable to
>> >> reproduce the issue without our help, ie. they really haven't  
set up

>> >> any monitoring outside of their network...
>>
>> >> On Oct 18, 2009, at 9:05 AM, Dewald Pretorius 
>> >> wrote:
>>
>> >>> I'd be more than happy to wait longer for snazzy API 2.0  
features so

>> >>> that the Platform team can build a QoS system that monitors the
>> >>> API's
>> >>> availability and performance from the outside. That will enable
>> >>> Twitter to catch these kinds of issues long before we do.
>>
>> >>> Dewald
>>
>> >>> On Oct 18, 12:47 pm, Michael Steuer  wrote:
>> >>>> This outage is now going on 7 hours. Any word from Twitter  
as to an

>> >>>> ETA for resolution?
>>
>> >>>> On Oct 18, 2009, at 8:08 AM, John Meyer  


>> >>>> wrote:
>>
>> >>>>> John Kalucki wrote:
>> >>>>>> And here's the next question:
>>
>> >>>>>> Is anyone having trouble from non-service, non-hosted
>> >>>>>> endpoints. In
>> >>>>>> other words, problem from home ISPs and desktop clients?
>>
>> >>>>>> -John Kalucki
>> >>>>>>http://twitter.com/jkalucki
>> >>>>>> Services, Twitter Inc.
>>
>> >>>>> Yep. (comcast, cannot access through either the website or  
desktop

>> >>>>> clients).
>



--
Regards,
Atul Kulkarni
www.d.umn.edu/~kulka053

[twitter-dev] Re: Problems Connecting to the API

[Michael Steuer]

Setting up external monitoring isn't a huge undertaking. Their are  
plenty of existing services out there already. Even free ones like pingdom.com 
. Perhaps Twitter should set up a couple of those until they have  
their full QoS implementation in place. Pingdom for example would have  
started sending them emails and SMS messages at 2am pst this morning,  
when the issue started. They could have then escalated to their ISP  
and this whole thing wouldn't have lasted for close to 9 hours.




On Oct 18, 2009, at 10:35 AM, Dewald Pretorius  wrote:



I don't really blame Twitter Ops for not knowing. It's probably a new
edge defense that was installed by their service provider during
Sunday night.

However, a while ago Alex said the Platform team were working on an
external monitoring solution. Hopefully Ryan, who is now Director of
the Platform team, will quickly move this forward to completion.

Dewald

On Oct 18, 1:30 pm, Michael Steuer  wrote:
Amen to that. I find it kind of curious that as per John K., 5-6  
hours

into this issue, the Twitter ops team was still blissfully unaware of
anything going on... Also weird that they apparently are unable to
reproduce the issue without our help, ie. they really haven't set up
any monitoring outside of their network...

On Oct 18, 2009, at 9:05 AM, Dewald Pretorius   
wrote:





I'd be more than happy to wait longer for snazzy API 2.0 features so
that the Platform team can build a QoS system that monitors the  
API's

availability and performance from the outside. That will enable
Twitter to catch these kinds of issues long before we do.



Dewald



On Oct 18, 12:47 pm, Michael Steuer  wrote:

This outage is now going on 7 hours. Any word from Twitter as to an
ETA for resolution?



On Oct 18, 2009, at 8:08 AM, John Meyer 
wrote:



John Kalucki wrote:

And here's the next question:


Is anyone having trouble from non-service, non-hosted  
endpoints. In

other words, problem from home ISPs and desktop clients?



-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.



Yep. (comcast, cannot access through either the website or desktop
clients).

[twitter-dev] Re: Problems Connecting to the API

[Michael Steuer]

The situation seems to have been resolved, at least for me, as of a  
few minutes ago. My Rackspace hosted servers can reach the API again...




On Oct 18, 2009, at 10:35 AM, Dewald Pretorius  wrote:



I don't really blame Twitter Ops for not knowing. It's probably a new
edge defense that was installed by their service provider during
Sunday night.

However, a while ago Alex said the Platform team were working on an
external monitoring solution. Hopefully Ryan, who is now Director of
the Platform team, will quickly move this forward to completion.

Dewald

On Oct 18, 1:30 pm, Michael Steuer  wrote:
Amen to that. I find it kind of curious that as per John K., 5-6  
hours

into this issue, the Twitter ops team was still blissfully unaware of
anything going on... Also weird that they apparently are unable to
reproduce the issue without our help, ie. they really haven't set up
any monitoring outside of their network...

On Oct 18, 2009, at 9:05 AM, Dewald Pretorius   
wrote:





I'd be more than happy to wait longer for snazzy API 2.0 features so
that the Platform team can build a QoS system that monitors the  
API's

availability and performance from the outside. That will enable
Twitter to catch these kinds of issues long before we do.



Dewald



On Oct 18, 12:47 pm, Michael Steuer  wrote:

This outage is now going on 7 hours. Any word from Twitter as to an
ETA for resolution?



On Oct 18, 2009, at 8:08 AM, John Meyer 
wrote:



John Kalucki wrote:

And here's the next question:


Is anyone having trouble from non-service, non-hosted  
endpoints. In

other words, problem from home ISPs and desktop clients?



-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.



Yep. (comcast, cannot access through either the website or desktop
clients).

[twitter-dev] Re: Problems Connecting to the API

[Michael Steuer]

Amen to that. I find it kind of curious that as per John K., 5-6 hours  
into this issue, the Twitter ops team was still blissfully unaware of  
anything going on... Also weird that they apparently are unable to  
reproduce the issue without our help, ie. they really haven't set up  
any monitoring outside of their network...




On Oct 18, 2009, at 9:05 AM, Dewald Pretorius  wrote:



I'd be more than happy to wait longer for snazzy API 2.0 features so
that the Platform team can build a QoS system that monitors the API's
availability and performance from the outside. That will enable
Twitter to catch these kinds of issues long before we do.

Dewald

On Oct 18, 12:47 pm, Michael Steuer  wrote:

This outage is now going on 7 hours. Any word from Twitter as to an
ETA for resolution?

On Oct 18, 2009, at 8:08 AM, John Meyer   
wrote:





John Kalucki wrote:

And here's the next question:



Is anyone having trouble from non-service, non-hosted endpoints. In
other words, problem from home ISPs and desktop clients?



-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.



Yep. (comcast, cannot access through either the website or desktop
clients).

[twitter-dev] Re: Problems Connecting to the API

[Michael Steuer]

This outage is now going on 7 hours. Any word from Twitter as to an  
ETA for resolution?




On Oct 18, 2009, at 8:08 AM, John Meyer  wrote:



John Kalucki wrote:

And here's the next question:

Is anyone having trouble from non-service, non-hosted endpoints. In
other words, problem from home ISPs and desktop clients?

-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.




Yep. (comcast, cannot access through either the website or desktop  
clients).

[twitter-dev] Re: Problems Connecting to the API

[Michael Steuer]

I only have two endpoints to test from. Hosted: fails. Home DSL: no  
problem. I have several iPhone clients, but I'm bot sure if they're  
proxies or connect to the API directly...




On Oct 18, 2009, at 7:56 AM, John Kalucki  wrote:



And here's the next question:

Is anyone having trouble from non-service, non-hosted endpoints. In
other words, problem from home ISPs and desktop clients?

-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.


On Oct 18, 7:55 am, John Kalucki  wrote:

OK. I think we have enough traceroutes for now. Thanks for sending
them in!

If we need more datapoints or information, I'll update this thread.

On Oct 18, 7:14 am, John Kalucki  wrote:


I don't see any operational issues from here, but I'm not an
operational guy. At first glance the system looks fine, and the
operational team isn't in response mode. This is puzzling.



Seems like a connectivity issue upstream from twitter. At lest a few
developers: please send a traceroute to this list. Also, if you  
aren't

timing out, but rather are getting an HTTP error, send the response
headers. After say 4 or 5 responses, they'll probably have enough  
info

to triage this.



-John Kaluckihttp://twitter.com/jkalucki
Services, Twitter Inc.



On Oct 18, 6:40 am, Dewald Pretorius  wrote:



Does anyone else have problems connecting to the API at the moment
(Sunday morning October 18)?



Dewald

[twitter-dev] Re: Problems Connecting to the API

[Michael Steuer]

So somewhere before you reach twitter.com, traceroute must get
blocked. I just did a traceroute from my home (Verizon DSL) where I
can access Twitter perfectly, and traceroute still doesn't complete:

michael-steuers-computer:~ msteuer$ traceroute twitter.com
traceroute to twitter.com (128.121.146.100), 64 hops max, 52 byte
packets
 1  192.168.1.1 (192.168.1.1)  0.611 ms  0.311 ms  0.197 ms
 2  10.35.27.1 (10.35.27.1)  21.969 ms  22.321 ms  21.706 ms
 3  p0-3.lsanca-lcr-03.verizon-gni.net (130.81.34.248)  21.712 ms
21.478 ms  21.507 ms
 4  so-6-1-2-0.lax01-bb-rtr1.verizon-gni.net (130.81.28.225)  21.958
ms  21.830 ms  22.000 ms
 5  0.so-6-3-0.xt1.lax9.alter.net (152.63.10.153)  23.446 ms  23.323
ms  23.743 ms
 6  0.so-5-1-0.xt1.lax7.alter.net (152.63.116.253)  48.239 ms  24.029
ms  23.228 ms
 7  pos6-0.br2.lax7.alter.net (152.63.112.145)  23.472 ms  23.722 ms
23.467 ms
 8  p64-6-1-3.r20.lsanca03.us.bb.gin.ntt.net (129.250.8.205)  25.215
ms  24.968 ms  24.735 ms
 9  as-0.r21.snjsca04.us.bb.gin.ntt.net (129.250.4.96)  35.987 ms
36.747 ms  35.958 ms
10  po-2.r04.snjsca04.us.bb.gin.ntt.net (129.250.6.6)  36.516 ms
37.034 ms *
11  * * *

So I don't know how helpful all these traceroute results are going to
be for Twitter, given that both from networks that can connect, and
those that can't the traceroutes fail in the "ntt.net" or "telia.net"
networks

On Oct 18, 7:33 am, TCI  wrote:
> Tracert disabled from host - fail!
> But I assume that if we can't reach you, you should not be able to
> reach us either? My server's IP is 174.120.0.108 (The Planet)
>
> On Oct 18, 8:14 am, John Kalucki  wrote:
>
>
>
> > I don't see any operational issues from here, but I'm not an
> > operational guy. At first glance the system looks fine, and the
> > operational team isn't in response mode. This is puzzling.
>
> > Seems like a connectivity issue upstream from twitter. At lest a few
> > developers: please send a traceroute to this list. Also, if you aren't
> > timing out, but rather are getting an HTTP error, send the response
> > headers. After say 4 or 5 responses, they'll probably have enough info
> > to triage this.
>
> > -John Kaluckihttp://twitter.com/jkalucki
> > Services, Twitter Inc.
>
> > On Oct 18, 6:40 am, Dewald Pretorius  wrote:
>
> > > Does anyone else have problems connecting to the API at the moment
> > > (Sunday morning October 18)?
>
> > > Dewald

[twitter-dev] Re: Problems Connecting to the API

[Michael Steuer]

On my end: my server (at Rackspace) can't connect to twitter.com... If I
enter API URLs into my browser at home (Verizon DSL), I connect just fine.
Here's a traceroute from rackspace:

traceroute twitter.com
traceroute to twitter.com (168.143.161.20), 30 hops max, 60 byte packets
 1  xxx-xxx-xxx-xxx.static.cloud-ips.com (xxx.xxx.xxx.xxx)  4.000 ms  4.000
ms  4.000 ms
 2  98.129.84.216 (98.129.84.216)  0.000 ms  0.000 ms  0.000 ms
 3  edge3-core7-vlan3307.dfw1.rackspace.net (174.143.123.115)  4.000 ms
 4.000 ms edge3-core7-vlan2307.dfw1.rackspace.net (174.143.123.113)  4.000
ms
 4  dls-bb1-link.telia.net (213.248.88.173)  4.000 ms  4.000 ms  4.000 ms
 5  verio-ic-127187-dls-bb1.c.telia.net (213.248.81.62)  96.005 ms  96.005
ms  96.005 ms
 6  * * *

Based on my logs, this has been going on since before 2AM PST


On Sun, Oct 18, 2009 at 7:23 AM, Dewald Pretorius  wrote:

>
> traceroute to twitter.com (168.143.162.100), 30 hops max, 40 byte
> packets
>  1  81.b5.85ae.static.theplanet.com (174.133.181.129)  1.351 ms  1.439
> ms  1.464 ms
>  2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.198 ms  0.229
> ms  0.266 ms
>  3  et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.444 ms
> et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
> 0.224 ms et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.466 ms
>  4  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.519 ms
> et1-2.ibr02.hstntx2.theplanet.com (70.87.253.169)  0
> .454 ms  0.522 ms
>  5  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  167.161 ms
> 167.045 ms  167.206 ms
>  6  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.185 ms
> 1.164 ms  1.180 ms
>  7  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.424
> ms  6.331 ms  6.358 ms
>  8  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.400 ms
> 6.451 ms  6.489 ms
>  9  * * *
>
> --
>
> traceroute to twitter.com (168.143.162.116), 30 hops max, 40 byte
> packets
>  1  81.b5.85ae.static.theplanet.com (174.133.181.129)  0.387 ms  0.432
> ms  0.475 ms
>  2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.211 ms  0.257
> ms  0.273 ms
>  3  et1-3.ibr01.hstntx2.theplanet.com (70.87.253.154)  0.472 ms
> et3-2.ibr02.hstntx1.theplanet.com (70.87.253.157)
> 0.221 ms  0.249 ms
>  4  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.404 ms  0.466
> ms  0.553 ms
>  5  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  107.597 ms
> 107.679 ms  107.742 ms
>  6  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.136 ms
> 1.114 ms  1.035 ms
>  7  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.293
> ms  8.708 ms  6.335 ms
>  8  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.433 ms
> 6.486 ms  6.535 ms
>  9  * * *
>
> -
>
> traceroute to twitter.com (168.143.162.36), 30 hops max, 40 byte
> packets
>  1  81.b5.85ae.static.theplanet.com (174.133.181.129)  0.429 ms  0.515
> ms  0.567 ms
>  2  et2-5.ibr02.hstntx1.theplanet.com (207.218.245.5)  8.956 ms  8.986
> ms  9.024 ms
>  3  et1-3.ibr02.hstntx2.theplanet.com (70.87.253.58)  0.439 ms  0.493
> ms  0.546 ms
>  4  xe-4-4.r03.hstntx01.us.bb.gin.ntt.net (128.241.1.5)  1.156 ms
> 1.206 ms  1.254 ms
>  5  xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228)  1.114 ms
> 1.113 ms  1.131 ms
>  6  p64-7-0-2.r20.dllstx09.us.bb.gin.ntt.net (129.250.3.129)  6.280
> ms  6.256 ms  6.717 ms
>  7  po-1.r01.dllstx09.us.bb.gin.ntt.net (129.250.3.74)  6.377 ms
> 6.444 ms  6.499 ms
>  8  * * *
>
>
> On Oct 18, 11:14 am, John Kalucki  wrote:
> > I don't see any operational issues from here, but I'm not an
> > operational guy. At first glance the system looks fine, and the
> > operational team isn't in response mode. This is puzzling.
> >
> > Seems like a connectivity issue upstream from twitter. At lest a few
> > developers: please send a traceroute to this list. Also, if you aren't
> > timing out, but rather are getting an HTTP error, send the response
> > headers. After say 4 or 5 responses, they'll probably have enough info
> > to triage this.
> >
> > -John Kaluckihttp://twitter.com/jkalucki
> > Services, Twitter Inc.
> >
> > On Oct 18, 6:40 am, Dewald Pretorius  wrote:
> >
> > > Does anyone else have problems connecting to the API at the moment
> > > (Sunday morning October 18)?
> >
> > > Dewald
>

[twitter-dev] Re: Problems Connecting to the API

[Michael Steuer]

In fact, looking at my logs, the API was down since at least 2 AM  
Pacific (5 hours ago)...




On Oct 18, 2009, at 6:40 AM, Dewald Pretorius  wrote:



Does anyone else have problems connecting to the API at the moment
(Sunday morning October 18)?

Dewald