Re: [twitter-dev] can't post same message more than 1 time Getting error: The remote server returned an error: (403) Forbidden.

[Mark McBride]

This is the intended behavior
   ---Mark

http://twitter.com/mccv



On Mon, May 10, 2010 at 9:34 PM, manjunath hindupur  wrote:
> Scenario like :
>
> i want post same message twice in a same account, if i Try to send
> same message twice by using API.. getting error Like below : The
> remote server returned an error: (403) Forbidden.
>
> its right behavior or Bug?
>

[twitter-dev] can't post same message more than 1 time Getting error: The remote server returned an error: (403) Forbidden.

[manjunath hindupur]

Scenario like :

i want post same message twice in a same account, if i Try to send
same message twice by using API.. getting error Like below : The
remote server returned an error: (403) Forbidden.

its right behavior or Bug?

Re: [twitter-dev] Re: Slow response to twitter updates for a third party app

[John Kalucki]

Now that we have a reasonable idea about what is transpiring, I'd
venture to say that the latency distribution will be widest between
about 6:30am to 10:30am PDT (13:30-17:30 UTC), and considerably less
so until perhaps 5pm PDT. The balance of the day should be OK.

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


On Mon, May 10, 2010 at 8:25 PM, raj  wrote:
> Hi John and Ryan,
>
> Thanks for looking into this.
>
> The good news is that now I am seeing faster responses for my
> website.
> I did not change anything on my end, but maybe you guys did, or the
> traffic was more well-behaved :)
>
>  In any case, here are my impressions of using the twitter APIs.
>
> Use case: Posting updates to Twitter using oAuth API for the case when
> the consumer app
> already has the access token.
>
> Weekdays mornings (Pacific Time) are generally slower than evenings or
> weekends.
> Two timed experiments showed it took 3 sec, and 2 sec for posting two
> consecutive updates on Monday evening.
>
> The first message often takes longer than subsequent updates for the
> same access token (any token caching going on here ?).
>
> Here is a traceroute output taken Monday evening:
>
> traceroute to twitter.com (168.143.162.36), 30 hops max, 40 byte
> packets
>  1  ip-173-201-183-251.ip.secureserver.net (173.201.183.251)  0.918
> ms  0.977 ms  1.106 ms
>  2  ip-208-109-113-169.ip.secureserver.net (208.109.113.169)  1.505
> ms  1.490 ms  1.499 ms
>  3  ip-208-109-113-158.ip.secureserver.net (208.109.113.158)  1.445
> ms  1.424 ms  1.412 ms
>  4  ip-208-109-112-162.ip.secureserver.net (208.109.112.162)  1.386
> ms  1.395 ms  1.429 ms
>  5  ip-208-109-112-138.ip.secureserver.net (208.109.112.138)  1.463
> ms  1.515 ms  1.584 ms
>  6  xe-0-2-0.mpr3.phx2.us.above.net (64.124.196.37)  1.092 ms  1.184
> ms  1.142 ms
>  7  ge-0-3-0.mpr3.lax9.us.above.net (64.125.28.70)  37.857 ms  37.838
> ms  37.811 ms
>  8  xe-0-1-0.er1.lax9.us.above.net (64.125.31.89)  38.317 ms  38.306
> ms  38.290 ms
>  9  xe-0-1-0.mpr1.lax12.us.above.net (64.125.31.189)  9.359 ms  9.476
> ms  9.461 ms
> 10  * * *
> 11  ae-1.r20.lsanca03.us.bb.gin.ntt.net (129.250.5.253)  10.309 ms * *
> 12  * * *
> 13  ae-0.r20.snjsca04.us.bb.gin.ntt.net (129.250.2.96)  89.869 ms
> 56.178 ms *
> 14  ae-2.r20.mlpsca01.us.bb.gin.ntt.net (129.250.5.6)  62.913 ms
> 62.933 ms *
> 15  * * *
> 16  128.241.122.117 (128.241.122.117)  60.817 ms  59.320 ms  59.353 ms
> 17  * * *
> 18  * * *
> 19  * * *
> 20  * * *
> 21  * * *
> 22  * * *
> 23  * * *
> 24  * * *
> 25  * * *
> 26  * * *
> 27  * * *
> 28  * * *
> 29  * * *
> 30  * * *
>
> I would be interested in any pointers you guys might have related to
> faster response times.
>
> Thanks for all your help!
>
> -Raj
>
> On May 10, 2:51 pm, John Kalucki  wrote:
>> We're pretty sure that this isn't a connectivity issue. At least, it's
>> not *just* a connectivity issue.
>>
>> -John Kaluckihttp://twitter.com/jkalucki
>> Infrastructure, Twitter Inc.
>>
>> On Mon, May 10, 2010 at 2:06 PM, mikawhite  wrote:
>> > delayed tweet:ping & traceroute
>>
>> > 64 bytes from 128.242.240.61: icmp_seq=9 ttl=244 time=36.851 ms
>>
>> > --- api.twitter.com ping statistics ---
>> > 10 packets transmitted, 8 packets received, 20% packet loss
>> > round-trip min/avg/max/stddev = 36.851/37.725/39.607/0.902 ms
>>
>> > --
>> > traceroute to api.twitter.com (128.242.240.93), 64 hops max, 40 byte
>> > packets
>> >  1  10.0.1.1 (10.0.1.1)  1.337 ms  0.661 ms  0.678 ms
>> >  2  192.168.254.254 (192.168.254.254)  2.009 ms  1.609 ms  0.977 ms
>> >  3  dr01.moab.ut.frontiernet.net (74.40.8.109)  8.835 ms  7.860 ms
>> > 9.103 ms
>> >  4  74.40.41.233 (74.40.41.233)  14.145 ms  13.365 ms  14.576 ms
>> >  5  xe--0-2-0---0.cor01.slkc.ut.frontiernet.net (74.40.4.1)  13.959
>> > ms  14.443 ms  14.768 ms
>> >  6  ae1---0.cor02.plal.ca.frontiernet.net (74.40.5.61)  34.496 ms
>> > 32.226 ms  32.357 ms
>> >  7  ae1---0.cbr01.plal.ca.frontiernet.net (74.40.3.170)  60.735 ms
>> > 65.466 ms  35.187 ms
>> >  8  xe-0.paix.plalca01.us.bb.gin.ntt.net (198.32.176.14)  34.242 ms
>> > 36.110 ms  33.274 ms
>> >  9  xe-1-1-0.r21.mlpsca01.us.bb.gin.ntt.net (129.250.3.50)  30.914 ms
>> > 37.517 ms  30.781 ms
>> > 10  mg-2.c20.mlpsca01.us.da.verio.net (129.250.29.81)  34.434 ms
>> > 36.171 ms  34.288 ms
>> > 11  128.241.122.213 (128.241.122.213)  36.377 ms  34.334 ms  33.771 ms
>> > 12  * 128.241.122.213 (128.241.122.213)  34.956 ms !X *
>> > 13  * * *
>> > -
>

[twitter-dev] Re: Slow response to twitter updates for a third party app

[raj]

Hi John and Ryan,

Thanks for looking into this.

The good news is that now I am seeing faster responses for my
website.
I did not change anything on my end, but maybe you guys did, or the
traffic was more well-behaved :)

 In any case, here are my impressions of using the twitter APIs.

Use case: Posting updates to Twitter using oAuth API for the case when
the consumer app
already has the access token.

Weekdays mornings (Pacific Time) are generally slower than evenings or
weekends.
Two timed experiments showed it took 3 sec, and 2 sec for posting two
consecutive updates on Monday evening.

The first message often takes longer than subsequent updates for the
same access token (any token caching going on here ?).

Here is a traceroute output taken Monday evening:

traceroute to twitter.com (168.143.162.36), 30 hops max, 40 byte
packets
 1  ip-173-201-183-251.ip.secureserver.net (173.201.183.251)  0.918
ms  0.977 ms  1.106 ms
 2  ip-208-109-113-169.ip.secureserver.net (208.109.113.169)  1.505
ms  1.490 ms  1.499 ms
 3  ip-208-109-113-158.ip.secureserver.net (208.109.113.158)  1.445
ms  1.424 ms  1.412 ms
 4  ip-208-109-112-162.ip.secureserver.net (208.109.112.162)  1.386
ms  1.395 ms  1.429 ms
 5  ip-208-109-112-138.ip.secureserver.net (208.109.112.138)  1.463
ms  1.515 ms  1.584 ms
 6  xe-0-2-0.mpr3.phx2.us.above.net (64.124.196.37)  1.092 ms  1.184
ms  1.142 ms
 7  ge-0-3-0.mpr3.lax9.us.above.net (64.125.28.70)  37.857 ms  37.838
ms  37.811 ms
 8  xe-0-1-0.er1.lax9.us.above.net (64.125.31.89)  38.317 ms  38.306
ms  38.290 ms
 9  xe-0-1-0.mpr1.lax12.us.above.net (64.125.31.189)  9.359 ms  9.476
ms  9.461 ms
10  * * *
11  ae-1.r20.lsanca03.us.bb.gin.ntt.net (129.250.5.253)  10.309 ms * *
12  * * *
13  ae-0.r20.snjsca04.us.bb.gin.ntt.net (129.250.2.96)  89.869 ms
56.178 ms *
14  ae-2.r20.mlpsca01.us.bb.gin.ntt.net (129.250.5.6)  62.913 ms
62.933 ms *
15  * * *
16  128.241.122.117 (128.241.122.117)  60.817 ms  59.320 ms  59.353 ms
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

I would be interested in any pointers you guys might have related to
faster response times.

Thanks for all your help!

-Raj

On May 10, 2:51 pm, John Kalucki  wrote:
> We're pretty sure that this isn't a connectivity issue. At least, it's
> not *just* a connectivity issue.
>
> -John Kaluckihttp://twitter.com/jkalucki
> Infrastructure, Twitter Inc.
>
> On Mon, May 10, 2010 at 2:06 PM, mikawhite  wrote:
> > delayed tweet:ping & traceroute
>
> > 64 bytes from 128.242.240.61: icmp_seq=9 ttl=244 time=36.851 ms
>
> > --- api.twitter.com ping statistics ---
> > 10 packets transmitted, 8 packets received, 20% packet loss
> > round-trip min/avg/max/stddev = 36.851/37.725/39.607/0.902 ms
>
> > --
> > traceroute to api.twitter.com (128.242.240.93), 64 hops max, 40 byte
> > packets
> >  1  10.0.1.1 (10.0.1.1)  1.337 ms  0.661 ms  0.678 ms
> >  2  192.168.254.254 (192.168.254.254)  2.009 ms  1.609 ms  0.977 ms
> >  3  dr01.moab.ut.frontiernet.net (74.40.8.109)  8.835 ms  7.860 ms
> > 9.103 ms
> >  4  74.40.41.233 (74.40.41.233)  14.145 ms  13.365 ms  14.576 ms
> >  5  xe--0-2-0---0.cor01.slkc.ut.frontiernet.net (74.40.4.1)  13.959
> > ms  14.443 ms  14.768 ms
> >  6  ae1---0.cor02.plal.ca.frontiernet.net (74.40.5.61)  34.496 ms
> > 32.226 ms  32.357 ms
> >  7  ae1---0.cbr01.plal.ca.frontiernet.net (74.40.3.170)  60.735 ms
> > 65.466 ms  35.187 ms
> >  8  xe-0.paix.plalca01.us.bb.gin.ntt.net (198.32.176.14)  34.242 ms
> > 36.110 ms  33.274 ms
> >  9  xe-1-1-0.r21.mlpsca01.us.bb.gin.ntt.net (129.250.3.50)  30.914 ms
> > 37.517 ms  30.781 ms
> > 10  mg-2.c20.mlpsca01.us.da.verio.net (129.250.29.81)  34.434 ms
> > 36.171 ms  34.288 ms
> > 11  128.241.122.213 (128.241.122.213)  36.377 ms  34.334 ms  33.771 ms
> > 12  * 128.241.122.213 (128.241.122.213)  34.956 ms !X *
> > 13  * * *
> > -

[twitter-dev] OAuth login without PIN but with callback on cesktop.

[Jeena]

Hi,

 I am working on a Desktop Twitter client for OS X and try to
implement OAuth login with a custom url-scheme. It is the client
Twittia http://wiki.github.com/jeena/Twittia/

I wrote to the a...@twitter.com and talked about it with them and they
finally send me here for help. They say that they have set the custom
URI-Scheme to:

twittia://oauth_token/

The problem is I never get back anything like twittia://oauth_token/
when I look at the website which redirects the user I see:



no sign of a oauth_verifier like it says in the documentatiuon. And
without it I can't get an access_token. The system works perfect with
a PIN but the redirect just doesn't work and I don't know what to do
about it.

Any help is appreciated.

 /Jeena

[twitter-dev] Re: Mobile OAuth Summary

[twittme_mobi]

Hi All,

I still think that it is reasonable to think about this.
Is there anyone from twitter doing something about it?

Thanks.

On May 4, 9:25 am, twittme_mobi  wrote:
> Hello Raffi,
>
> Could you please, get back to us on this?
> Do you have any plans on resolving that issue?
> Is there any show stopper?
> What are we doing with this?!
>
> Thanks.
>
> On Apr 29, 12:07 pm, Raffi Krikorian  wrote:
>
> > hi.
>
> > i'll follow up on this - do you have a notion of what browsers, what phones,
> > etc. your users are coming from
>
> > On Thu, Apr 29, 2010 at 1:49 AM, twittme_mobi 
> > wrote:
>
> > > Hello,
>
> > > I migrated mymobileweb site toOAuth.
> > > Now, I have a lot of users complaining that theOAuthpage of twitter
> > > is not
> > >mobilefriendly.Some of them are getting just a blank screen or just
> > > cannot open it.
>
> > > My honest question is - this is being discussed many times but where
> > > are we with this?
> > > Are all those users really suppose to get such a bad user experience?
> > > Why would you need a javascript
> > > on a login page?Is it so hard to create such page just formobile
> > > browsers?
>
> > > Is anybody handling this - I mean it is an obvious problem that we
> > > have for more than a year already.
>
> > > Any comments on this are highly appreciated.
>
> > --
> > Raffi Krikorian
> > Twitter Platform Teamhttp://twitter.com/raffi

[twitter-dev] Re: Send Cyrillic character (OAuth)

[Matt Sanford]

Hi Z-13,

  Short Answer: This looks like a bug in Tweetr [5].

  Long Answer: I'm not familiar with Tweetr, and my Action Script is a
bit rusty, but I took a look at the source of the updateStatus method
[1]. It looks like the code calls strEscape [2] (also defined in that
file [3]), which takes care of some common problems. What it does not
do is encode the string as UTF-8. It looks like some special handling
is needed in Action Script [4]. There is already a bug opened again
Tweetr for this [5].

Thanks;
  — Matt "Footnote" Sanford / @mzsanford
Twitter International

[1] - 
http://svn.swfjunkie.com/websvn/filedetails.php?repname=Tweetr&path=%2Ftrunk%2Fsrc%2Fcom%2Fswfjunkie%2Ftweetr%2FTweetr.as

[2] Calling code: vars.status = strEscape(status.substr(0,140));

[3] strEscape:

private function strEscape(value:String):String
{
if (_oAuth)
{
var str:String = escape(value);
str = str.replace(/\//g, "%2F");
str = str.replace(/\*/g, "%2A");
str = str.replace(/\+/g, "%2B");
str = str.replace(/@/g, "%40");
return str;
}
return value;
}

[4] - 
http://blog.dborisenko.com/en/2009/09/05/extended-utf-8-in-oauth-actionscript-library/

[5] - http://bugs.swfjunkie.com/task/30?project=3&status%5B0%5D=open


On May 10, 11:54 am, Z-13  wrote:
> How does this relate to AIR 1.5 and ActionScript 3?

[twitter-dev] Re: Send Cyrillic character (OAuth)

[Z-13]

Thank you for this method - 
http://destroytoday.com/blog/2010/02/encoding-for-oauth-using-as3/

[twitter-dev] Re: Send Cyrillic character (OAuth)

[Z-13]

I found solution!!
Here it is:
private function encodez(str:String):String {
return escape(unescape(encodeURIComponent(str))).replace(/%7E/g,
'~').replace(/@/g, '%40').replace(/\*/g, '%2A').replace(/\+/g,
'%2B').replace(/\//g, '%2F');
}

This is poblema with Cyrillic characters and UTF8 encoding.

[twitter-dev] Two apps one set of tolkens

[scott . a . herbert]

Just a quick questron, would two applications login in at the same time (via 
the same credencals, to the same account) cause twitter to have issues? 

I have a desktop client and background service that use the same database to 
tweet RSS feeds to twitter and am experances some strange issues which this may 
be the cause of...
Sent using BlackBerry® from Orange

[twitter-dev] Re: Send Cyrillic character (OAuth)

[Z-13]

Ok.
But, I don't know how work with this!

[twitter-dev] OAuth update on userstreams

[Mark McBride]

I deployed some OAuth fixes to betastream.twitter.com.  It should
handle spacing in the OAuth header better, and in general be more
stable.

   ---Mark

http://twitter.com/mccv

Re: [twitter-dev] Re: Someone managed to get me to follow them w/o my intervention (@johnnymatosj)

[John Meyer]

On 5/10/2010 3:48 PM, John Kalucki wrote:

That's unlikely.

Userstreams will tell you this in real time, FWIW. And you could
always poll the REST API against a trusted source. But, the workaround
is easy enough -- just unfollow the offending account...

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



Depending upon the number of people your account was signed up to follow 
against your wishes, could this by some chance fall under the churning 
clause if you unfollowed them at once?

Re: [twitter-dev] Re: Someone managed to get me to follow them w/o my intervention (@johnnymatosj)

[John Meyer]

On 5/10/2010 3:48 PM, John Kalucki wrote:

That's unlikely.

Userstreams will tell you this in real time, FWIW. And you could
always poll the REST API against a trusted source. But, the workaround
is easy enough -- just unfollow the offending account...

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




True; I could write up something.  But I was thinking more of people 
directly using the web site who aren't using third-party tools.  Not an 
API, mind you, just a notification.

Re: [twitter-dev] Re: Slow response to twitter updates for a third party app

[John Kalucki]

We're pretty sure that this isn't a connectivity issue. At least, it's
not *just* a connectivity issue.

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

On Mon, May 10, 2010 at 2:06 PM, mikawhite  wrote:
> delayed tweet:ping & traceroute
>
> 64 bytes from 128.242.240.61: icmp_seq=9 ttl=244 time=36.851 ms
>
> --- api.twitter.com ping statistics ---
> 10 packets transmitted, 8 packets received, 20% packet loss
> round-trip min/avg/max/stddev = 36.851/37.725/39.607/0.902 ms
>
>
>
> --
> traceroute to api.twitter.com (128.242.240.93), 64 hops max, 40 byte
> packets
>  1  10.0.1.1 (10.0.1.1)  1.337 ms  0.661 ms  0.678 ms
>  2  192.168.254.254 (192.168.254.254)  2.009 ms  1.609 ms  0.977 ms
>  3  dr01.moab.ut.frontiernet.net (74.40.8.109)  8.835 ms  7.860 ms
> 9.103 ms
>  4  74.40.41.233 (74.40.41.233)  14.145 ms  13.365 ms  14.576 ms
>  5  xe--0-2-0---0.cor01.slkc.ut.frontiernet.net (74.40.4.1)  13.959
> ms  14.443 ms  14.768 ms
>  6  ae1---0.cor02.plal.ca.frontiernet.net (74.40.5.61)  34.496 ms
> 32.226 ms  32.357 ms
>  7  ae1---0.cbr01.plal.ca.frontiernet.net (74.40.3.170)  60.735 ms
> 65.466 ms  35.187 ms
>  8  xe-0.paix.plalca01.us.bb.gin.ntt.net (198.32.176.14)  34.242 ms
> 36.110 ms  33.274 ms
>  9  xe-1-1-0.r21.mlpsca01.us.bb.gin.ntt.net (129.250.3.50)  30.914 ms
> 37.517 ms  30.781 ms
> 10  mg-2.c20.mlpsca01.us.da.verio.net (129.250.29.81)  34.434 ms
> 36.171 ms  34.288 ms
> 11  128.241.122.213 (128.241.122.213)  36.377 ms  34.334 ms  33.771 ms
> 12  * 128.241.122.213 (128.241.122.213)  34.956 ms !X *
> 13  * * *
> -
>

Re: [twitter-dev] Re: Someone managed to get me to follow them w/o my intervention (@johnnymatosj)

[John Kalucki]

That's unlikely.

Userstreams will tell you this in real time, FWIW. And you could
always poll the REST API against a trusted source. But, the workaround
is easy enough -- just unfollow the offending account...

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



On Mon, May 10, 2010 at 2:11 PM, John Meyer  wrote:
> On 5/10/2010 2:31 PM, jmathai wrote:
>>
>> So, I knew I wasn't hallucinating. Looks like this dude knew of the
>> 'accept username' bug before me :).
>>
>>
>
> Yep.
> On a suggestion request (for Twitter, not necessarily the API) would it be
> possible to e-mail people indicating that they have started following a
> particular Twitter User?  Just in case somebody figures out a way around
> this one.
>
>

Re: [twitter-dev] Need clearer explanation of using a single oauth token

[Taylor Singletary]

And you can get the Access Token (oauth_token and oauth_token_secret)
corresponding to your own user account for your own application by
navigating to one of your application detail pages at
http://dev.twitter.com/apps and selecting the "My Access Token" link on the
right-hand rail.

If you still have questions, I'll be happy to assist.

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod


On Mon, May 10, 2010 at 2:22 PM, Abraham Williams <4bra...@gmail.com> wrote:

> You need not only the oauth token and oauth secret for the user but the
> consumer key and secret.
>
> The consumer key and secret go on in "consumer =
> oauth.Consumer(key=CONSUMER_KEY, secret=CONSUMER_SECRET)"
>
> The users oauth token and secret replace "'abcdefg', 'hijklmnop'"
>
> Abraham
>
> On Mon, May 10, 2010 at 13:24, Glenn  wrote:
>
>> I'm looking at this snippet for Python:
>>
>> http://dev.twitter.com/pages/oauth_single_token#python
>>
>> and there are the key and secret parameters for oauth.Token. But the
>> page does not go into what those two are suppose to be. I tried using
>> oauth token and secret, as well as the username and password for the
>> twitter account to authorize under. Neither worked, because I got a
>> "Could not authenticate you." message once I tried my first API
>> lookup.
>>
>> Any advice?
>>
>
>
>
> --
> Abraham Williams | Developer for hire | http://abrah.am
> @abraham | http://projects.abrah.am | http://blog.abrah.am
> This email is: [ ] shareable [x] ask first [ ] private.
>

Re: [twitter-dev] Need clearer explanation of using a single oauth token

[Abraham Williams]

You need not only the oauth token and oauth secret for the user but the
consumer key and secret.

The consumer key and secret go on in "consumer =
oauth.Consumer(key=CONSUMER_KEY, secret=CONSUMER_SECRET)"

The users oauth token and secret replace "'abcdefg', 'hijklmnop'"

Abraham

On Mon, May 10, 2010 at 13:24, Glenn  wrote:

> I'm looking at this snippet for Python:
>
> http://dev.twitter.com/pages/oauth_single_token#python
>
> and there are the key and secret parameters for oauth.Token. But the
> page does not go into what those two are suppose to be. I tried using
> oauth token and secret, as well as the username and password for the
> twitter account to authorize under. Neither worked, because I got a
> "Could not authenticate you." message once I tried my first API
> lookup.
>
> Any advice?
>



-- 
Abraham Williams | Developer for hire | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.

Re: [twitter-dev] Re: Someone managed to get me to follow them w/o my intervention (@johnnymatosj)

[John Meyer]

On 5/10/2010 2:31 PM, jmathai wrote:

So, I knew I wasn't hallucinating. Looks like this dude knew of the
'accept username' bug before me :).




Yep.
On a suggestion request (for Twitter, not necessarily the API) would it 
be possible to e-mail people indicating that they have started following 
a particular Twitter User?  Just in case somebody figures out a way 
around this one.

[twitter-dev] Re: Slow response to twitter updates for a third party app

[mikawhite]

delayed tweet:ping & traceroute

64 bytes from 128.242.240.61: icmp_seq=9 ttl=244 time=36.851 ms

--- api.twitter.com ping statistics ---
10 packets transmitted, 8 packets received, 20% packet loss
round-trip min/avg/max/stddev = 36.851/37.725/39.607/0.902 ms



--
traceroute to api.twitter.com (128.242.240.93), 64 hops max, 40 byte
packets
 1  10.0.1.1 (10.0.1.1)  1.337 ms  0.661 ms  0.678 ms
 2  192.168.254.254 (192.168.254.254)  2.009 ms  1.609 ms  0.977 ms
 3  dr01.moab.ut.frontiernet.net (74.40.8.109)  8.835 ms  7.860 ms
9.103 ms
 4  74.40.41.233 (74.40.41.233)  14.145 ms  13.365 ms  14.576 ms
 5  xe--0-2-0---0.cor01.slkc.ut.frontiernet.net (74.40.4.1)  13.959
ms  14.443 ms  14.768 ms
 6  ae1---0.cor02.plal.ca.frontiernet.net (74.40.5.61)  34.496 ms
32.226 ms  32.357 ms
 7  ae1---0.cbr01.plal.ca.frontiernet.net (74.40.3.170)  60.735 ms
65.466 ms  35.187 ms
 8  xe-0.paix.plalca01.us.bb.gin.ntt.net (198.32.176.14)  34.242 ms
36.110 ms  33.274 ms
 9  xe-1-1-0.r21.mlpsca01.us.bb.gin.ntt.net (129.250.3.50)  30.914 ms
37.517 ms  30.781 ms
10  mg-2.c20.mlpsca01.us.da.verio.net (129.250.29.81)  34.434 ms
36.171 ms  34.288 ms
11  128.241.122.213 (128.241.122.213)  36.377 ms  34.334 ms  33.771 ms
12  * 128.241.122.213 (128.241.122.213)  34.956 ms !X *
13  * * *
-

[twitter-dev] Elevated API latency

[themattharris]

We've been getting reports from developers that the API has been
suffering from elevated latency, and in some cases have heard of
requests failing completely.

This is clearly a high priority issue, and is being actively
investigated by the team at Twitter HQ.

We'll post updates on Twitter http://twitter.com/twitterapi and to
this mailing list when we have them.

Thank you to all the developers who have provided us with examples and
datasets of where this has happened to them.

Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

[twitter-dev] What's better: Twitter4R or Twitter for Rails?

[garyz]

Switching to oAuth, and now's our chance to pick the best Twitter
library.  You thoughts/votes?

[twitter-dev] Re: Someone managed to get me to follow them w/o my intervention (@johnnymatosj)

[jmathai]

So, I knew I wasn't hallucinating. Looks like this dude knew of the
'accept username' bug before me :).

On Mar 19, 8:28 am, Abraham Williams <4bra...@gmail.com> wrote:
> He had just over 1000 followers a few days ago as 
> well:http://twitterholic.com/johnnymatosj
>
>
>
> On Thu, Mar 18, 2010 at 18:08, @kemeny_x  wrote:
> > Apparently he started tweeting only a few day ago and has over 10,000
> > followers... others are noticing also:
> >http://twitter.com/franklinpolanco/statuses/10588238989
>
> > On Mar 18, 6:32 pm, Andrew Badera  wrote:
> > > Ask them? I mean, this IS Twitter, right?
>
> > > ∞ 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 18, 2010 at 6:31 PM, jmathai  wrote:
>
> > > > On Mar 18, 2:14 pm, TJ Luoma  wrote:
> > > >> >http://search.twitter.com/search?q=johnnymatosj
>
> > > >> I used this:
>
> > > >>http://search.twitter.com/search?q=johnnymatosj+-from%3Ajohnnymatosj
>
> > > >> and saw two, including you.
>
> > > > I'm seeing 3 or 4...not a huge total but just wondering if there's a
> > > > security hole.  This guy has a lot of followers and isn't following a
> > > > ton of people.  So he's either genuinely interesting or gaming the
> > > > system.
>
> > > >> My guess? He's someone you were following who changed their
> > twittername.
>
> > > >> He joined back in September 2009. Anyone you've followed since then
> > > >> who's gone "missing"?
>
> > > > Possible.  I'm only following 13 people...don't remember who all.
> > > > This is a personal account I use only via a desktop client.  Could be
> > > > a switched username.  But I can't verify 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.
>
> --
> Abraham Williams | Community Advocate |http://abrah.am
> TwitterOAuth |http://github.com/abraham/twitteroauth
> This email is: [ ] shareable [x] ask first [ ] private.

[twitter-dev] Need clearer explanation of using a single oauth token

[Glenn]

I'm looking at this snippet for Python:

http://dev.twitter.com/pages/oauth_single_token#python

and there are the key and secret parameters for oauth.Token. But the
page does not go into what those two are suppose to be. I tried using
oauth token and secret, as well as the username and password for the
twitter account to authorize under. Neither worked, because I got a
"Could not authenticate you." message once I tried my first API
lookup.

Any advice?

Re: [twitter-dev] Current TwitterOAuth API won't display authorization page

[Abraham Williams]

It is because you are using the faster Sign in With Twitter endpoint where
if a user has already authorized your application they will automatically
redirect back to your site. If you want the user to always get prompted use
$connection->getAuthorizeURL($token, FALSE);

Abraham

On Sat, May 8, 2010 at 19:25, Jonathan  wrote:

> I'm having a puzzling (to me) problem with the TwitterOAuth API.
>
> I wrote and debugged code to get authorization to use a Twitter
> account, but I wasn't able to set the callback URL. With the help of
> people in this forum, I learned that I had an old beta copy of the
> API. Installing a current copy was supposed to solve the problem.
> Instead, it "broke" my program.
>
> Now, when I call click the link returned by getAuthorizeURL, I don't
> get the authorization page at all. I'm just redirected to the callback
> URL.
>
> (Yes, getAuthorizeURL is returning a URL on Twitter that looks about
> the same as it did before:
> https://twitter.com/oauth/authenticate?oauth_token=[a
> long string of gibberish].)
>
> What's happening here?
>



-- 
Abraham Williams | Developer for hire | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.

Re: [twitter-dev] random question

[John Meyer]

On 5/10/2010 1:40 PM, derek train wreck wrote:

Is it possible to have a user input their twitter status on a website
and submit it from the form box and have the text in the form box sent
directly to twitter?

i want to do it with this site:

http://www.ftwcontests.com/keane

is this possible?




http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update

Re: [twitter-dev] random question

[Abraham Williams]

Use the TweetBox: http://dev.twitter.com/anywhere

Abraham

On Mon, May 10, 2010 at 12:40, derek train wreck
wrote:

> Is it possible to have a user input their twitter status on a website
> and submit it from the form box and have the text in the form box sent
> directly to twitter?
>
> i want to do it with this site:
>
> http://www.ftwcontests.com/keane
>
> is this possible?
>
> thanks
>



-- 
Abraham Williams | Developer for hire | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.

[twitter-dev] random question

[derek train wreck]

Is it possible to have a user input their twitter status on a website
and submit it from the form box and have the text in the form box sent
directly to twitter?

i want to do it with this site:

http://www.ftwcontests.com/keane

is this possible?

thanks

[twitter-dev] double escaping issue

[heel99]

The twitter RSS feed for searches is double encoding special
characters

For example:
http://search.twitter.com/search.atom?q=+from%3AFSidorenko

The tweet says “Facebook’s Mark Zuckerberg…”

Twitter should be escaping the apostrophe like this: “Facebook's
Mark Zuckerberg”

But they are double-escaping the apostrophe, like this:
“Facebook's Mark Zuckerberg”.  They escape it once correctly
like above – but then escape it again – turning the & into an &.

Anyone know who to contact about this issue?

Actually - viewing the search results on the twitter's web site shows
the same issue:
http://search.twitter.com/search?ands=&from=FSidorenko&lang=all

Re: [twitter-dev] Re: Send Cyrillic character (OAuth)

[Taylor Singletary]

How does it relate?

You are trying to get your AIR/Actionscript code to generate proper OAuth
signatures that Twitter will understand. Instead of just writing code and
trying against Twitter to "see if it works", you can instead speed up the
process by starting with a vector that is known to produce valid signatures
-- which the oauth-dancer does, with the added benefit of heaps of debugging
information.

In this way, you would use the OAuth Dancer to attempt to make a resource
request or perform a step of the OAuth Dance, after entering in your
credentials. You will then see how every parameter got used in the request,
the signature base string generated, and the signatures and authorization
headers yielded by that process.

Then you do a bit of behavior-driven or test-driven development in your
AIR/Actionscript code, using exactly the same parameters that produced a
valid signature in the oauth-dancer, and keep iterating until you can
generate exactly the same signature base strings and signatures. Then you'll
move on to actually attempting to make calls against Twitter.

It's one tool, among many, that can help you create a "golden example" to
work towards, giving you a clearer path to knowing when your own code is
doing the right thing.

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod


On Mon, May 10, 2010 at 11:54 AM, Z-13  wrote:

> How does this relate to AIR 1.5 and ActionScript 3?
>

Re: [twitter-dev] Authenticated Search:Version 2.1.2

[Suresh Kalass]

But in code i can see Basic Authentication if passed to search method is
being stored as HttpRequest and passed on as request.Still not working.

Btw any other alternatives for it?
I need to have it at GAE for demo puropose.

Regards,
Suresh

On Mon, May 10, 2010 at 7:57 PM, Jonathan Reichhold <
jonathan.reichh...@gmail.com> wrote:

> You are also using api.twitter.com/v1/search when you should be using
> search.twitter.com/search
>
> The low rate limit is a side affect of the incorrect endpoint.
>
> Jonathan
>
> On Mon, May 10, 2010 at 4:32 AM, seshu  wrote:
>
>> Hi,
>> Twitter api supports maximum of 150 requests per hour for an
>> unauthenticated request from an ip.
>> So when i hosted it on GAE i was getting response code as 420.
>> Does basic authentication for the search api work? I can see we are
>> passing null for auth in Twitter.java.
>> I tried passing auth also.(I created an extra method). After creating
>> an authenticated instance of Twitter from Factory class by passing
>> userId/password.
>> But still seems it was not working as i was getting 420 status for
>> GAE. But was working fine locally.
>> Any workarounds for this? Or are there any gaps in my understandings?
>>
>> Best Regards,
>> Suresh
>>
>
>


-- 

Best Regards,
Suresh
9321811966/9765897825

[twitter-dev] Re: Send Cyrillic character (OAuth)

[Z-13]

How does this relate to AIR 1.5 and ActionScript 3?

Re: [twitter-dev] OAuth with Backend Calls? Am I just missing it?

[Abraham Williams]

Have a look at http://dev.twitter.com/pages/oauth_single_token

Abraham

On Mon, May 10, 2010 at 11:11, Pete  wrote:

> Ok so I'm trying to muddle through the myriad of article to glean some
> information about how this new OAuth REQUIREMENTS will work with
> backend applications.  I completely get how it works for user
> interaction, but what I fail to find anywhere is how it works with
> automated backend tools.
>
> Our web app doesn't interact with a user at all - we go do an
> aggregation into our own database and then present the data to users
> from there.  What I don't get is how our application running on a CRON
> with PHP would ever get OAuth credentials to do it's data mining job.
>
> Help?!?!
>
>


-- 
Abraham Williams | Developer for hire | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.

[twitter-dev] OAuth with Backend Calls? Am I just missing it?

[Pete]

Ok so I'm trying to muddle through the myriad of article to glean some
information about how this new OAuth REQUIREMENTS will work with
backend applications.  I completely get how it works for user
interaction, but what I fail to find anywhere is how it works with
automated backend tools.

Our web app doesn't interact with a user at all - we go do an
aggregation into our own database and then present the data to users
from there.  What I don't get is how our application running on a CRON
with PHP would ever get OAuth credentials to do it's data mining job.

Help?!?!

[twitter-dev] Re: The most shameful bug a site can have! Fix it quickly before it causes havoc dear Twitter

[nischalshetty]

All the best to your team. Hope things turn out well for everyone :)

-Nischal

On May 10, 9:42 pm, Mark McBride  wrote:
> We're aware and currently working on a fix.
>
>    ---Mark
>
> http://twitter.com/mccv
>
> On Mon, May 10, 2010 at 9:37 AM, nischalshetty
>
>
>
>  wrote:
> > Hi,
>
> > TechCrunch Europe reported the bug. I hope you fix it asap. It seems
> > to work! I'm extremely sorry, did not mean to exploit it, was just
> > trying to ascertain if it was true.
>
> > Once you are done fixing the bug, you will have the arduous task of
> > reversing all the follows that took place by exploiting this bug. If
> > you have an easy way to do that, well and fine.
>
> > One  thing I noticed, when you make someone follow you using the
> > exploited bug, the "new follower notification email" is never sent.
> > This might be of some help to you in identifying all those who
> > exploited the bug and reverse it.

Re: [twitter-dev] Followers / Following numbers.

[Nigel Legg]

Saw your tweet after sending email.  Sorry to disturb.

On 10 May 2010 18:10, Taylor Singletary wrote:

> Hi Nigel,
>
> This is related to a bug discovered this morning -- it will be resolved
> shortly. More information:
> http://status.twitter.com/post/587210796/follow-bug-discovered-remedied
>
> Thanks,
> Taylor
>
> On Mon, May 10, 2010 at 10:06 AM, Nigel Legg  wrote:
>
>> There appears to be a problem, these have disappeared??
>>
>
>

Re: [twitter-dev] Followers / Following numbers.

[Taylor Singletary]

Hi Nigel,

This is related to a bug discovered this morning -- it will be resolved
shortly. More information:
http://status.twitter.com/post/587210796/follow-bug-discovered-remedied

Thanks,
Taylor

On Mon, May 10, 2010 at 10:06 AM, Nigel Legg  wrote:

> There appears to be a problem, these have disappeared??
>

Re: [twitter-dev] The most shameful bug a site can have! Fix it quickly before it causes havoc dear Twitter

[Zac Bowling]

So weird. I KNEW something was up. I thought it was just stale memcache data
and it would expire.

I've been jacking around this script all week and what I was getting back
didn't make sense: http://gist.github.com/396262

So confused because things weren't adding up. I even sent out tweets asking
if someone else was actually following me or not (eg:
http://twitter.com/zbowling/status/13698520461 and
http://twitter.com/zbowling/status/13653464851 )


Zac Bowling
@zbowling


On Mon, May 10, 2010 at 9:42 AM, Mark McBride  wrote:

> We're aware and currently working on a fix.
>
>   ---Mark
>
> http://twitter.com/mccv
>
>
>
> On Mon, May 10, 2010 at 9:37 AM, nischalshetty
>  wrote:
> > Hi,
> >
> > TechCrunch Europe reported the bug. I hope you fix it asap. It seems
> > to work! I'm extremely sorry, did not mean to exploit it, was just
> > trying to ascertain if it was true.
> >
> > Once you are done fixing the bug, you will have the arduous task of
> > reversing all the follows that took place by exploiting this bug. If
> > you have an easy way to do that, well and fine.
> >
> > One  thing I noticed, when you make someone follow you using the
> > exploited bug, the "new follower notification email" is never sent.
> > This might be of some help to you in identifying all those who
> > exploited the bug and reverse it.
> >
> >
>

[twitter-dev] Issues with forced following, follower counts, following counts - resolved soon

[Taylor Singletary]

Hi Folks,

As you may have noticed, everyone's following and follower counts are
represented with a big fat zero right now. They aren't actually zero, we
just changed some wiring around to halt a nasty bug that's flowing around. A
fix for that bug and the restoration of following and follower counts will
deploy shortly. Tweets are flowing normally.

>From our status.twitter.com blog post:

"We identified and resolved a bug that permitted a user to “force” other
users to follow them. We’re now working to rollback all abuse of the bug
that took place. Follower/following numbers are currently at 0; we’re aware
and this too should shortly be resolved."

http://status.twitter.com/post/587210796/follow-bug-discovered-remedied

Thank you everyone for your patience as we work this one out.

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod

Re: [twitter-dev] Followers / Following numbers.

[John Kalucki]

Working on it.

On Mon, May 10, 2010 at 10:06 AM, Nigel Legg  wrote:
> There appears to be a problem, these have disappeared??
>

[twitter-dev] Followers / Following numbers.

[Nigel Legg]

There appears to be a problem, these have disappeared??

[twitter-dev] Re: TweetDeck and xAuth

[Brian Sutorius]

I can't find a ticket under your email address requesting xAuth. Could
you please follow up with me directly? I'll be happy to review your
request.
Brian Sutorius

On May 10, 3:28 am, Steve Loft  wrote:
> Does anyone know how long it should take to get xAuth privilege? It's
> just that I applied nearly a week ago for access for my desktop app,
> and time is running out. It looks like I am going to have an app which
> doesn't work with Twitter come the end of June.

[twitter-dev] Re: Slow response to twitter updates for a third party app

[mikawhite]

John,

Chart of failed pings originating in Moab, Utah...
http://tweetprobe.tumblr.com/post/587169206

Re: [twitter-dev] How would I get remaing hits using OAuth.

[Abraham Williams]

Look at your request
"/account/rate_limit_statusaccount/verify_credentials.json".
Notice how rate_limit_status and verify_credentials are both jammed
together.

It also looks like you are using an older version of TwitterOAuth. The
newest version uses https://api.twitter.com/1/ as the host which gives you a
rate limit of 350/hour instead of 150/hour.

To get the rate_limit_status in the newest version call
$connection->get('account/rate_limit_status');

Abraham

On Mon, May 10, 2010 at 07:23, Rushikesh Bhanage wrote:

>
>   Hi there,
> * About my app* - my app deals with showing user his followers
> information. So I  need to check each follower to show result. Everything is
> going properly except one. While doing this I need to check API remaining
> hits of account.(whitelisted a/c.)
>  Now what I want is, if my app is using calls of particular a/c then I
> should get remaining hits of that a/c using OAuth.
>  I am studying Abraham's code on github in that it gives particular
> user's info, but when I go for rate limit status url for Host like as:
> public $host = "http://twitter.com/account/rate_limit_status";;
> it gives result as:
>   stdClass Object
> (
> [request] =>
> /account/rate_limit_statusaccount/verify_credentials.json?oauth_consumer_key=bTeyT1WTohdf7IT4JZ4iYg&oauth_nonce=8e7f694db22fead19d8833ab67430ca6&oauth_signature=9BTlNg%2BePdvIENSxqd%2B6quZ5bms%3D&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1273497259&oauth_token=113883944-6A9NCG9DCkZ0DpJnHzBxZCxPEcezD2Pmn32pmc5O&oauth_version=1.0
> [error] => Not found
> )
>
> Am I going wrong way? Can you suggest me the right one?
>
>  Thank you in advance.
>
>


-- 
Abraham Williams | Developer for hire | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.

Re: [twitter-dev] The most shameful bug a site can have! Fix it quickly before it causes havoc dear Twitter

[Mark McBride]

We're aware and currently working on a fix.

   ---Mark

http://twitter.com/mccv



On Mon, May 10, 2010 at 9:37 AM, nischalshetty
 wrote:
> Hi,
>
> TechCrunch Europe reported the bug. I hope you fix it asap. It seems
> to work! I'm extremely sorry, did not mean to exploit it, was just
> trying to ascertain if it was true.
>
> Once you are done fixing the bug, you will have the arduous task of
> reversing all the follows that took place by exploiting this bug. If
> you have an easy way to do that, well and fine.
>
> One  thing I noticed, when you make someone follow you using the
> exploited bug, the "new follower notification email" is never sent.
> This might be of some help to you in identifying all those who
> exploited the bug and reverse it.
>
>

[twitter-dev] The most shameful bug a site can have! Fix it quickly before it causes havoc dear Twitter

[nischalshetty]

Hi,

TechCrunch Europe reported the bug. I hope you fix it asap. It seems
to work! I'm extremely sorry, did not mean to exploit it, was just
trying to ascertain if it was true.

Once you are done fixing the bug, you will have the arduous task of
reversing all the follows that took place by exploiting this bug. If
you have an easy way to do that, well and fine.

One  thing I noticed, when you make someone follow you using the
exploited bug, the "new follower notification email" is never sent.
This might be of some help to you in identifying all those who
exploited the bug and reverse it.

Re: [twitter-dev] Re: Send Cyrillic character (OAuth)

[Patrick Kennedy]

Z-13,

Don't forget to do rake db:migrate to build the tables in Sqlite.

"Agile Web Development with Rails" has the skinny to install rails for
Mac, Linux, or Windows, if you need more solid material.


On Mon, May 10, 2010 at 8:23 PM, Taylor Singletary
 wrote:
> Hi Z-13,
> It's a Ruby on Rails application, though it doesn't require too much
> familiarity with Ruby on Rails to get up and running with it.
> On a Mac or Linux environment, it should be as easy as git cloning the
> repository ( http://learn.github.com/p/intro.html ) then trying to start the
> server from within the directory that unpacks with "script/server" -- if
> that command succeeds, you then point your web browser to
> http://localhost:3000
> If it doesn't succeed, then you may need to install some dependencies.
> Sqlite3 is required along with Ruby 1.8.6 and Rubygems. Almost all other
> dependencies should be included with the archive, though if you install
> rails with Rubygems it will ensure that you have any missing dependencies.
> Taylor Singletary
> Developer Advocate, Twitter
> http://twitter.com/episod
>
>
> On Sun, May 9, 2010 at 10:47 AM, Z-13  wrote:
>>
>> How use your "OAuth Dancer tool"?
>>
>> Thank you.
>
>

Re: [twitter-dev] Authenticated Search:Version 2.1.2

[Jonathan Reichhold]

You are also using api.twitter.com/v1/search when you should be using
search.twitter.com/search

The low rate limit is a side affect of the incorrect endpoint.

Jonathan

On Mon, May 10, 2010 at 4:32 AM, seshu  wrote:

> Hi,
> Twitter api supports maximum of 150 requests per hour for an
> unauthenticated request from an ip.
> So when i hosted it on GAE i was getting response code as 420.
> Does basic authentication for the search api work? I can see we are
> passing null for auth in Twitter.java.
> I tried passing auth also.(I created an extra method). After creating
> an authenticated instance of Twitter from Factory class by passing
> userId/password.
> But still seems it was not working as i was getting 420 status for
> GAE. But was working fine locally.
> Any workarounds for this? Or are there any gaps in my understandings?
>
> Best Regards,
> Suresh
>

[twitter-dev] How would I get remaing hits using OAuth.

[Rushikesh Bhanage]

  Hi there,
* About my app* - my app deals with showing user his followers
information. So I  need to check each follower to show result. Everything is
going properly except one. While doing this I need to check API remaining
hits of account.(whitelisted a/c.)
 Now what I want is, if my app is using calls of particular a/c then I
should get remaining hits of that a/c using OAuth.
 I am studying Abraham's code on github in that it gives particular
user's info, but when I go for rate limit status url for Host like as:
public $host = "http://twitter.com/account/rate_limit_status";;
it gives result as:
  stdClass Object
(
[request] =>
/account/rate_limit_statusaccount/verify_credentials.json?oauth_consumer_key=bTeyT1WTohdf7IT4JZ4iYg&oauth_nonce=8e7f694db22fead19d8833ab67430ca6&oauth_signature=9BTlNg%2BePdvIENSxqd%2B6quZ5bms%3D&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1273497259&oauth_token=113883944-6A9NCG9DCkZ0DpJnHzBxZCxPEcezD2Pmn32pmc5O&oauth_version=1.0
[error] => Not found
)

Am I going wrong way? Can you suggest me the right one?

 Thank you in advance.

Re: [twitter-dev] How can I know why my app fails OAuth?

[Morr. Liang]

This really helpful,thanks~[?]

2010/5/10 Taylor Singletary 

> Hi,
>
> We're readying a revision of our OAuth implementation that will give more
> feedback on what went wrong -- including showing the signature base string
> generated on our side when there's a signature mis-match.
>
> The best thing you can do to solve your OAuth woes is to forget about
> actually making HTTP calls to twitter.com for a bit. The documentation at
> http://dev.twitter.com/pages/auth includes detailed signature base
> strings, signatures, and parameters -- including consumer keys and secrets
> -- that give you everything you need to make a matching implementation
> without even issuing a single HTTP request.
>
> Use those examples as "golden examples" -- take the inputs like
> oauth_nonce, oauth_timestamp, the resource, the method, the consumer key,
> the consumer secret, etc. and try to recreate the signatures exactly as they
> are calculated in the documentation. I wouldn't recommend moving on to using
> real, live timestamp and nonce values (and your own keys) until you can
> reliably reproduce all of the signatures in that documentation. Once you're
> able to repeat the signatures verbatim, you can have confidence that your
> OAuth signature generation steps are kosher and then move on to actually
> trying real calls.
>
> Taylor Singletary
> Developer Advocate, Twitter
> http://twitter.com/episod
>
>
> On Sun, May 9, 2010 at 12:29 AM, Morr. Liang  wrote:
>
>> I'm trying to create an twitter client using c++.Since it's written in
>> c++,not much infomation I found.
>>
>> When I try to request a token,it kept saying "Failed to validate oauth
>> signature and token".
>> I don't know where I went wrong.So I cannot fix it.
>> I just want more details.
>>
>> One of webs in my country supports oauth.I try using oauth on it.At
>> first,I failed.But at least it provides me infomations like "signature
>> doesn't match,expected:xx,received:oo".So I finally figure out
>> where I went wrong.
>>
>> But twitter provides so little info.I don't even know wether the
>> timestamp or the signature is wrong or some other stuff cause the
>> problem.
>>
>> So,how can I retreive more details?
>>
>
>
<<330.gif>>

[twitter-dev] Re: Malformed XML in some Atom feeds...

[Claudia A. V. Callegari]

Thank you, I am going to wait.

Thanks
Claudia Antonini  Vitiello  Callegari
São Paulo -  Brasil

On 10 maio, 10:46, Taylor Singletary 
wrote:
> Hi Claudia,
>
> Looks like I was mistaken and this bugfix hasn't hit the server yet. It
> should go out sometime early this week.
>
> Taylor Singletary
> Developer Advocate, Twitterhttp://twitter.com/episod
>
> On Mon, May 10, 2010 at 4:15 AM, Claudia A. V. Callegari <
>
> claudia.avcalleg...@gmail.com> wrote:
> > Hello !
>
> > Thanks for the feedback.
>
> > See, for example, the url that my application is using:
>
> >http://twitter.com/statuses/user_timeline.atom?page=1&user_id=5421011...
>
> > Thanks
> > Claudia Antonini  Vitiello  Callegari
> > São Paulo -  Brasil
>
> > On 7 maio, 11:00, Taylor Singletary 
> > wrote:
> > > Hi Claudia,
>
> > > Could you paste a little bit of the invalid ATOM feed you are still
> > > receiving it? This problem should be fixed now, but it's possible that
> > some
> > > persistent cache elements may still have the unencoded ampersand within
> > > them.
>
> > > Taylor Singletary
> > > Developer Advocate, Twitterhttp://twitter.com/episod
>
> > > On Fri, May 7, 2010 at 3:57 AM, Claudia A. V. Callegari <
>
> > > claudia.avcalleg...@gmail.com> wrote:
> > > > Hello!
>
> > > > Sorry for my English.
> > > > I'm also having the same problem, has agumar forecast for this
> > > > problem?
>
> > > > Thanks
> > > > Claudia Antonini  Vitiello  Callegari
> > > > São Paulo -  Brasil
>
> > > > On 4 maio, 12:33, Taylor Singletary 
> > > > wrote:
> > > > > Hi Brandon,
>
> > > > > Thanks for the bug report. We'll work on getting this fixed quickly.
>
> > > > > Thanks!
>
> > > > > Taylor Singletary
> > > > > Developer Advocate, Twitterhttp://twitter.com/episod
>
> > > > > On Tue, May 4, 2010 at 7:54 AM, Brandon Stone 
> > wrote:
> > > > > > One very popular Twitter list is Scoble's Tech News Brands list:
>
> >http://api.twitter.com/1/Scobleizer/lists/tech-news-brands/statuses.a.
> > > > ..
>
> > > > > > I've got a program that's been watching this feed for a while now.
> > > >  Just
> > > > > > yesterday I started getting some XML parsing errors.  I can create
> > a
> > > > hack to
> > > > > > make this work again on my end, but it's definitely best for
> > Twitter to
> > > > make
> > > > > > sure their XML is well-formed.
>
> > > > > > Here's what feed validator says:
>
> >http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fapi.twitter.c.
> > > > ..
>
> > > > > >> Sorry
>
> > > > > >> This feed does not validate.
>
> > > > > >> line 482<
> > > >http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fapi.twitter.c..
> > .>,
> > > > > >> column 73: XML parsing error: :482:73: not well-formed
> > > > (invalid
> > > > > >> token) [help <
> >http://validator.w3.org/feed/docs/error/SAXError.html>]
>
> > > > > >> http://www.google.com/support/youtube/bin/answer.py?hl=en&answer=16...
>
> > > > > > It looks like whenever a  of "Google" appears, it
> > > > breaks
> > > > > > the XML because of the ampersand in the URL:
>
> > > > > > 
> > > > > >> http://www.google.com/support/youtube/bin/answer.py?hl=en&answer=164577
> > "
> > > > > >> rel="nofollow">Google
> > > > > >> 
>
> > > > > > If the ampersand is fixed, I'm guessing things will be happy again.
>
> > > > > > I hope I'm sending this to the right place.  Not sure where else to
> > > > send
> > > > > > it.
>
> > > > > > Thanks!
>
> > > > > > -Brandon
>
> > > > > > --
> > > > > > Brandon Stone
> > > > > >http://brandonstone.com
> > > > > >http://twitter.com/LBStone

Re: [twitter-dev] what's wrong with my xAuth code ???

[Taylor Singletary]

Hi Mostafa,

What environment are you trying to execute this code in? Javascript in most
use cases is not an appropriate vehicle for performing OAuth operations --
unless you "are" the web browser or another kind of application development
environment in which Javascript is a bit more secure.

That said, I helped a developer through a Javascript OAuth implementation
last week and after much bashing of the head against the desk, it was found
that the HMAC_SHA1 algorithm being used was not doing the right thing and
using the wrong kind of padding.

Are you able to reproduce the signatures (given exactly the same inputs) as
detailed on http://dev.twitter.com/pages/auth ?

Have you traced the request to ensure that your authorization header is
actually being sent properly? How are you avoiding cross-domain issues?

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod


On Thu, May 6, 2010 at 5:13 PM, mostafa farghaly wrote:

> every time i get "failed to validate outh token and signature" :(
> here's my simple code
>
>var username = "username",
>password = "password",
>url= "
> https://api.twitter.com/oauth/access_token";,
>key = "key",
>timestamp = +new Date,
>nonce = "thisismynoncce" + timestamp;
>
>var access_token = "oauth_consumer_key=" + key +
>"&oauth_nonce=" + nonce +
>"&oauth_signature_method=HMAC_SHA1" +
>"&oauth_timestamp=" + timestamp +
>"&oauth_version=1.0" +
>"&x_auth_mode=client_auth" +
>"&x_auth_password=" + password +
>"&x_auth_username=" + username;
>
>var base_string = "POST&" + encodeURIComponent(url)
> + "&" +
> encodeURIComponent(access_token);
>
>var oauth_signature = b64_hmac_sha1("token_secret&",
> base_string);
>
>
>var auth_header = 'OAuth oauth_nonce="' + nonce +
> '"' +
>', oauth_signature_method="HMAC-SHA1"' +
>', oauth_timestamp="' + timestamp + '"' +
>', oauth_consumer_key="' + key + '"' +
>', oauth_signature="' + oauth_signature + '"' +
>', oauth_version="1.0"';
>
>
>  $.ajax({
>url:url,
>method: "POST",
>data: {
>x_auth_username: username,
>x_auth_password: password,
>x_auth_mode: "client_auth"
>},
>beforeSend: function(xhr){
>
>  xhr.setRequestHeader("Authorization", auth_header);
>},
>success: function(data){
>alert(data);
>},
>error: function(xhr){
>alert(xhr.responseText);
>}
>})
>

Re: [twitter-dev] How can I know why my app fails OAuth?

[Taylor Singletary]

Hi,

We're readying a revision of our OAuth implementation that will give more
feedback on what went wrong -- including showing the signature base string
generated on our side when there's a signature mis-match.

The best thing you can do to solve your OAuth woes is to forget about
actually making HTTP calls to twitter.com for a bit. The documentation at
http://dev.twitter.com/pages/auth includes detailed signature base strings,
signatures, and parameters -- including consumer keys and secrets -- that
give you everything you need to make a matching implementation without even
issuing a single HTTP request.

Use those examples as "golden examples" -- take the inputs like oauth_nonce,
oauth_timestamp, the resource, the method, the consumer key, the consumer
secret, etc. and try to recreate the signatures exactly as they are
calculated in the documentation. I wouldn't recommend moving on to using
real, live timestamp and nonce values (and your own keys) until you can
reliably reproduce all of the signatures in that documentation. Once you're
able to repeat the signatures verbatim, you can have confidence that your
OAuth signature generation steps are kosher and then move on to actually
trying real calls.

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod


On Sun, May 9, 2010 at 12:29 AM, Morr. Liang  wrote:

> I'm trying to create an twitter client using c++.Since it's written in
> c++,not much infomation I found.
>
> When I try to request a token,it kept saying "Failed to validate oauth
> signature and token".
> I don't know where I went wrong.So I cannot fix it.
> I just want more details.
>
> One of webs in my country supports oauth.I try using oauth on it.At
> first,I failed.But at least it provides me infomations like "signature
> doesn't match,expected:xx,received:oo".So I finally figure out
> where I went wrong.
>
> But twitter provides so little info.I don't even know wether the
> timestamp or the signature is wrong or some other stuff cause the
> problem.
>
> So,how can I retreive more details?
>

[twitter-dev] Re: Slow response to twitter updates for a third party app

[@epc]

I’m also seeing a ~5 second delay in responses to requests for
http://api.twitter.com/1/statuses/user_timeline.xml.
It’s consistently 5-7 seconds, but appears to happen both before the
response is sent as well as midway, it sort of feels like both a
timeout waiting for something to happen as well as a buffering
thing.

I can send a tcpdump report & additional details offlist.
--
-ed costello

Re: [twitter-dev] Re: Tweeting from PHP backed will also require OAuth in the upcoming changes?

[Taylor Singletary]

Hi Eric,

The oauth_single_token isn't really a feature -- it's just a demonstration
of how you would go about it if that was your use case.

The usage of a stored access token is the same in most implementations,
whether you got that single access token through the feature on
dev.twitter.com or you got the access token by performing the OAuth token
negotiation dance -- with most OAuth libraries, you still instantiate an
access token object the same way -- you might be pulling the token from a
database in context to a user using your application instead of having it
hard coded.

For those that do have a single-user use-case, usually people who've written
an application mainly for their own research purposes, it's a quick and easy
way to skip over the hardest part of implementing OAuth and instead skip
right to the part where you're making resource requests.

But the pattern is the same regardless of how you got the access tokens.
Some libraries might obfuscate or simplify the process, but under the hood
they are doing very similar operations.

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod


On Sun, May 9, 2010 at 11:58 AM, Eric  wrote:

> Is the point of oauth_single_token that you can only work with a
> single account? Meaning if I have a feature on my site, I can't use
> this library to interact with the users accounts, I can only use this
> library to work with my own, or one account?
>
> Much appreciated!
>
> On May 3, 2:35 pm, Abraham Williams <4bra...@gmail.com> wrote:
> > You can checkout this page describing using a script to post to a single
> > Twitter account:http://dev.twitter.com/pages/oauth_single_token
> >
> > One of the examples is for my PHP library:
> http://github.com/abraham/twitteroauth
> >
> > Abraham
> >
> >
> >
> > On Mon, May 3, 2010 at 13:04, YCBM  wrote:
> > > Hi Paul,
> >
> > > Posting status updates using Basic Auth like that won't work any more
> > > after 6/30.  You'll need to use a PHP oAuth class (there are a few of
> > > them athttp://dev.twitter.com/pages/oauth_libraries#php) as well as
> > > register an oAuth app.
> >
> > > Best,
> > > Y
> >
> > > On May 3, 3:17 pm, "Paul A."  wrote:
> > > > Hi guys,
> >
> > > > Quick question that "hunts" me and can't find an answer.
> >
> > > > I'm using this line of code to post  tweets to my account direclty
> > > > from my website
> >
> > > >  $host = "http://twitter.com/statuses/update.xml?
> > > > status=".urlencode(stripslashes(urldecode($message)))
> > > > and posting it with curl with my user/password
> >
> > > > Will this still going to work after Twitter  upcoming June
> requirement
> > > > for Oauth. It's unclear to me.
> >
> > > > Thanks, Paul
> >
> > --
> > Abraham Williams | Developer for hire |http://abrah.am
> > @abraham |http://projects.abrah.am|http://blog.abrah.am
> > This email is: [ ] shareable [x] ask first [ ] private.
>

Re: [twitter-dev] Re: Malformed XML in some Atom feeds...

[Taylor Singletary]

Hi Claudia,

Looks like I was mistaken and this bugfix hasn't hit the server yet. It
should go out sometime early this week.

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod


On Mon, May 10, 2010 at 4:15 AM, Claudia A. V. Callegari <
claudia.avcalleg...@gmail.com> wrote:

> Hello !
>
> Thanks for the feedback.
>
> See, for example, the url that my application is using:
>
>
> http://twitter.com/statuses/user_timeline.atom?page=1&user_id=54210117&count=200&since_id=12941651260
>
>
> Thanks
> Claudia Antonini  Vitiello  Callegari
> São Paulo -  Brasil
>
>
> On 7 maio, 11:00, Taylor Singletary 
> wrote:
> > Hi Claudia,
> >
> > Could you paste a little bit of the invalid ATOM feed you are still
> > receiving it? This problem should be fixed now, but it's possible that
> some
> > persistent cache elements may still have the unencoded ampersand within
> > them.
> >
> > Taylor Singletary
> > Developer Advocate, Twitterhttp://twitter.com/episod
> >
> > On Fri, May 7, 2010 at 3:57 AM, Claudia A. V. Callegari <
> >
> > claudia.avcalleg...@gmail.com> wrote:
> > > Hello!
> >
> > > Sorry for my English.
> > > I'm also having the same problem, has agumar forecast for this
> > > problem?
> >
> > > Thanks
> > > Claudia Antonini  Vitiello  Callegari
> > > São Paulo -  Brasil
> >
> > > On 4 maio, 12:33, Taylor Singletary 
> > > wrote:
> > > > Hi Brandon,
> >
> > > > Thanks for the bug report. We'll work on getting this fixed quickly.
> >
> > > > Thanks!
> >
> > > > Taylor Singletary
> > > > Developer Advocate, Twitterhttp://twitter.com/episod
> >
> > > > On Tue, May 4, 2010 at 7:54 AM, Brandon Stone 
> wrote:
> > > > > One very popular Twitter list is Scoble's Tech News Brands list:
> >
> > > > >
> http://api.twitter.com/1/Scobleizer/lists/tech-news-brands/statuses.a.
> > > ..
> >
> > > > > I've got a program that's been watching this feed for a while now.
> > >  Just
> > > > > yesterday I started getting some XML parsing errors.  I can create
> a
> > > hack to
> > > > > make this work again on my end, but it's definitely best for
> Twitter to
> > > make
> > > > > sure their XML is well-formed.
> >
> > > > > Here's what feed validator says:
> >
> > > > >
> http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fapi.twitter.c.
> > > ..
> >
> > > > >> Sorry
> >
> > > > >> This feed does not validate.
> >
> > > > >> line 482<
> > >http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fapi.twitter.c..
> .>,
> > > > >> column 73: XML parsing error: :482:73: not well-formed
> > > (invalid
> > > > >> token) [help <
> http://validator.w3.org/feed/docs/error/SAXError.html>]
> >
> > > > >> http://www.google.com/support/youtube/bin/answer.py?hl=en&answer=16...
> >
> > > > > It looks like whenever a  of "Google" appears, it
> > > breaks
> > > > > the XML because of the ampersand in the URL:
> >
> > > > > 
> > > > >> http://www.google.com/support/youtube/bin/answer.py?hl=en&answer=164577
> "
> > > > >> rel="nofollow">Google
> > > > >> 
> >
> > > > > If the ampersand is fixed, I'm guessing things will be happy again.
> >
> > > > > I hope I'm sending this to the right place.  Not sure where else to
> > > send
> > > > > it.
> >
> > > > > Thanks!
> >
> > > > > -Brandon
> >
> > > > > --
> > > > > Brandon Stone
> > > > >http://brandonstone.com
> > > > >http://twitter.com/LBStone
>

Re: [twitter-dev] Authenticated Search:Version 2.1.2

[Taylor Singletary]

Hi Seshu,

The Search API doesn't use authentication right now. Much of Google App
Engine's traffic comes to Twitter from the same IP address, such that other
developers running applications on Google AppEngine might be using the limit
up before your requests go out.

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod


On Mon, May 10, 2010 at 4:32 AM, seshu  wrote:

> Hi,
> Twitter api supports maximum of 150 requests per hour for an
> unauthenticated request from an ip.
> So when i hosted it on GAE i was getting response code as 420.
> Does basic authentication for the search api work? I can see we are
> passing null for auth in Twitter.java.
> I tried passing auth also.(I created an extra method). After creating
> an authenticated instance of Twitter from Factory class by passing
> userId/password.
> But still seems it was not working as i was getting 420 status for
> GAE. But was working fine locally.
> Any workarounds for this? Or are there any gaps in my understandings?
>
> Best Regards,
> Suresh
>

Re: [twitter-dev] Re: Send Cyrillic character (OAuth)

[Taylor Singletary]

Hi Z-13,

It's a Ruby on Rails application, though it doesn't require too much
familiarity with Ruby on Rails to get up and running with it.

On a Mac or Linux environment, it should be as easy as git cloning the
repository ( http://learn.github.com/p/intro.html ) then trying to start the
server from within the directory that unpacks with "script/server" -- if
that command succeeds, you then point your web browser to
http://localhost:3000

If it doesn't succeed, then you may need to install some dependencies.
Sqlite3 is required along with Ruby 1.8.6 and Rubygems. Almost all other
dependencies should be included with the archive, though if you install
rails with Rubygems it will ensure that you have any missing dependencies.

Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod


On Sun, May 9, 2010 at 10:47 AM, Z-13  wrote:

> How use your "OAuth Dancer tool"?
>
> Thank you.
>

[twitter-dev] Authenticated Search:Version 2.1.2

[seshu]

Hi,
Twitter api supports maximum of 150 requests per hour for an
unauthenticated request from an ip.
So when i hosted it on GAE i was getting response code as 420.
Does basic authentication for the search api work? I can see we are
passing null for auth in Twitter.java.
I tried passing auth also.(I created an extra method). After creating
an authenticated instance of Twitter from Factory class by passing
userId/password.
But still seems it was not working as i was getting 420 status for
GAE. But was working fine locally.
Any workarounds for this? Or are there any gaps in my understandings?

Best Regards,
Suresh

[twitter-dev] Re: TweetDeck and xAuth

[Steve Loft]

Does anyone know how long it should take to get xAuth privilege? It's
just that I applied nearly a week ago for access for my desktop app,
and time is running out. It looks like I am going to have an app which
doesn't work with Twitter come the end of June.

[twitter-dev] Re: Using @anywhere and the Twitter Search Widget

[Elenor]

I get this as well. It happens in Safari (4.0.5) and Chrome (5.0.375).
It's not just with the search widget though, it happens in
http://platform.twitter.com/anywhere.js when you call twttr.anywhere()
which uses https://api.twitter.com/xd_receiver.html

I've been getting it with the hovercards, although it doesn't stop
them from working.

You can also see it happening here: http://dev.twitter.com/anywhere/begin


On Apr 23, 4:31 pm, Dustin Diaz  wrote:
> What is the url of your site?
>
> --
> Subscription 
> settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en

[twitter-dev] Javascript API Help

[Rishit]

I'm building a Google Wave Gadget (which is very similar to iGoogle
Gadget) where i need Twitter connectivity.
I want to update to Twitter my Twitter Status and then get Replies to
that and process it.
I am writing the Gadget in Javascript.
API documentation Gives URL and Parameters
I tried the JS libraries but they work on platforms: AIR,WebOS (not in
browser like i want)

What i'd love to hav is a Step by Step procedure how to update status
using Javascript.

eg.
1)Create an Object 'Twitter t={}'.
2)Assign parameters 't.status = msg'
3)How to Call Post method
4)Done

Any help will b appreciated. Thnx
- Twitter Rocks \m/

[twitter-dev] Re: Malformed XML in some Atom feeds...

[Claudia A. V. Callegari]

Hello !

Thanks for the feedback.

See, for example, the url that my application is using:

http://twitter.com/statuses/user_timeline.atom?page=1&user_id=54210117&count=200&since_id=12941651260


Thanks
Claudia Antonini  Vitiello  Callegari
São Paulo -  Brasil


On 7 maio, 11:00, Taylor Singletary 
wrote:
> Hi Claudia,
>
> Could you paste a little bit of the invalid ATOM feed you are still
> receiving it? This problem should be fixed now, but it's possible that some
> persistent cache elements may still have the unencoded ampersand within
> them.
>
> Taylor Singletary
> Developer Advocate, Twitterhttp://twitter.com/episod
>
> On Fri, May 7, 2010 at 3:57 AM, Claudia A. V. Callegari <
>
> claudia.avcalleg...@gmail.com> wrote:
> > Hello!
>
> > Sorry for my English.
> > I'm also having the same problem, has agumar forecast for this
> > problem?
>
> > Thanks
> > Claudia Antonini  Vitiello  Callegari
> > São Paulo -  Brasil
>
> > On 4 maio, 12:33, Taylor Singletary 
> > wrote:
> > > Hi Brandon,
>
> > > Thanks for the bug report. We'll work on getting this fixed quickly.
>
> > > Thanks!
>
> > > Taylor Singletary
> > > Developer Advocate, Twitterhttp://twitter.com/episod
>
> > > On Tue, May 4, 2010 at 7:54 AM, Brandon Stone  wrote:
> > > > One very popular Twitter list is Scoble's Tech News Brands list:
>
> > > >http://api.twitter.com/1/Scobleizer/lists/tech-news-brands/statuses.a.
> > ..
>
> > > > I've got a program that's been watching this feed for a while now.
> >  Just
> > > > yesterday I started getting some XML parsing errors.  I can create a
> > hack to
> > > > make this work again on my end, but it's definitely best for Twitter to
> > make
> > > > sure their XML is well-formed.
>
> > > > Here's what feed validator says:
>
> > > >http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fapi.twitter.c.
> > ..
>
> > > >> Sorry
>
> > > >> This feed does not validate.
>
> > > >> line 482<
> >http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fapi.twitter.c...>,
> > > >> column 73: XML parsing error: :482:73: not well-formed
> > (invalid
> > > >> token) [help ]
>
> > > >> http://www.google.com/support/youtube/bin/answer.py?hl=en&answer=16...
>
> > > > It looks like whenever a  of "Google" appears, it
> > breaks
> > > > the XML because of the ampersand in the URL:
>
> > > > 
> > > >> http://www.google.com/support/youtube/bin/answer.py?hl=en&answer=164577";
> > > >> rel="nofollow">Google
> > > >> 
>
> > > > If the ampersand is fixed, I'm guessing things will be happy again.
>
> > > > I hope I'm sending this to the right place.  Not sure where else to
> > send
> > > > it.
>
> > > > Thanks!
>
> > > > -Brandon
>
> > > > --
> > > > Brandon Stone
> > > >http://brandonstone.com
> > > >http://twitter.com/LBStone

Re: [twitter-dev] Re: Why have I recieved a HTTP 601 Response.

[Raffi Krikorian]

i'm not sure - how long do you see the connection hang before the disconnect
occurs?  how frequently do you see this issue?  where is your proxy
geographically located?

On Mon, May 10, 2010 at 4:34 AM, Asura  wrote:

> hi,
>
> Actually, I'm connecting through a proxy.
> But, they saied that "we just send HTTP 601 message cause twitter
> disconnects".
>
> when do you disconnect with client while authorize?
>
> your kind comment would be much appreciated.
>
> Thanks.
> Regards,
> H.
>
>
>
> On May 7, 2:42 pm, Raffi Krikorian  wrote:
> > hi!
> >
> > are you connecting through a proxy or some other intermediary?  that
> failure
> > doesn't seem like it came from the twitter stack.
> >
> >
> >
> >
> >
> > On Fri, May 7, 2010 at 10:10 AM, Asura  wrote:
> > > I have some Twitter login problem with my Polaris 6.2 Mobile Browser
> > > on handset device.
> > > I’ve been trying to figure it out. But I haven’t found out a problem,
> > > I really need you guys's answer for that.
> > > Currently, I use the IE user agent string for compatibility.
> > > I’ve attached some transaction log.
> > > Please let me know, if you guys need more information.
> > > I’m looking forward to your hopeful response.
> > > Thank you.
> >
> > >
> ---­--
> > > POSThttp://twitter.com/oauth/authorizeHTTP/1.1
> > > Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
> > > application/x-shockwave-flash, application/vnd.ms-excel, application/
> > > vnd.ms-powerpoint, application/msword, */*
> > > Accept-Language: ko
> > > Accept-Encoding: gzip, deflate
> > > User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0);
> > > 800*480;POLARIS 6.100;em1.0;01057407732
> > > Host: twitter.com
> > > Connection: Keep-Alive
> > > Referer:
> > >http://twitter.com/oauth/authorize?oauth_token=QQCGC4jstIj1LN73LZxuh2.
> ..
> > > Proxy-Authorization: Basic OTcyMjQ5NjEwNTp2enc=
> > > Cookie: guest_id=127181804004115551;
> >
> > >
> original_referer=LQtHfb3aVLhzTQteZqBtMsK1SG1k6PabMrGGFzkb8SWvN4rcMar6PByaoA­j77FrM0MzwLyUG00BPri2ivfClbpZqqFy5G5VDpU5n;
> > > auth_token=;
> >
> > >
> _twitter_sess=BAh7CzoPY3JlYXRlZF9hdGwrCKpp52FRh4oAToOcmV0dXJuX3RvIl5odHRwOi­8vv50AdHdpdHRlci5jb20vb2F1dGgvYXV0aG9yaXplP29hdXRoX3Rva2VuPVFRQ0dDD50ANGpzd­ElqMUxONzNMWnh1aDJKaEtFYWVvaWZGN1hmTVNIalpSWToRdHJhbnNff50AcHJvbXB0MDoMY3Ny­Zl9pZCIlYmRiMzYzNWJjZWQ0MjYyZjc4ZDZmODViZTUyy50ANjhiZGM6B2lkIiUxYjg2NmE0OTl­iNjI0NDljNWUwMTc5Yjg1MWU1YmU1YiIKK50AZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rm­xhc2g6OkZsYXNoSGFzaHsAA50ABjoKQHVzZWR7AAA53DD53D--
> > > c2404da8c9fd8ee2a8738deeb9f7b77d49ee0c7d;
> > > __utmz=43838368.1271818261.2.2.utmcsr=browser.lgtelecom.com|
> > > utmccn=(referral)|utmcmd=referral|utmcct=/svc_twitter/fb/width/prg/
> > > information_1.htm;
> > > __utma=43838368.114323.1271818047.1271818047.1271818261.2;
> > > __utmc=43838368; __utmv=43838368.langgAA0en;
> > > __utmb=43838368.4.10.1271818261
> > > Content-Type: application/x-www-form-urlencoded
> > > Content-Length: 186
> >
> > >
> authenticity_token=8e936e0758e27e3bfd5dfba85e62ee418d045f6f&oauth_token=QQC­GC4jstIj1LN73LZxuh2JhKEaeoifF7XfMSHjZRY&sessionnBusername_or_emaillD=minbg7­17&sessionnBpassworddD=m20062445
> >
> > >
> ---­---­
> > > HTTP/1.1 601 Connect Fail
> > > Connection: close
> > > Content-Length: 55
> > > Connecting to WEB Server Fail
> >
> > --
> > Raffi Krikorian
> > Twitter Platform Teamhttp://twitter.com/raffi- Hide quoted text -
> >
> > - Show quoted text -
>



-- 
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi

Re: [twitter-dev] Re: User tag inside users/show

[Raffi Krikorian]

hi!

are you still, as of monday 10 may, having this problem?  if so, please send
me an email directly with a list of screen_names that you are seeing this
problem on, and i can personally track it down.

i'll then also update this mailing list.

thanks!

On Sat, May 8, 2010 at 6:21 PM, catalyst media <
catalystmediastud...@gmail.com> wrote:

> Is this fixed yet? I'm still having issues with this problem. Is
> anyone else still experiencing issues with it?
>
> Thanks!
> Paul
>
> On May 7, 10:03 am, Taylor Singletary 
> wrote:
> > Melissa,
> >
> > We had to pause the cache expiration for a little while yesterday
> afternoon,
> > but it resumed last night. It's going to continue working through the
> queue
> > today.
> >
> > Taylor Singletary
> > Developer Advocate, Twitterhttp://twitter.com/episod
> >
> > On Fri, May 7, 2010 at 7:51 AM, Taylor Singletary <
> >
> >
> >
> > taylorsinglet...@twitter.com> wrote:
> > > Hi Melissa,
> >
> > > Sorry to hear you are still down. Can you send along some examples of
> > > payloads still including the embedded user object and the URL used to
> access
> > > it?
> >
> > > Taylor Singletary
> > > Developer Advocate, Twitter
> > >http://twitter.com/episod
> >
> > > On Fri, May 7, 2010 at 7:41 AM, melissa 
> wrote:
> >
> > >> Sorry, missed your last reply.  Anyway, we are still down.  I assume
> > >> propagation *should* have happened - what can we do to debug this?
> >
> > >> On May 7, 10:39 am, melissa  wrote:
> > >> > Guys, we really need an update on this.  I understand if you don;t
> > >> > have a resolution, but not responding at all is not cool.  Looks
> like
> > >> > maybe Tweetsharp, the API we use, thinks the problem is resolved,
> but
> > >> > our customers are still DOWN.  Do we need to redeploy a workaround?
> > >> > What is the ETA?
> >
> > >> > On May 6, 12:19 pm, Taylor Singletary  >
> > >> > wrote:
> >
> > >> > > We're working on getting this fixed as soon as we can.
> >
> > >> > > Taylor Singletary
> > >> > > Developer Advocate, Twitterhttp://twitter.com/episod
> >
> > >> > > On Thu, May 6, 2010 at 9:12 AM, irhetoric  >
> > >> wrote:
> > >> > > > This appears to still be broken.  It affects anyone using the
> > >> > > > TweetSharp library as well. There's a workaround (http://
> > >> > > > tweetsharp.codeplex.com/Thread/View.aspx?ThreadId=211712), but
> > >> > > > hopefully it will be fixed soon so that we don't have to
> redeploy
> > >> with
> > >> > > > the workaround.
> >
> > >> > > > On May 6, 5:23 am, Raffi Krikorian  wrote:
> > >> > > > > i'm currently looking into this now.
> >
> > >> > > > > On Thu, May 6, 2010 at 4:51 AM, Rich 
> wrote:
> > >> > > > > > Yep looks like I spoke to soon, many of my users are still
> > >> seeing this
> > >> > > > > > issue.  I've actually handled it but Apple are now taking
> about
> > >> a week
> > >> > > > > > to approve updates
> >
> > >> > > > > > On May 6, 6:50 am, Raul  wrote:
> > >> > > > > > > We still see this issue on every request athttp://
> streamd.in,
> > >> Also
> > >> > > > > > > all other apps that use twitter4j are experiencing this
> issue.
> >
> > >> > > > > > > On May 5, 6:04 pm, Taylor Singletary <
> > >> taylorsinglet...@twitter.com>
> > >> > > > > > > wrote:
> >
> > >> > > > > > > > This should now be fixed, though it may take a little
> while
> > >> for the
> > >> > > > > > cache to
> > >> > > > > > > > completely clear the labyrinth.
> >
> > >> > > > > > > > Let us know if you're still having wide spread problems.
> >
> > >> > > > > > > > Thanks!
> > >> > > > > > > > Taylor
> >
> > >> > > > > > > > On Wed, May 5, 2010 at 2:27 PM, Rich  >
> > >> wrote:
> > >> > > > > > > > > Cool, thanks Raffi, I was more concerned if it was
> > >> intentional
> > >> > > > rather
> > >> > > > > > > > > than a bug :)  Of course we all get unintentional bugs
> > >> from time
> > >> > > > to
> > >> > > > > > > > > time
> >
> > >> > > > > > > > > On May 5, 10:21 pm, Raffi Krikorian <
> ra...@twitter.com>
> > >> wrote:
> > >> > > > > > > > > > my stance on versioning is for when something has
> > >> changed that
> > >> > > > > > breaks
> > >> > > > > > > > > > backwards compatibility.  in this case, we haven't
> > >> broken
> > >> > > > backwards
> > >> > > > > > > > > > compatibility, but a regression was introduced.
> > >>  regressions
> > >> > > > can
> > >> > > > > > get
> > >> > > > > > > > > > introduced in a variety of different ways, and
> across a
> > >> variety
> > >> > > > of
> > >> > > > > > > > > different
> > >> > > > > > > > > > properties unfortunately.  software projects do
> their
> > >> best to
> > >> > > > avoid
> > >> > > > > > them
> > >> > > > > > > > > --
> > >> > > > > > > > > > but its orthogonal to versioning
> >
> > >> > > > > > > > > > either way - we're working on a fix.
> >
> > >> > > > > > > > > > On Wed, May 5, 2010 at 2:11 PM, Orian Marx (@orian)
> <
> > >> > > > > > or...@orianmarx.com
> > >> > > > > > > > > >wrote:
> >
> > >> > > > > > > > > > > Well, I'm not sure if Rich was 

Re: [twitter-dev] Email address Search

[Nigel Legg]

Twitter does not allow access to email addresses at all.

On 9 May 2010 11:56, Vaibhav Agrawal  wrote:

> Hello Team,
>
> Is there any way to search friends/profiles on the basis of 'email
> address' only?
> We were trying to write an application and for that we have thought of
> using the email address as the basic search criteria. ( As first name,
> last name can be easily be duplicate in nature and we therefore want
> the search to return 'only one profile' or 'none').
>
> It will be of great help from your side if you can suggest some
> solution.
>
>
> Thanks in advance,
> Cheers!
>