Re: [twitter-dev] Re: Signature generation issue

[kamesh SmartDude]

Hai lappynet,

I Used GET method to retrive the Request Token And I Avoided the OAuth
Callback, because it was registered when i registered my app.

Below is the method how i am  doing.


 ** SignatureBase String is *

GET&https%3A%2F%2Fapi.twitter.com
%2Foauth%2Frequest_token&oauth_consumer_key%3D
%26oauth_nonce%3DydBxFJKdzK%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1300167727%26oauth_version%3D1.0

Signature Key U are appending "&" and it is correct.

i am adding the oauth header like below

OAuth realm="Twitter API", oauth_consumer_key=,
oauth_nonce=ydBxFJKdzK, oauth_signature=89%2BSoLKBdE%2FeHN5PFRxNl3G7tNo%3D,
oauth_signature_method=HMAC-SHA1, oauth_timestamp=1300167727,
oauth_version=1.0

I think u might have some problem with generating the signature.


Try this,
//kamesh



On Mon, Mar 14, 2011 at 8:16 PM, lappynet  wrote:

> cURL... I've heard about this, but I don't really know about it. Is
> there a windows version as I don't have access to other OSs at work
> (*sigh*)?
>
> On Mar 14, 2:18 pm, Taylor Singletary 
> wrote:
> > Hi Georgina,
> >
> > Everything appears correct with your base string for this step.
> >
> > Are you performing this operation through a HTTP proxy of any kind? Have
> you
> > tried producing a valid OAuth header and executed it in curl (without
> having
> > "executed it" in C# first)? I'm not familiar with C#'s HTTP request
> > libraries and the configuration options available to you in it.
> >
> > We were having an issue with occasionally hanging connections recently
> and
> > it's possible that it may be related -- but if that's the case, you
> > shouldn't have it occur to you every time -- it would be one out of X
> times.
> >
> > I'm curious where the connection is hanging -- while you are sending HTTP
> > request headers or when your HTTP client is awaiting a response?
> >
> > Thanks,
> > Taylor
> >
> >
> >
> >
> >
> >
> >
> > On Mon, Mar 14, 2011 at 7:02 AM, lappynet 
> wrote:
> > > Hi
> >
> > > I'm using C#.NET to produce an oob client. I've fallen at the first
> > > hurdle though as I'm failing to make the token request.
> >
> > > I've gone through many iterations, and am no longer receiving a 417,
> > > 404, or 401. This is very positive! Now my application hangs whilst
> > > waiting for a response from twitter. (I left it running for an hour
> > > over lunch and still nothing happened, and the code didn't appear to
> > > want to step through.)
> >
> > > I've tried with the values detailed in the documentation to have a
> > > look at the variables that have been produced from them in my
> > > algorithm. I think that I've traced it down to being the way I
> > > generate the signature string:
> >
> > > string signingKey = Uri.EscapeDataString(ConsumerSecret) + "&";
> > > HMACSHA1 hasher = new HMACSHA1(new
> > > ASCIIEncoding().GetBytes(signingKey));
> > > string signatureString = Convert.ToBase64String(hasher.ComputeHash(new
> > > ASCIIEncoding().GetBytes(baseString)));
> >
> > > My base string is:
> >
> > > POST&https%3A%2F%2Fapi.twitter.com%2Foauth
> > > %2Frequest_token&oauth_callback%3Doob%26oauth_consumer_key%XXX
> > > %26oauth_nonce%3DNjM0MzU3MDgxMDEyMDcwODkw%26oauth_signature_method
> > > %3DHMAC-SHA1%26oauth_timestamp%3D1300111301%26oauth_version%3D1.0
> >
> > > Any pointers as to where I may be going wrong?
> >
> > > Thanks in advance
> > > Georgina
> >
> > > --
> > > Twitter developer documentation and resources:
> http://dev.twitter.com/doc
> > > API updates via Twitter:http://twitter.com/twitterapi
> > > Issues/Enhancements Tracker:
> > >http://code.google.com/p/twitter-api/issues/list
> > > Change your membership to this group:
> > >http://groups.google.com/group/twitter-development-talk
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Using XAuth with TweetSharp

[JamieMac]

I'm trying to use XAuth with TweetSharp.  I have my app approved by
Twitter for XAuth access.  I can call the XAuth funciton as per the
TweetSharp sample and I don't recieve an error  - however, the
returned ScreenName, Token, and TokenSecret are all "?" and the userID
is 0.


The code is dead simple:
TwitterService service = new TwitterService("consumer
key", "consumer secret");
OAuthAccessToken access =
service.GetAccessTokenWithXAuth("uname","pwd");

Any ideas as to what could be happening?   Given a user token and
secret, my app has no problem authenticating and making any necessary
calls.

Thanks.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Re: IPhone + Twitter + LinkedIn Error : Command /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/gcc-4.2 failed with exit code 1

[Bess Ho]

*From Linkedin response:*
http://developer.linkedin.com/message/8675#8675

If you are not using an oauth callback, the user will need to return to your
application themselves and input the token for you to use for verification.
If you are using a callback, the user will never see the PIN screen.  See
the documentation on Using OAuth with the LinkedIn
APIsfor more information.

*See more explanation here*
http://developer.linkedin.com/docs/DOC-1008#comment-1337

If the member chooses to authorize your application, you'll get two fields
back: oauth_token and an oauth_verifier. The oauth_token will be the same
requestToken you received in the first step. You'll want to temporarily
store the oauth_verifier so that you can use it as part of your accessToken
request in the next step.

In the examples used so far, the callback specified in the requestToken step
would receive a request like this:

http://localhost/oauth_callback?oauth_token=94ab03c4-ae2c-45e4-8732-0e6c4899db63&oauth_verifier=98295

If the member chooses to deny your application a token (by pressing the
Cancel button in the authorization flow), we redirect them back to your
server. We send them to either the "Integration URL" you defined for your
application, or, if that value is blank, the OAuth callback URL you passed
in your request.  However we do not send a token or secret. Instead your
callback will include the url parameter oauth_problem with the value
user_refused.

Note: If you're performing an out-of-band style request (indicated by
setting the oauth_callback to "oob", the user is be directed to a page
containing the OAuth Verifier step. They can then return to your application
and hand-enter the OAuth verifier code, which you pass back to us in the
next step. Otherwise, all of these steps remain the same. Out of band
requests are done where there is no natural web flow available as part of
your application.
On Mon, Mar 14, 2011 at 4:35 PM, Bess Ho  wrote:

>
> http://stackoverflow.com/questions/5297783/linkedin-successfull-authrized-interface-on-iphone
>
> The problems you are facing on Linkedin authorized page are similar to
> Twitter. Initially Twitter authorized page is not optimized to mobile
> browser screen size. This is not related to your code at all.
>
> Since I am not sure where Linkedin developer group is and I didn't sign up
> for the developer group mailing list, I'll see if I could contact Linkedin
> directly about this issue.
>
>
> On Mon, Mar 14, 2011 at 2:08 AM, Bess Ho  wrote:
>
>> Congratulation. Are you planning to post photos than updating status on
>> Twitter, FB, & Linkedin at the same time?
>>
>>
>> On Mon, Mar 14, 2011 at 2:01 AM, Battan Amit  wrote:
>>
>>> *Solved *
>>>
>>> solved now...I have given the same key and secret to both linkedin and
>>> twitter ..after changing them it works
>>> 
>>> AB
>>>
>>> On 14 March 2011 11:55, Battan Amit  wrote:
>>>
 I done one thing that is ... I remove the library files of linkedin
 sdk.. and add the source files of it with oAuth files from twiiter sdk...
 then it works ok for linkedin http://i.imgur.com/cXLXU.png
 http://i.imgur.com/ntV9G.png then I integrate all twitter code then
 project run ok without error but for twitter login interface it shows PAGE
 NOT FOUND ..http://i.imgur.com/8a1ua.png


 
 AB




 On 12 March 2011 11:44, Bess  wrote:

> First of all it is difficult to identify errors esp you don't have the
> source code. However the stockoverflow discussion was good enough to
> point out the general problems.
>
> ld: duplicate symbol _EstimateBas64EncodedDataSize in /Users/pratgupta/
> Desktop/Settinglinkedin/10_mar_butterfli/LinkedInClientLibrary/build/
> Debug-iphonesimulator/libLinkedInClientLibrary.a(Base64Transcoder.o)
> and /Users/pratgupta/Desktop/Settinglinkedin/10_mar_butterfli/Twitter
> +OAuth/Libraries & Headers/libOAuth.a(Base64Transcoder.o)
>
> Problem is: duplicate symbol
>
> It occurs on _EstimateBas64EncodedDataSize from LinkedinClientLibrary
> in libLinkedInClientLibrary.a(Base64Transcoder.o) and Twitter+OAuth in
> libOAuth.a(Base64Transcoder.o).
>
> Note: LinkedIn library and Ben Gottlieb's Twitter client include the
> same OAuthConsumer code. It is duplicated. libLinkedInClientLibrary
> and libOAuth both symbolicate the same method
> '_EstimateBas64EncodedDataSize'. Check your #imports.
>
> Just do a search within your Xcode project on
> _EstimateBas64EncodedDataSize. Find out where the duplicated methods.
> Determine which one you should remove.
>
> On Mar 11, 4:56 am, Battan Ror  wrote:
> > HI All
> >
> > I am using MGTwitterEngine oAuth and LinkedIn iOS sdk in my Iphone
> > application with facebook-ios-sdk
> >
> > TwitterEngine :https://github.com/bengottlieb/Twitter-OAuth-iPhone
> >
> 

Re: [twitter-dev] Hoping to clear my confusion about Twitter's announcement

[Scott Wilcox]

Bearing mind that I run tweekly.fm, some of this issues are of interest to me 
too.

On 14 Mar 2011, at 23:39, Tim Haines wrote:

> Hey Ryan, Raffi, Taylor, Matt, and other Twitter staff, 
> 
> I've been confused about Ryan's post, and some of the follow up comments.  
> Some of the tweets I've seen since have been reassuring that my original 
> interpretation of Ryan's email was inaccurate.  I thought you were saying 'no 
> new client apps allowed', and I'm very relieved to hear I was wrong.
> 
> I wanted to follow up with a few more questions and comments to make sure I 
> understand Twitter's message correctly.  Twitter staff, if I have anything 
> wrong here, please correct, or rephrase to be more accurate.
> 
> Please excuse the length of this and the number of questions at the end of 
> the email. Changing the API rules is changing the contract we have, and as 
> I'm so invested in the ecosystem (my family's livelihood now depends on it), 
> I want to be completely sure I understand what the new contract is that 
> you're introducing.  
> 
> First off, some background.  Ryan said that developers are welcome to develop 
> things that Twitter has said developers shouldn't be doing - "shouldn't" is 
> guidance only, and not a prohibition.  Twitter will only interfere with 
> applications if they break the API TOS. Tweets related to this (clicking on 
> the last one and viewing the thread is easiest):
> https://twitter.com/joestump/status/47094929796759552
> https://twitter.com/rsarver/status/47095346899320832
> https://twitter.com/timhaines/status/47096379306291203
> https://twitter.com/rsarver/status/47096690288771072
> https://twitter.com/timhaines/status/47097497679708160
> https://twitter.com/rsarver/status/47097681591545856
> 
> Furthermore, the most disturbing paragraph for me in Ryan's announcement:
> 
> If you are an existing developer of client apps, you can continue to serve 
> your user base, but we will be holding you to high standards to ensure you do 
> not violate users’ privacy, that you provide consistency in the user 
> experience, and that you rigorously adhere to all areas of our Terms of 
> Service.
> 
> This and the preceding paragraph together could be interpreted to mean that 
> developers "aren't allowed" to build NEW client apps.  According to the 
> tweets above, they are allowed, but Twitter is advising developers that they 
> should focus their efforts elsewhere.  Likewise, existing applications "will 
> be held to high standards".  As Ryan clarified in his tweets, these 
> applications won't be interfered with unless they break the API TOS.  So all 
> told, the email itself doesn't introduce anything new rulewise; you can do 
> anything you want within the API TOS, but if you break the API TOS you'll 
> potentially have your app revoked.  No change here.
> 
> You won't be applying a subjective 'high standard' or 'high bar' and revoking 
> an app unless it breaks the API TOS. Phew!  You are remaining an open API, 
> within the confines of your stated rules.
> 
> However, the email was accompanied with changes to the API TOS (of course 
> Twitter can make any change to the API TOS at any time - including adding 
> further restrictions in the future).  This round of changes included amongst 
> other things, the addition of section I.5, adding restrictions to what client 
> applications may and may not do.  For the purposes of this email, I'm 
> considering my own application, Favstar, a client.  While it doesn't allow 
> you to tweet at the moment, it will in the coming months, therefore meeting 
> the criteria specified in the API TOS for Favstar to be regarded as a client.
> 
> 
> My questions:
> 
> 
> 5a: Your Client must use the Twitter API as the sole source for features that 
> are substantially similar to functionality offered by Twitter. Some examples 
> include trending topics, who to follow, and suggested user lists.
> 
> Question re 5a:  Favstar has for a long time offered 'suggested user lists' 
> in the form of it's popular page 
> (http://favstar.fm/popular-on-twitter-by-tweets-with-50-favorites)  Is this 
> feature now in breach of the API TOS?  If it is in breach, does this place 
> Favstar in breach until the feature is removed?
> 
> Question re 5a:  If I was to add features that surfaced 'popular themes' 
> found in tweets that Favstar collects, would this be considered similar to 
> Trending topics, and put Favstar in breach of the API TOS?
> 
> Question re 5a: Favstar users can buy 'bonus features', and receive a slew of 
> extra features.  I've recently started promoting these users on the site. If 
> follow buttons were added to their avatar's in the places of promotion, could 
> this be considered as a 'who to follow' feature that would put Favstar in 
> breach of the API TOS?
> 
> 5c: Your Client cannot frame or otherwise reproduce significant portions of 
> the Twitter service. You should display Twitter Content from the Twitter API.
> 
> Clarify Pleas

[twitter-dev] Hoping to clear my confusion about Twitter's announcement

[Tim Haines]

Hey Ryan, Raffi, Taylor, Matt, and other Twitter staff,

I've been confused about Ryan's post, and some of the follow up comments.
 Some of the tweets I've seen since have been reassuring that my original
interpretation of Ryan's email was inaccurate.  I thought you were saying
'no new client apps allowed', and I'm very relieved to hear I was wrong.

I wanted to follow up with a few more questions and comments to make sure I
understand Twitter's message correctly.  Twitter staff, if I have anything
wrong here, please correct, or rephrase to be more accurate.

Please excuse the length of this and the number of questions at the end of
the email. Changing the API rules is changing the contract we have, and as
I'm so invested in the ecosystem (my family's livelihood now depends on it),
I want to be completely sure I understand what the new contract is that
you're introducing.

First off, some background.  Ryan said that developers are welcome to
develop things that Twitter has said developers shouldn't be doing -
"shouldn't" is guidance only, and not a prohibition.  Twitter will
only interfere with applications if they break the API TOS. Tweets related
to this (clicking on the last one and viewing the thread is easiest):

   - https://twitter.com/joestump/status/47094929796759552
   - https://twitter.com/rsarver/status/47095346899320832
   - https://twitter.com/timhaines/status/47096379306291203
   - https://twitter.com/rsarver/status/47096690288771072
   - https://twitter.com/timhaines/status/47097497679708160
   - https://twitter.com/rsarver/status/47097681591545856


Furthermore, the most disturbing paragraph for me in Ryan's announcement:

If you are an existing developer of client apps, you can continue to serve
> your user base, but we will be holding you to high standards to ensure you
> do not violate users’ privacy, that you provide consistency in the user
> experience, and that you rigorously adhere to all areas of our Terms of
> Service.


This and the preceding paragraph together could be interpreted to mean that
developers "aren't allowed" to build NEW client apps.  According to the
tweets above, they are allowed, but Twitter is advising developers that they
should focus their efforts elsewhere.  Likewise, existing applications "will
be held to high standards".  As Ryan clarified in his tweets, these
applications won't be interfered with unless they break the API TOS.  So all
told, the email itself doesn't introduce anything new rulewise; you can do
anything you want within the API TOS, but if you break the API TOS you'll
potentially have your app revoked.  No change here.

You won't be applying a subjective 'high standard' or 'high bar' and
revoking an app unless it breaks the API TOS. Phew!  You are remaining an
open API, within the confines of your stated rules.

However, the email was accompanied with changes to the API TOS (of course
Twitter can make any change to the API TOS at any time - including adding
further restrictions in the future).  This round of changes included amongst
other things, the addition of section I.5, adding restrictions to what
client applications may and may not do.  For the purposes of this email, I'm
considering my own application, Favstar, a client.  While it doesn't allow
you to tweet at the moment, it will in the coming months, therefore meeting
the criteria specified in the API TOS for Favstar to be regarded as a
client.


My questions:


5a: Your Client must use the Twitter API as the sole source for features
> that are substantially similar to functionality offered by Twitter. Some
> examples include trending topics, who to follow, and suggested user lists.


*Question re 5a:*  Favstar has for a long time offered 'suggested user
lists' in the form of it's popular page (
http://favstar.fm/popular-on-twitter-by-tweets-with-50-favorites)  Is this
feature now in breach of the API TOS?  If it is in breach, does this place
Favstar in breach until the feature is removed?

*Question re 5a:*  If I was to add features that surfaced 'popular themes'
found in tweets that Favstar collects, would this be considered similar to
Trending topics, and put Favstar in breach of the API TOS?

*Question re 5a:* Favstar users can buy 'bonus features', and receive a slew
of extra features.  I've recently started promoting these users on the site.
If follow buttons were added to their avatar's in the places of promotion,
could this be considered as a 'who to follow' feature that would put Favstar
in breach of the API TOS?

5c: Your Client cannot frame or otherwise reproduce significant portions of
> the Twitter service. You should display Twitter Content from the Twitter
> API.


*Clarify Please re 5c:* This seems like it could be applied pretty
generally, and I'm not sure what what constitute a breach of it.  Could you
provide some examples?

5d: Do not store non-public user profile data or content.


*Question re 5d:* Favstar collects and stores tweets that are favorited.
 Some of th

Re: [twitter-dev] Re: IPhone + Twitter + LinkedIn Error : Command /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/gcc-4.2 failed with exit code 1

[Bess Ho]

http://stackoverflow.com/questions/5297783/linkedin-successfull-authrized-interface-on-iphone

The problems you are facing on Linkedin authorized page are similar to
Twitter. Initially Twitter authorized page is not optimized to mobile
browser screen size. This is not related to your code at all.

Since I am not sure where Linkedin developer group is and I didn't sign up
for the developer group mailing list, I'll see if I could contact Linkedin
directly about this issue.

On Mon, Mar 14, 2011 at 2:08 AM, Bess Ho  wrote:

> Congratulation. Are you planning to post photos than updating status on
> Twitter, FB, & Linkedin at the same time?
>
>
> On Mon, Mar 14, 2011 at 2:01 AM, Battan Amit  wrote:
>
>> *Solved *
>>
>> solved now...I have given the same key and secret to both linkedin and
>> twitter ..after changing them it works
>> 
>> AB
>>
>> On 14 March 2011 11:55, Battan Amit  wrote:
>>
>>> I done one thing that is ... I remove the library files of linkedin sdk..
>>> and add the source files of it with oAuth files from twiiter sdk... then it
>>> works ok for linkedin http://i.imgur.com/cXLXU.png
>>> http://i.imgur.com/ntV9G.png then I integrate all twitter code then
>>> project run ok without error but for twitter login interface it shows PAGE
>>> NOT FOUND ..http://i.imgur.com/8a1ua.png
>>>
>>>
>>> 
>>> AB
>>>
>>>
>>>
>>>
>>> On 12 March 2011 11:44, Bess  wrote:
>>>
 First of all it is difficult to identify errors esp you don't have the
 source code. However the stockoverflow discussion was good enough to
 point out the general problems.

 ld: duplicate symbol _EstimateBas64EncodedDataSize in /Users/pratgupta/
 Desktop/Settinglinkedin/10_mar_butterfli/LinkedInClientLibrary/build/
 Debug-iphonesimulator/libLinkedInClientLibrary.a(Base64Transcoder.o)
 and /Users/pratgupta/Desktop/Settinglinkedin/10_mar_butterfli/Twitter
 +OAuth/Libraries & Headers/libOAuth.a(Base64Transcoder.o)

 Problem is: duplicate symbol

 It occurs on _EstimateBas64EncodedDataSize from LinkedinClientLibrary
 in libLinkedInClientLibrary.a(Base64Transcoder.o) and Twitter+OAuth in
 libOAuth.a(Base64Transcoder.o).

 Note: LinkedIn library and Ben Gottlieb's Twitter client include the
 same OAuthConsumer code. It is duplicated. libLinkedInClientLibrary
 and libOAuth both symbolicate the same method
 '_EstimateBas64EncodedDataSize'. Check your #imports.

 Just do a search within your Xcode project on
 _EstimateBas64EncodedDataSize. Find out where the duplicated methods.
 Determine which one you should remove.

 On Mar 11, 4:56 am, Battan Ror  wrote:
 > HI All
 >
 > I am using MGTwitterEngine oAuth and LinkedIn iOS sdk in my Iphone
 > application with facebook-ios-sdk
 >
 > TwitterEngine :https://github.com/bengottlieb/Twitter-OAuth-iPhone
 >
 > LinkedInIphone :https://github.com/ResultsDirect/LinkedIn-iPhone
 >
 > Both integrated well separately, But when I have used both in
 > application then error coming
 >
 > FB + Twitter = working well
 > FB + LinkedIn = Working Well
 > FB + Twitter + LinkedIn = Not Working
 >
 > and giving error
 >
 > Command /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/
 > bin/gcc-4.2 failed with exit code 1
 >
 > Please help me where I am wrong.
 >
 > Error Transcript Text File
 >
 > Build butterfli of project butterfli with configuration Debug
 >
 > Ld build/Debug-iphonesimulator/butterfli.app/butterfli normal i386
 > cd /Users/pratgupta/Desktop/Settinglinkedin/10_mar_butterfli
 > setenv MACOSX_DEPLOYMENT_TARGET 10.6
 > setenv PATH "/Developer/Platforms/iPhoneSimulator.platform/Developer/
 > usr/bin:/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin"
 > /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/
 > gcc-4.2 -arch i386 -isysroot /Developer/Platforms/
 > iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator4.1.sdk -L/
 > Users/pratgupta/Desktop/Settinglinkedin/10_mar_butterfli/build/Debug-
 > iphonesimulator "-L/Users/pratgupta/Desktop/Settinglinkedin/
 > 10_mar_butterfli/Twitter+OAuth/Libraries & Headers"
 -F/Users/pratgupta/
 > Desktop/Settinglinkedin/10_mar_butterfli/build/Debug-iphonesimulator -
 > filelist /Users/pratgupta/Desktop/Settinglinkedin/10_mar_butterfli/
 > build/butterfli.build/Debug-iphonesimulator/butterfli.build/Objects-
 > normal/i386/butterfli.LinkFileList -mmacosx-version-min=10.6 -all_load
 > -Xlinker -objc_abi_version -Xlinker 2 -framework Foundation -framework
 > UIKit -framework CoreGraphics -lOAuth -lxml2 /Users/pratgupta/Desktop/
 > Settinglinkedin/10_mar_butterfli/LinkedInClientLibrary/build/Debug-
 > iphonesimulator/libLinkedInClientLibrary.a -o
 /Users/pratgupta/Desktop/
 > Settinglinkedin/10_mar_butterfli/build/Debug-iphonesimulator/
 > but

[twitter-dev] Re: Please hire a developer relations manager

[Bess]

This is interesting. I don't see this is a threat suggestion for any
replacement @Twitter. In fact Twitter is growing to the size where
Twitter should consider having an official Developer Relations
Manager. Facebook lost one and found a new hire. Google lost one and
is hiring a new one. I have served at least 2 different "official"
advisory boards of developers for the biggest companies. I have
informally given advisory input for other big companies. Facebook does
this privately by inviting selective groups of developers from time to
time to evaluate their API before public release. Microsoft also does
this kind of things with their MSFT Certified Golden partners. The
companies I served directly will call advisory board on quarterly
basis to present us with rough drafts and product road map to ask for
candid input. It turns out to be very helpful to get insights from
active developers. It was amazing that the company executives would
listen "in" to these communications to understand the community.

Google is hiring crazy to expand Developer Relation team size to
support global reach. ROI must be very good before Google could
justify the head counts and investment. You can see how quickly Google
sold out their Google I/O conference in less than an hour. Given >75%
Twitter traffic are coming from API, it makes sense on the business
side that Twitter continues to support traffic growth without adding
business costs or increase burn rate.

Most likely Twitter stock would trade lower in secondary market or
investors would lower the company evaluation if Twitter couldn't
maintain the growth rate at par with Facebook. These days developer
community is a "true" commodities for currencies. The mobile app store
war battles for developers' love is a good example.

4/15/2010
Twitter Reveals: 75% of all their traffic comes from their API
http://blog.programmableweb.com/2010/04/15/twitter-reveals-75-of-our-traffic-is-via-api-3-billion-calls-per-day/

9/10/2007
API has 10x the traffic of the website and that of all that’s happened
with Twitter in the past year that “the amount of activity around the
API has been the most surprising experience”
http://blog.programmableweb.com/2007/09/10/twitter-api-traffic-is-10x-twitters-site/

On Mar 14, 8:48 am, Adam Green <140...@gmail.com> wrote:
> I've been getting emails saying that this message was a request to replace
> Ryan. That was not my intent. I am suggesting that he be given someone to
> help with developer communications. His job title implies that he does much
> beside sending out these cheery notes to developers. He should have a
> full-time person to do this and much else to improve developer relations
> instead.
>
> If this was seen as an attack on Ryan, I apologize. I recognize the irony of
> my critique of his message as an attack on us being seen as an attack on
> him. It was meant to be a suggestion for a better way to work together.
>
>
>
> On Mon, Mar 14, 2011 at 9:44 AM, Adam Green <140...@gmail.com> wrote:
> > First of all, I honestly believe that Twitter HQ values developers and
> > appreciates their contribution. That is why I decided to devote myself
> > to this area a couple of years ago. I was amazed that when a dev
> > reported a problem the engineer responsible replied here and tried to
> > solve it. That is better than any big product I know of today. That is
> > why you have so many developers putting in all this work.
>
> > I also believe that the last few announcements from Ryan and others
> > have been the worst examples of third party developer management I
> > have seen in 30 years in this business. I can see what Ryan wanted to
> > accomplish in his latest message. He wanted to provide guidance. He
> > ended up telling us that Twitter no longer wanted anyone to build
> > clients, didn't explain clearly what a "client" meant to him, and
> > pointed out that hundreds of apps that fail to meet his undefined
> > "high bar" were cut off every week. Not good. Sorry, Ryan. You are
> > right. You are not good at communicating with third party developers.
> > At least not in written form. You look like a very cool guy with a lot
> > of personal charm. Maybe it works better in person. You should spend
> > some time talking directly to developers in small groups. It might
> > help you develop some canned responses that work.
>
> > Here is a simple way this could have been prevented. If you had a
> > developer relations person with experience and skills in dealing with
> > third party developers, who have completely different motivations from
> > in-house coders, he or she could have quietly passed around a draft of
> > what you wanted to say. This would have gotten very strong negative
> > reactions. You would have been able to reformulate it to strip out the
> > implied threats and turn it into a positive roadmap. It could have
> > been framed as "Here are some areas we promise to leave open for
> > developers. If you work here, we will give you all kind

Re: [twitter-dev] Re: get user email address

[Scott Wilcox]

Hello,

As Taylor has just said to you, it is impossible to get a users email address 
from the Twitter REST API. If you want a users email address you will have to 
explicitly ask them for it yourself.

Scott.

On 14 Mar 2011, at 22:32, Andrey Kostromin wrote:

> I make site registration with twitter. How I can ask email? I have
> twitter access token to get more info (user_id, name,
> screen_name, ...) but not email
> 
> On Feb 23, 5:19 pm, Taylor Singletary 
> wrote:
>> Hi Amrish,
>> 
>> User email addresses are not returned in the Twitter API. If you would like
>> a user's email address, you'll have to ask them for it in your application.
>> 
>> Taylor
>> 
>> On Wed, Feb 23, 2011 at 4:09 AM, amrish.prajapati <
>> 
>> 
>> 
>> amrish.prajap...@gmail.com> wrote:
>>> hello,
>> 
>>> I would like to get all details including email address of user.
>>> When I make http request by parameter screen_name
>> 
>>> http://api.twitter.com/1/users/show.xml?screen_name=
>> 
>>> I am not able to get email address of that user.
>> 
>>> How can I able to get it ?
>> 
>>> Please help for same.
>> 
>>> Thanks in advance.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Re: consistency and ecosystem opportunities

[Alison W]

Chucking in a few lines here too ...

On 14 March 2011 20:03, Derek Gathright  wrote:
> I do it for the challenge and the learning experience.

Ditto. I worked up and 'beta'd' an archive service a while ago but
concluded that Twitter was likely to introduce its own service in that
area (given it had at that time lists and other services had suddenly
become available 'in house) so I ceased work on it but continued to
use it for my own interest. It is a one-way archive and can't be used
to forward to any other service plus it is comprised solely and only
of public data (tweets) of users who requested it. This -- to me --
says it should still be OK on the revised tos.

> For example, where is the official Twitter client for webOS?  Messages
> like "Don't build
> clients anymore" and no official Twitter app on webOS does nothing but hurt
> the ecosystem for thousands of users.  If I were a developer for one of the
> popular webOS clients, I'd be pretty pissed right now.  Heck, as a webOS
> user I'm not thrilled.  I'm sure this is applicable to other ecosystems too.

As another WebOS user here I've tried the 'official' mobile web
interface through the browser, and one of the other clients available,
but neither have given me the user experience I'd like or think could
be possible, so had been thinking of turning my mind to it.

But then on Friday night without any notice or explanation my access
*as a user* to twitter was suspended. As a learning experience it has
been 'interesting'; the system obliges a user to initiate a ticket
requesting reinstatement -- though over 24 hours later I've had
nothing back except an initial automated 'received' reply -- and a set
of timestamps on the ticket thread which are massively in error. I've
done nothing contrary to the TOS and though I was loathe to bring it
up here there is just the tiniest wisp of a thought at the back of my
mind of whether my development activities have been the cause? If so
this should be worrying to everyone here.

Anyway, for anyone who wants to know more you can read it on my blog
at http://www.alisonw.com/

But back on the main issue here, I can understand why Twitter wants to
make this move -- from a business pov it is a no-brainer to do so --
but given the sheer number of developers who have been encouraged in
the past to get involved with using the API to provide services it is
worrying that such a substantial revision has happened.

Alison Wheeler (AlisonW)

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: get user email address

[Andrey Kostromin]

I make site registration with twitter. How I can ask email? I have
twitter access token to get more info (user_id, name,
screen_name, ...) but not email

On Feb 23, 5:19 pm, Taylor Singletary 
wrote:
> Hi Amrish,
>
> User email addresses are not returned in the Twitter API. If you would like
> a user's email address, you'll have to ask them for it in your application.
>
> Taylor
>
> On Wed, Feb 23, 2011 at 4:09 AM, amrish.prajapati <
>
>
>
> amrish.prajap...@gmail.com> wrote:
> > hello,
>
> > I would like to get all details including email address of user.
> > When I make http request by parameter screen_name
>
> >http://api.twitter.com/1/users/show.xml?screen_name=
>
> > I am not able to get email address of that user.
>
> > How can I able to get it ?
>
> > Please help for same.
>
> > Thanks in advance.
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Search old tweets

[A.MellIce]

Hi there,

Is there any way that I can retrieve old tweets using search API's and
I don't know there since_id?
For example, I'm trying to search for tweets from 25 Jan 2011 and it's
not retrieving anything, but when I tried 10 Mar 2011 it worked!

Thanks

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Re: consistency and ecosystem opportunities

[Derek Gathright]

My 2 cents...

The reason for the perceived mixed messages for some of us is because many
developers don't, and never have been interested in doing Twitter
development as a business.  I've created a dozen Twitter clients & apps over
the last 5 years, some of which received enough users and press coverage
that I could have attempted to turn it into a business, but I didn't. Why?
Because it doesn't interest me. I do it for the challenge and the learning
experience.

So, the things we hear Twitter saying are "Don't build clients anymore" as
well as "Client apps make bad business".  Well, first, as long as the APIs
are active and it's not against the TOS, I'm still going to build, develop,
and use my own clients.  Second, I don't care that it makes "bad business",
that's isn't a concern to me.  Third, developers can determine for
themselves what seems like a smart business decision or not.  Fourth,
frankly, Twitter Inc has never been regarded as an expert in monetization
strategies.

Plus, this is info we already knew.  For the most part, building a company
whose main product is a Twitter client hasn't been a good business decision
for a few years (if ever, outside of a lucky few).  But on the other hand,
there are still markets where it could be good business.  For example, where
is the official Twitter client for webOS?  Messages like "Don't build
clients anymore" and no official Twitter app on webOS does nothing but hurt
the ecosystem for thousands of users.  If I were a developer for one of the
popular webOS clients, I'd be pretty pissed right now.  Heck, as a webOS
user I'm not thrilled.  I'm sure this is applicable to other ecosystems too.

The point is, Twitter should be more vocal about what it is going to do as
opposed to coy suggestions to developers (which some perceive as threats)
about what they shouldn't do.  Twitter is going to heavily focus on
front-end user experiences across all platforms? Great! Leave it at that.
 Let developers decide for themselves what are good/bad ideas.  Just arm us
with the knowledge of your plans, and we'll worry about our own.

Finally, Twitter, you should be excited to compete with your developers.
Much of the innovation over the years has been a product of the developer &
user community.  Things like mentions & hashtags came from your users.
 Features like saved searches, lists, trends, and ajax driven clients were
inventions of developers years before they made it into Twitter.com.
 Essentially, "New" Twitter is just a compilation of the best features from
all the 3rd party clients.  Do not be hostile.  Do not attack them with your
TOS.  Do not suspend tokens without working with the developer first.  Doing
these things hurts the community, which in turn hurts you.  Your users are
your product.  Not your platform.  Not your website.  Not your ads.  Your
users.

- @derek

On Mon, Mar 14, 2011 at 10:50 AM, Pizik  wrote:

> I get the distinct feeling of someone saying something that they do not
> really believe in.
>
> Money makes puppets as ever.
>
>  --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: Do new ToS conditions apply to my app?

[howardk]

No, the rejection didn't have anything to do with Twitter. There was
too little functionality in the app -- I was only showing John
Gruber's Daring Fireball feed -- and Apple rejected it as being "not
sufficiently useful or providing long-term entertainment value". So
I've generalized it to allow the user their choice of Twitter feed.
Hopefully that'll answer Apple's objections. And now I have to satisfy
Twitter as well. Sigh.
Howard

On Mar 12, 4:31 pm, kosso  wrote:
> Out of interest, what did you get rejected by Apple for? Was it
> anything to do with Twitter? Or was it all objectiveC stuff?
>
> I too have a Twitter client waiting in the wings for submission. Not
> long to go now.
>
> I'm just going to launch it and see what happens.
>
> if Twitter 'rejects'/disables it (considering they actually hold the
> 'keys' to whether the app is allowed to communicate - thanks oAuth)
> then I'll be making a big fuss about it ;)
>
> Good luck!
> K
>
> On Mar 11, 10:27 pm, howardk  wrote:
>
>
>
> > I've just read the new Terms of Service referenced in the announcement
> > "consistency and ecosystem opportunities". It's unclear to me if those
> > terms apply to an app I've just finished. I've developed a very simple
> > iPad app that allows the user to maintain a list of feeds and stream
> > any of those timelines banner-wise across the screen on demand.
>
> > It's useful if you want to quickly check the most recent tweets from a
> > particular source and also serves as a vehicle to show off some
> > interesting and creative use of 3D typography on the iPad to display
> > the content. There's almost no interface: Tweet content is shown
> > exactly as-is, with only the addition of a username to identify the
> > feed and an elapsed-time-since-publication placard.
>
> > I submitted this app to the app store in December and was rejected.
> > I've rewritten the app in response to Apple concerns and am one (1)
> > day away from resubmitting to the app store. I've got +/- five months
> > of effort into this project and will be devastated if I'm disallowed
> > from publishing at this late date.
>
> > Who can I talk to re determining whether what I've done falls under
> > the umbrella of applications that are now prohibited by the new ToS?
> > Best,
> > Howard Katz

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Anywhere Tweet Boxes

[Peter Denton]

Hello,
I must be missing something obvious about the Anywhere tweetbox. I have a
set of business profile pages and I want to allow any user who comes to
contact those businesses through the  anywhere tweetbox.

Basically, I can:

   -  get the form to render correctly.
   - after the user hit tweet, it will ask to connect

However, it will always fail giving the error that the 
does not match the url for the site, which is my standard callback file.
Ex: I am at Twitter's profile page (url.com/twitter) and I go to submit a
tweet and it will say url.com/twitter does not match url.com/callback

I am guessing there is just something obvious I am not doing.

Thanks in advance

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Spanish apps for the USA market?

[Dean Collins]

Hi, my name is Dean Collins and I'm one of the founders of
http://www.LiveBaseballChat.com   

 

We are a live chat app that is tightly integrated into Facebook and
Twitter.

 

The reason for writing is we've been asked by a few users over the last
few months to create a Spanish version of our app. I'm wondering how
many twitter developers on this list have created a bilingual version of
their apps and what the takeup in the USA market has been?

 

I know that is makes up a significant portion of the USA population but
just hoping for some credible data about similar language conversions.

 

 

Regards,

Dean Collins
LiveChatConcepts inc
d...@livechatconcepts.com 
 +1-212-203-4357   New York
+61-2-9016-5642   (Sydney in-dial).
+44-20-3129-6001 (London in-dial).

 

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: consistency and ecosystem opportunities

[Pizik]

I get the distinct feeling of someone saying something that they do not 
really believe in.

Money makes puppets as ever.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Proposed Additional Feature

[m36tb6ll]

Hi -- would anyone agree if the GET users/lookup and other related API
would include the followed_by in the response rather than making
additional calls to the API to determine the relationship of a user
with the authenticating user?

Just a thought -- or is it already there?

Thanks..

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: consistency and ecosystem opportunities

[@smartwatermelon]

Ryan,

I've read through the rest of this thread and appreciate your
clarifications. May I ask a followup: How does the new policy vis-a-
vis basic functionality client applications apply to platforms on
which Twitter does not have an official client? For example, HP webOS.

Thank you.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Please hire a developer relations manager

[Adam Green]

I've been getting emails saying that this message was a request to replace
Ryan. That was not my intent. I am suggesting that he be given someone to
help with developer communications. His job title implies that he does much
beside sending out these cheery notes to developers. He should have a
full-time person to do this and much else to improve developer relations
instead.

If this was seen as an attack on Ryan, I apologize. I recognize the irony of
my critique of his message as an attack on us being seen as an attack on
him. It was meant to be a suggestion for a better way to work together.


On Mon, Mar 14, 2011 at 9:44 AM, Adam Green <140...@gmail.com> wrote:

> First of all, I honestly believe that Twitter HQ values developers and
> appreciates their contribution. That is why I decided to devote myself
> to this area a couple of years ago. I was amazed that when a dev
> reported a problem the engineer responsible replied here and tried to
> solve it. That is better than any big product I know of today. That is
> why you have so many developers putting in all this work.
>
> I also believe that the last few announcements from Ryan and others
> have been the worst examples of third party developer management I
> have seen in 30 years in this business. I can see what Ryan wanted to
> accomplish in his latest message. He wanted to provide guidance. He
> ended up telling us that Twitter no longer wanted anyone to build
> clients, didn't explain clearly what a "client" meant to him, and
> pointed out that hundreds of apps that fail to meet his undefined
> "high bar" were cut off every week. Not good. Sorry, Ryan. You are
> right. You are not good at communicating with third party developers.
> At least not in written form. You look like a very cool guy with a lot
> of personal charm. Maybe it works better in person. You should spend
> some time talking directly to developers in small groups. It might
> help you develop some canned responses that work.
>
> Here is a simple way this could have been prevented. If you had a
> developer relations person with experience and skills in dealing with
> third party developers, who have completely different motivations from
> in-house coders, he or she could have quietly passed around a draft of
> what you wanted to say. This would have gotten very strong negative
> reactions. You would have been able to reformulate it to strip out the
> implied threats and turn it into a positive roadmap. It could have
> been framed as "Here are some areas we promise to leave open for
> developers. If you work here, we will give you all kinds of extra
> support and promotion."
>
> Here is another simple way this could have been prevented. Create an
> advisory board of developers. Rotate people through it every 6-12
> months. Let them vet announcements in advance. Let them respond to the
> questions. It works in every other company I have worked with.
>
> Here is what could be done instead of these repeated bombs you keep
> dropping on the community. Give people a present. Announce that you
> will use some of your precious ad space to promote third party apps,
> and not just the ones with millions of dollars of VC who happen to
> work in your building. Find new ways to rev share with developers.
> Offer all expense paid trips to select developers to visit your office
> for a day to hang out. HOLD A DEVELOPERS CONFERENCE.
>
> There are many other things a good developer relations person could
> do. Talk to Guy. That is how he started for Apple.
>
> One last thing. Give this developer relations person a seat at the
> table when big decisions are made. I can read lots of signals, like
> this "high bar" nonsense, that there are negative attitudes inside
> Twitter towards developers. They are a pain in the ass. Yes. But they
> do hundreds of millions of dollars in development and promotion for
> you for free. Hire someone good for $100K+. Give them a million dollar
> budget to really take care of developers and run conferences and get
> togethers around the world. It will pay off many times over.
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>



-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Twitter List

[Tim Grant]

Is there anyone that can help me with the Twitter API?
I am creating an app with loads of info for users, but I would love to
include a screen that displays the tweets of lists that I have
created. It's not a place for users to post their own tweets, just a
reader. The user would first see a screen of the possible lists to
read, then display the chosen list. It would be so simple if it were a
simple URL of that page but it's not. Id like it to display similar to
twitters mobil app for lists; the tweet'ers aviator, tweet, and
timeline. RSS doesn't fit the bill for the look I want.  Looking for
the exact look the twitter app displays for a given list, thats it.
It seems like it should be simple coding but I have not been able to
find the answer.
Anyone have this expertise?

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] API - Get total count of hashtag usage

[JC]

If possible, what is the best approach to getting a total count of a
specific hashtag used.  I'm looking to build an app leveraging the API
that helps me get to this data.  I've seen the search api through
"search.twitter.com" but it filters users out it appears.  It doesn't
look I can get to this total through the streaming API or from what
I've seen.  I appreciate any help.  Thanks.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] twurl block is sending 502 even when it succeeds

[Thomas Woolway]

Hi Matt,

We've been seeing this for a while - the block and report spam calls always
return 502s (with a full page of HTML), even though they actually succeed.
This doesn't seem to be tied into the stability of the rest of the API. This
is happening across all of our clients, including those that use .xml and
.json resources.

Any chance that you could have a look into this? I can provide you with more
information if required,

Best,

Tom

On Tue, Jan 4, 2011 at 7:00 PM, Matt Harris wrote:

> Hi TjL,
>
> The API can occasionally return a Twitter Over Capacity error when the site
> is experiencing a lot traffic. If this happens waiting a little white and
> trying the request again will work.
>
> I notice you are using a variable for the screen_name. Is this being set
> correctly in your environment?
>
> Best
> @themattharris
> Developer Advocate, Twitter
> http://twitter.com/themattharris
>
>
>
> On Thu, Dec 30, 2010 at 2:34 PM, TJ Luoma  wrote:
>
>> I am trying to block users on the command line like this:
>>
>>twurl -t -d "screen_name=$1" "/1/blocks/create.xml"
>>
>> I am consistently getting
>>
>> -> "HTTP/1.1 502 Bad Gateway\r\n"
>>
>> as a response to this (Twitter Over Capacity) even when it works
>> (verified via API and via website)
>>
>> Is this why so few 3rd party apps can successfully block? Because the
>> API gives bad information? I've had to follow every blocks/create with
>> a blocks/exists to see if it really worked or not.
>>
>> TjL
>>
>> --
>> Twitter developer documentation and resources: http://dev.twitter.com/doc
>> API updates via Twitter: http://twitter.com/twitterapi
>> Issues/Enhancements Tracker:
>> http://code.google.com/p/twitter-api/issues/list
>> Change your membership to this group:
>> http://groups.google.com/group/twitter-development-talk
>>
>
>  --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Publish some Plug and Play CSS in the Interest of Consistency

[Whonew]

As someone who has been working on a new application for while now and
who hopes to release it shortly I am following the new terms of
service debate closely.

In the mean-time, I have a suggestion:

If Twitter is looking for consistency in the presentation of Tweets,
why not publish some CSS that developers can just plug into their apps
and know that they will have a Twitter-approved look and feel?


Thanks to Twitter and to all the developers for this forum.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: consistency and ecosystem opportunities

[Dewald Pretorius]

Taylor,

Would you mind taking a stab at clarifying Section 5.E of the new TOS,
which reads, "You may not use Twitter Content or other data collected
from end users of your Client to create or maintain a separate status
update or social network database or service."

It appears to say that a Client is not allowed to offer its users the
ability to create status updates on other services (StatusNet,
Facebook, etc.). Had it not been for the "or other data collected from
end users" I would have interpreted it that one cannot use any Twitter
Content (user data and tweets obtained via the Twitter API) and feed
that Twitter Data into other and/or competing social network
platforms. But, "or other data collected from end users" seems to
suggest that one cannot so much as offer any support for any other and/
or competing social network platform. Meaning, if you have a Client,
you can support Twitter OR Everything Else, not both.


On Mar 14, 11:12 am, Taylor Singletary 
wrote:
> Hi Adam,
>
> Thanks for your comments as always. I can help clarify a bit around how
> clients will be held to higher standards.
>
> Criteria we may examine include: is the application in tune with the spirit
> of the developer guidelines? Does the application refrain from storing
> username & password if it's using xAuth? Are tweets displayed with the
> proper attribution? Are the actions presented for the tweet appropriate in
> respect to it being a tweet? Does the application frame portions of our
> mobile site? Does it store non-public user data in a public way? Does the
> application provide a privacy policy? Is the client application paying for
> installation on mobile carriers?
>
> The new terms also offer some examples that are reasonably specific:
>
>
>
>
>
> >> A. Your Client must use the Twitter API as the sole source for features
> >> that are substantially similar to functionality offered by Twitter. Some
> >> examples include trending topics, who to follow, and suggested user lists.
>
> >  B. You may not pay, or offer to pay, third parties for distribution of
> >> your Client. This includes offering compensation for downloads (other than
> >> transactional fees), pre-installations, or other mechanisms of traffic
> >> acquisition.
>
> >  C. Your Client cannot frame or otherwise reproduce significant portions of
> >> the Twitter service. You should display Twitter Content from the Twitter
> >> API.
>
> > D. Do not store non-public user profile data or content.
>
> > E. You may not use Twitter Content or other data collected from end users
> >> of your Client to create or maintain a separate status update or social
> >> network database or service
>
> Using a Twitter client is like using an extension of Twitter, and though the
> user interfaces may change we want to ensure that the user experience is
> consistent, whether it's consistency in the actions a user can perform with
> a Tweet, the way their private information is treated, or how slowly,
> quickly, and with what tact advertising flows or does not flow through the
> network.
>
> Taylor
>
> On Sun, Mar 13, 2011 at 9:55 PM, Adam Green <140...@gmail.com> wrote:
> > Yes! Transparency!  That is what we are really craving. That is the subtext
> > for every developer responding to this thread. What we all want is
> > transparency about being shut down. Why does Twitter "revoke literally
> > hundreds of API tokens / apps a week" as Ryan said? Is it for something
> > obvious, like pumping out thousand of spam tweets or abusive follows, or is
> > it for something innocent, like not putting the right text on a tweet
> > button? I have never seen a description of an app that was blocked, except
> > for a few loons like Edward H. What if you told us about apps that get
> > blocked as examples, and explain what they did wrong? You don't even have to
> > identify them by name. Just explain exactly what type of transgressions are
> > causing rejection. That could calm people down.
>
> > Who doesn't meet the "high bar" and why? I know "high bar" has a lot of
> > meaning to you Twitter guys, since you all use the same term (a real example
> > of groupthink, BTW), but it means nothing to us. Tell us where this high bar
> > is exactly, by showing examples of not reaching it. Then we can learn and
> > improve, rather than guessing at what you mean.
>
> > Nobody here would bitch and moan if they didn't really want to learn
> > something. Please, help us by giving us examples.
>
> > On Mon, Mar 14, 2011 at 12:07 AM, Matt Harris  wrote:
>
> >> Innovation and development with the APIs are not being prevented. There
> >> have always been guidelines, and rules of the road so we all know what is
> >> and isn't allowed.
>
> >> If you build a client you are touching the majority of Twitter features.
> >> The APIs allow you to do this, and Twitter and your users trust you to use
> >> them in the way the terms or service allow. The high bar covers your use of
> >> these methods, and how you present inf

Re: [twitter-dev] Re: consistency and ecosystem opportunities

[Adam Green]

But you will allow it, right? Even if it is thinking small, it will not be
blocked? That is our problem. We can't separate business advice from a
warning to prepare to be cut off. We can't help watching the hand that holds
the kill switch. It makes it hard to hear what you say. Have patience, and
keep explaining please. If something will not cause a ban, then say this
explicitly to us. Don't just think it was implied.

On Mon, Mar 14, 2011 at 11:20 AM, Raffi Krikorian  wrote:

> my statement here was not providing "small" on the size of the company, but
> rather, "small" on the size of the idea. to re-iterate, making a piece of
> software that simply renders home_timeline is thinking too small.
>
>
> On Sun, Mar 13, 2011 at 6:21 PM, Lil Peck  wrote:
>
>> On Sun, Mar 13, 2011 at 7:45 PM, @siculars  wrote:
>> > @raffi @rsarver, I wrote up my two cents earlier,
>> > http://siculars.posterous.com/twitter-monoculture. I just don't
>> > appreciate the direction you all are going in. @raffi, I spoke with
>> > you at the CU recruiting event a few weeks back and I got to tell you
>> > that if I were asked I would tell those kids to reconsider working at
>> > twitter and possibly consider a Twitter competitor. you say "building
>> > clients is ... Thinking too small" I would say your policy change is
>> > thinking small and alienating your ardent supporters.
>> >
>>
>> To which I would add, what is Twitter to arbitrate that which is and
>> is not "too small?" Has Twitter subscribed to the fallacious "bigger
>> is always better" philosophy?
>>
>> How small is too small?
>>
>> Less than $25 million in startup funds?
>>
>> OR
>>
>> One creative, fun loving person and their sweat equity?
>>
>> --
>> Twitter developer documentation and resources: http://dev.twitter.com/doc
>> API updates via Twitter: http://twitter.com/twitterapi
>> Issues/Enhancements Tracker:
>> http://code.google.com/p/twitter-api/issues/list
>> Change your membership to this group:
>> http://groups.google.com/group/twitter-development-talk
>>
>
>
>
> --
> Raffi Krikorian
> Twitter, Application Services
> http://twitter.com/raffi
>
>
>  --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>



-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Re: consistency and ecosystem opportunities

[Raffi Krikorian]

my statement here was not providing "small" on the size of the company, but
rather, "small" on the size of the idea. to re-iterate, making a piece of
software that simply renders home_timeline is thinking too small.

On Sun, Mar 13, 2011 at 6:21 PM, Lil Peck  wrote:

> On Sun, Mar 13, 2011 at 7:45 PM, @siculars  wrote:
> > @raffi @rsarver, I wrote up my two cents earlier,
> > http://siculars.posterous.com/twitter-monoculture. I just don't
> > appreciate the direction you all are going in. @raffi, I spoke with
> > you at the CU recruiting event a few weeks back and I got to tell you
> > that if I were asked I would tell those kids to reconsider working at
> > twitter and possibly consider a Twitter competitor. you say "building
> > clients is ... Thinking too small" I would say your policy change is
> > thinking small and alienating your ardent supporters.
> >
>
> To which I would add, what is Twitter to arbitrate that which is and
> is not "too small?" Has Twitter subscribed to the fallacious "bigger
> is always better" philosophy?
>
> How small is too small?
>
> Less than $25 million in startup funds?
>
> OR
>
> One creative, fun loving person and their sweat equity?
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>



-- 
Raffi Krikorian
Twitter, Application Services
http://twitter.com/raffi

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: Signature generation issue

[lappynet]

cURL... I've heard about this, but I don't really know about it. Is
there a windows version as I don't have access to other OSs at work
(*sigh*)?

On Mar 14, 2:18 pm, Taylor Singletary 
wrote:
> Hi Georgina,
>
> Everything appears correct with your base string for this step.
>
> Are you performing this operation through a HTTP proxy of any kind? Have you
> tried producing a valid OAuth header and executed it in curl (without having
> "executed it" in C# first)? I'm not familiar with C#'s HTTP request
> libraries and the configuration options available to you in it.
>
> We were having an issue with occasionally hanging connections recently and
> it's possible that it may be related -- but if that's the case, you
> shouldn't have it occur to you every time -- it would be one out of X times.
>
> I'm curious where the connection is hanging -- while you are sending HTTP
> request headers or when your HTTP client is awaiting a response?
>
> Thanks,
> Taylor
>
>
>
>
>
>
>
> On Mon, Mar 14, 2011 at 7:02 AM, lappynet  wrote:
> > Hi
>
> > I'm using C#.NET to produce an oob client. I've fallen at the first
> > hurdle though as I'm failing to make the token request.
>
> > I've gone through many iterations, and am no longer receiving a 417,
> > 404, or 401. This is very positive! Now my application hangs whilst
> > waiting for a response from twitter. (I left it running for an hour
> > over lunch and still nothing happened, and the code didn't appear to
> > want to step through.)
>
> > I've tried with the values detailed in the documentation to have a
> > look at the variables that have been produced from them in my
> > algorithm. I think that I've traced it down to being the way I
> > generate the signature string:
>
> > string signingKey = Uri.EscapeDataString(ConsumerSecret) + "&";
> > HMACSHA1 hasher = new HMACSHA1(new
> > ASCIIEncoding().GetBytes(signingKey));
> > string signatureString = Convert.ToBase64String(hasher.ComputeHash(new
> > ASCIIEncoding().GetBytes(baseString)));
>
> > My base string is:
>
> > POST&https%3A%2F%2Fapi.twitter.com%2Foauth
> > %2Frequest_token&oauth_callback%3Doob%26oauth_consumer_key%XXX
> > %26oauth_nonce%3DNjM0MzU3MDgxMDEyMDcwODkw%26oauth_signature_method
> > %3DHMAC-SHA1%26oauth_timestamp%3D1300111301%26oauth_version%3D1.0
>
> > Any pointers as to where I may be going wrong?
>
> > Thanks in advance
> > Georgina
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Please hire a developer relations manager

[Adam Green]

Matt and Taylor do a great job of answering technical questions and being a
liason with engineers on developers behalf. That is a technical task. They
do it well.

A developer relations manager's job is to create and manage programs that
reach out to developers, make sure real docs are produced, provide business
support (ads, trips, rev share, etc.), and run small and large events that
help build a community of passionate developers around a product. It is a
completely different job from what Matt and Taylor do. I hate to use the P
word with this group, but it is really public relations aimed at developers.
it is not just business relations, because many developers aren't
businesses, but they contribute greatly to Twitter's growth. A developer
relations manager would talk to devs constantly and bring back this feedback
to be applied against future communications.

Objectively, based on the results here and in the tech press, nobody  could
claim this last communication was a success. Right? Whatever was meant and
said, it was a disaster. A developer relations manager who was given a real
budget and some say in communications would have avoided this.

On Mon, Mar 14, 2011 at 10:13 AM, Tom van der Woerdt  wrote:

> Isn't what you are describing the task of a developer advocate, Taylor
> Singletary and Matt Harris (and others?)?
>
> Tom
>
>
>
> On 3/14/11 2:44 PM, Adam Green wrote:
>
>> First of all, I honestly believe that Twitter HQ values developers and
>> appreciates their contribution. That is why I decided to devote myself
>> to this area a couple of years ago. I was amazed that when a dev
>> reported a problem the engineer responsible replied here and tried to
>> solve it. That is better than any big product I know of today. That is
>> why you have so many developers putting in all this work.
>>
>> I also believe that the last few announcements from Ryan and others
>> have been the worst examples of third party developer management I
>> have seen in 30 years in this business. I can see what Ryan wanted to
>> accomplish in his latest message. He wanted to provide guidance. He
>> ended up telling us that Twitter no longer wanted anyone to build
>> clients, didn't explain clearly what a "client" meant to him, and
>> pointed out that hundreds of apps that fail to meet his undefined
>> "high bar" were cut off every week. Not good. Sorry, Ryan. You are
>> right. You are not good at communicating with third party developers.
>> At least not in written form. You look like a very cool guy with a lot
>> of personal charm. Maybe it works better in person. You should spend
>> some time talking directly to developers in small groups. It might
>> help you develop some canned responses that work.
>>
>> Here is a simple way this could have been prevented. If you had a
>> developer relations person with experience and skills in dealing with
>> third party developers, who have completely different motivations from
>> in-house coders, he or she could have quietly passed around a draft of
>> what you wanted to say. This would have gotten very strong negative
>> reactions. You would have been able to reformulate it to strip out the
>> implied threats and turn it into a positive roadmap. It could have
>> been framed as "Here are some areas we promise to leave open for
>> developers. If you work here, we will give you all kinds of extra
>> support and promotion."
>>
>> Here is another simple way this could have been prevented. Create an
>> advisory board of developers. Rotate people through it every 6-12
>> months. Let them vet announcements in advance. Let them respond to the
>> questions. It works in every other company I have worked with.
>>
>> Here is what could be done instead of these repeated bombs you keep
>> dropping on the community. Give people a present. Announce that you
>> will use some of your precious ad space to promote third party apps,
>> and not just the ones with millions of dollars of VC who happen to
>> work in your building. Find new ways to rev share with developers.
>> Offer all expense paid trips to select developers to visit your office
>> for a day to hang out. HOLD A DEVELOPERS CONFERENCE.
>>
>> There are many other things a good developer relations person could
>> do. Talk to Guy. That is how he started for Apple.
>>
>> One last thing. Give this developer relations person a seat at the
>> table when big decisions are made. I can read lots of signals, like
>> this "high bar" nonsense, that there are negative attitudes inside
>> Twitter towards developers. They are a pain in the ass. Yes. But they
>> do hundreds of millions of dollars in development and promotion for
>> you for free. Hire someone good for $100K+. Give them a million dollar
>> budget to really take care of developers and run conferences and get
>> togethers around the world. It will pay off many times over.
>>
>>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitt

[twitter-dev] Re: Signature generation issue

[lappynet]

Yeah, I've used that tool with my real full base string and everything
appears OK. Thanks for the pointer though, I'm sure that tool will
come in handy again. :)

I have seen some blog posts issuing warnings over .NET's various ways
of RFC3986 encoding, but this doesn't appear to be the issue here...
I'll look into the hashing and base 64 encoding some more...

(I've been working through this for almost two days now. Although this
is the stuff I love doing in programming, it would be really nice if
twitter could improve/make some documentation for oob.)

On Mar 14, 2:25 pm, Tom van der Woerdt  wrote:
> No, actually, it was my fault: it wasn't a %26, but a %3D.
>
> Oops! Base string is fine.
>
> Tom
>
> On 3/14/11 3:21 PM, Taylor Singletary wrote:
>
>
>
>
>
>
>
> > Wow, my blindness to signature base string foo this morning is
> > humbling. Thanks Tom.
>
> > On Mon, Mar 14, 2011 at 7:15 AM, Tom van der Woerdt  > > wrote:
>
> >     After fixing the basic parts of your signature (please don't ever
> >     replace %26 with only a %, it screws up the encoding) and checking
> >     athttp://quonos.nl/oauthTester/, I got :
>
> >     *Bad sorting!*
> >     All Base String parameters (query and POST parameters) must be
> >     sorted alphabetically.
>
> >     Tom
>
> >     On 3/14/11 3:02 PM, lappynet wrote:
> >>     Hi
>
> >>     I'm using C#.NET to produce an oob client. I've fallen at the first
> >>     hurdle though as I'm failing to make the token request.
>
> >>     I've gone through many iterations, and am no longer receiving a 417,
> >>     404, or 401. This is very positive! Now my application hangs whilst
> >>     waiting for a response from twitter. (I left it running for an hour
> >>     over lunch and still nothing happened, and the code didn't appear to
> >>     want to step through.)
>
> >>     I've tried with the values detailed in the documentation to have a
> >>     look at the variables that have been produced from them in my
> >>     algorithm. I think that I've traced it down to being the way I
> >>     generate the signature string:
>
> >>     string signingKey = Uri.EscapeDataString(ConsumerSecret) + "&";
> >>     HMACSHA1 hasher = new HMACSHA1(new
> >>     ASCIIEncoding().GetBytes(signingKey));
> >>     string signatureString = Convert.ToBase64String(hasher.ComputeHash(new
> >>     ASCIIEncoding().GetBytes(baseString)));
>
> >>     My base string is:
>
> >>     POST&https%3A%2F%2Fapi.twitter.com  %2Foauth
> >>     %2Frequest_token&oauth_callback%3Doob%26oauth_consumer_key%XXX
> >>     %26oauth_nonce%3DNjM0MzU3MDgxMDEyMDcwODkw%26oauth_signature_method
> >>     %3DHMAC-SHA1%26oauth_timestamp%3D1300111301%26oauth_version%3D1.0
>
> >>     Any pointers as to where I may be going wrong?
>
> >>     Thanks in advance
> >>     Georgina
>
> >     --
> >     Twitter developer documentation and resources:
> >    http://dev.twitter.com/doc
> >     API updates via Twitter:http://twitter.com/twitterapi
> >     Issues/Enhancements Tracker:
> >    http://code.google.com/p/twitter-api/issues/list
> >     Change your membership to this group:
> >    http://groups.google.com/group/twitter-development-talk
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Signature generation issue

[Umashankar Das]

I guess we're seeing that the effects of the announcement of last weekend is
not limited to the 3rd party developers but also to the people working in
twitter :).

Just a joke Taylor, Have a Good day :).

Cheers
Umashankar Das

On Mon, Mar 14, 2011 at 7:51 PM, Taylor Singletary <
taylorsinglet...@twitter.com> wrote:

> Wow, my blindness to signature base string foo this morning is humbling.
> Thanks Tom.
>
>
> On Mon, Mar 14, 2011 at 7:15 AM, Tom van der Woerdt  wrote:
>
>>  After fixing the basic parts of your signature (please don't ever replace
>> %26 with only a %, it screws up the encoding) and checking at
>> http://quonos.nl/oauthTester/, I got :
>>
>> *Bad sorting!*
>> All Base String parameters (query and POST parameters) must be sorted
>> alphabetically.
>>
>>
>> Tom
>>
>>
>>
>> On 3/14/11 3:02 PM, lappynet wrote:
>>
>> Hi
>>
>> I'm using C#.NET to produce an oob client. I've fallen at the first
>> hurdle though as I'm failing to make the token request.
>>
>> I've gone through many iterations, and am no longer receiving a 417,
>> 404, or 401. This is very positive! Now my application hangs whilst
>> waiting for a response from twitter. (I left it running for an hour
>> over lunch and still nothing happened, and the code didn't appear to
>> want to step through.)
>>
>> I've tried with the values detailed in the documentation to have a
>> look at the variables that have been produced from them in my
>> algorithm. I think that I've traced it down to being the way I
>> generate the signature string:
>>
>> string signingKey = Uri.EscapeDataString(ConsumerSecret) + "&";
>> HMACSHA1 hasher = new HMACSHA1(new
>> ASCIIEncoding().GetBytes(signingKey));
>> string signatureString = Convert.ToBase64String(hasher.ComputeHash(new
>> ASCIIEncoding().GetBytes(baseString)));
>>
>> My base string is:
>>
>> POST&https%3A%2F%2Fapi.twitter.com%2Foauth
>> %2Frequest_token&oauth_callback%3Doob%26oauth_consumer_key%XXX
>> %26oauth_nonce%3DNjM0MzU3MDgxMDEyMDcwODkw%26oauth_signature_method
>> %3DHMAC-SHA1%26oauth_timestamp%3D1300111301%26oauth_version%3D1.0
>>
>> Any pointers as to where I may be going wrong?
>>
>> Thanks in advance
>> Georgina
>>
>>
>>
>>  --
>> Twitter developer documentation and resources: http://dev.twitter.com/doc
>> API updates via Twitter: http://twitter.com/twitterapi
>> Issues/Enhancements Tracker:
>> http://code.google.com/p/twitter-api/issues/list
>> Change your membership to this group:
>> http://groups.google.com/group/twitter-development-talk
>>
>
>  --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Signature generation issue

[Tom van der Woerdt]

No, actually, it was my fault: it wasn't a %26, but a %3D.

Oops! Base string is fine.

Tom


On 3/14/11 3:21 PM, Taylor Singletary wrote:
Wow, my blindness to signature base string foo this morning is 
humbling. Thanks Tom.


On Mon, Mar 14, 2011 at 7:15 AM, Tom van der Woerdt > wrote:


After fixing the basic parts of your signature (please don't ever
replace %26 with only a %, it screws up the encoding) and checking
at http://quonos.nl/oauthTester/, I got :

*Bad sorting!*
All Base String parameters (query and POST parameters) must be
sorted alphabetically.


Tom



On 3/14/11 3:02 PM, lappynet wrote:

Hi

I'm using C#.NET to produce an oob client. I've fallen at the first
hurdle though as I'm failing to make the token request.

I've gone through many iterations, and am no longer receiving a 417,
404, or 401. This is very positive! Now my application hangs whilst
waiting for a response from twitter. (I left it running for an hour
over lunch and still nothing happened, and the code didn't appear to
want to step through.)

I've tried with the values detailed in the documentation to have a
look at the variables that have been produced from them in my
algorithm. I think that I've traced it down to being the way I
generate the signature string:

string signingKey = Uri.EscapeDataString(ConsumerSecret) + "&";
HMACSHA1 hasher = new HMACSHA1(new
ASCIIEncoding().GetBytes(signingKey));
string signatureString = Convert.ToBase64String(hasher.ComputeHash(new
ASCIIEncoding().GetBytes(baseString)));

My base string is:

POST&https%3A%2F%2Fapi.twitter.com  %2Foauth
%2Frequest_token&oauth_callback%3Doob%26oauth_consumer_key%XXX
%26oauth_nonce%3DNjM0MzU3MDgxMDEyMDcwODkw%26oauth_signature_method
%3DHMAC-SHA1%26oauth_timestamp%3D1300111301%26oauth_version%3D1.0

Any pointers as to where I may be going wrong?

Thanks in advance
Georgina



-- 
Twitter developer documentation and resources:

http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk


--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: 
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Signature generation issue

[Taylor Singletary]

Wow, my blindness to signature base string foo this morning is humbling.
Thanks Tom.

On Mon, Mar 14, 2011 at 7:15 AM, Tom van der Woerdt  wrote:

>  After fixing the basic parts of your signature (please don't ever replace
> %26 with only a %, it screws up the encoding) and checking at
> http://quonos.nl/oauthTester/, I got :
>
> *Bad sorting!*
> All Base String parameters (query and POST parameters) must be sorted
> alphabetically.
>
>
> Tom
>
>
>
> On 3/14/11 3:02 PM, lappynet wrote:
>
> Hi
>
> I'm using C#.NET to produce an oob client. I've fallen at the first
> hurdle though as I'm failing to make the token request.
>
> I've gone through many iterations, and am no longer receiving a 417,
> 404, or 401. This is very positive! Now my application hangs whilst
> waiting for a response from twitter. (I left it running for an hour
> over lunch and still nothing happened, and the code didn't appear to
> want to step through.)
>
> I've tried with the values detailed in the documentation to have a
> look at the variables that have been produced from them in my
> algorithm. I think that I've traced it down to being the way I
> generate the signature string:
>
> string signingKey = Uri.EscapeDataString(ConsumerSecret) + "&";
> HMACSHA1 hasher = new HMACSHA1(new
> ASCIIEncoding().GetBytes(signingKey));
> string signatureString = Convert.ToBase64String(hasher.ComputeHash(new
> ASCIIEncoding().GetBytes(baseString)));
>
> My base string is:
>
> POST&https%3A%2F%2Fapi.twitter.com%2Foauth
> %2Frequest_token&oauth_callback%3Doob%26oauth_consumer_key%XXX
> %26oauth_nonce%3DNjM0MzU3MDgxMDEyMDcwODkw%26oauth_signature_method
> %3DHMAC-SHA1%26oauth_timestamp%3D1300111301%26oauth_version%3D1.0
>
> Any pointers as to where I may be going wrong?
>
> Thanks in advance
> Georgina
>
>
>
>  --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: Signature generation issue

[lappynet]

Thanks, I'll take a look at the sorting.

I hadn't removed the 26 part, I think I deleted that along with by
consumer key for privacy by accident! I can assure you it is there
really. :)

On Mar 14, 2:15 pm, Tom van der Woerdt  wrote:
> After fixing the basic parts of your signature (please don't ever
> replace %26 with only a %, it screws up the encoding) and checking 
> athttp://quonos.nl/oauthTester/, I got :
>
> *Bad sorting!*
> All Base String parameters (query and POST parameters) must be sorted
> alphabetically.
>
> Tom
>
> On 3/14/11 3:02 PM, lappynet wrote:
>
>
>
>
>
>
>
> > Hi
>
> > I'm using C#.NET to produce an oob client. I've fallen at the first
> > hurdle though as I'm failing to make the token request.
>
> > I've gone through many iterations, and am no longer receiving a 417,
> > 404, or 401. This is very positive! Now my application hangs whilst
> > waiting for a response from twitter. (I left it running for an hour
> > over lunch and still nothing happened, and the code didn't appear to
> > want to step through.)
>
> > I've tried with the values detailed in the documentation to have a
> > look at the variables that have been produced from them in my
> > algorithm. I think that I've traced it down to being the way I
> > generate the signature string:
>
> > string signingKey = Uri.EscapeDataString(ConsumerSecret) + "&";
> > HMACSHA1 hasher = new HMACSHA1(new
> > ASCIIEncoding().GetBytes(signingKey));
> > string signatureString = Convert.ToBase64String(hasher.ComputeHash(new
> > ASCIIEncoding().GetBytes(baseString)));
>
> > My base string is:
>
> > POST&https%3A%2F%2Fapi.twitter.com%2Foauth
> > %2Frequest_token&oauth_callback%3Doob%26oauth_consumer_key%XXX
> > %26oauth_nonce%3DNjM0MzU3MDgxMDEyMDcwODkw%26oauth_signature_method
> > %3DHMAC-SHA1%26oauth_timestamp%3D1300111301%26oauth_version%3D1.0
>
> > Any pointers as to where I may be going wrong?
>
> > Thanks in advance
> > Georgina

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Signature generation issue

[Taylor Singletary]

Hi Georgina,

Everything appears correct with your base string for this step.

Are you performing this operation through a HTTP proxy of any kind? Have you
tried producing a valid OAuth header and executed it in curl (without having
"executed it" in C# first)? I'm not familiar with C#'s HTTP request
libraries and the configuration options available to you in it.

We were having an issue with occasionally hanging connections recently and
it's possible that it may be related -- but if that's the case, you
shouldn't have it occur to you every time -- it would be one out of X times.

I'm curious where the connection is hanging -- while you are sending HTTP
request headers or when your HTTP client is awaiting a response?

Thanks,
Taylor

On Mon, Mar 14, 2011 at 7:02 AM, lappynet  wrote:

> Hi
>
> I'm using C#.NET to produce an oob client. I've fallen at the first
> hurdle though as I'm failing to make the token request.
>
> I've gone through many iterations, and am no longer receiving a 417,
> 404, or 401. This is very positive! Now my application hangs whilst
> waiting for a response from twitter. (I left it running for an hour
> over lunch and still nothing happened, and the code didn't appear to
> want to step through.)
>
> I've tried with the values detailed in the documentation to have a
> look at the variables that have been produced from them in my
> algorithm. I think that I've traced it down to being the way I
> generate the signature string:
>
> string signingKey = Uri.EscapeDataString(ConsumerSecret) + "&";
> HMACSHA1 hasher = new HMACSHA1(new
> ASCIIEncoding().GetBytes(signingKey));
> string signatureString = Convert.ToBase64String(hasher.ComputeHash(new
> ASCIIEncoding().GetBytes(baseString)));
>
> My base string is:
>
> POST&https%3A%2F%2Fapi.twitter.com%2Foauth
> %2Frequest_token&oauth_callback%3Doob%26oauth_consumer_key%XXX
> %26oauth_nonce%3DNjM0MzU3MDgxMDEyMDcwODkw%26oauth_signature_method
> %3DHMAC-SHA1%26oauth_timestamp%3D1300111301%26oauth_version%3D1.0
>
> Any pointers as to where I may be going wrong?
>
> Thanks in advance
> Georgina
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Signature generation issue

[Tom van der Woerdt]

After fixing the basic parts of your signature (please don't ever 
replace %26 with only a %, it screws up the encoding) and checking at 
http://quonos.nl/oauthTester/, I got :


*Bad sorting!*
All Base String parameters (query and POST parameters) must be sorted 
alphabetically.



Tom



On 3/14/11 3:02 PM, lappynet wrote:

Hi

I'm using C#.NET to produce an oob client. I've fallen at the first
hurdle though as I'm failing to make the token request.

I've gone through many iterations, and am no longer receiving a 417,
404, or 401. This is very positive! Now my application hangs whilst
waiting for a response from twitter. (I left it running for an hour
over lunch and still nothing happened, and the code didn't appear to
want to step through.)

I've tried with the values detailed in the documentation to have a
look at the variables that have been produced from them in my
algorithm. I think that I've traced it down to being the way I
generate the signature string:

string signingKey = Uri.EscapeDataString(ConsumerSecret) + "&";
HMACSHA1 hasher = new HMACSHA1(new
ASCIIEncoding().GetBytes(signingKey));
string signatureString = Convert.ToBase64String(hasher.ComputeHash(new
ASCIIEncoding().GetBytes(baseString)));

My base string is:

POST&https%3A%2F%2Fapi.twitter.com%2Foauth
%2Frequest_token&oauth_callback%3Doob%26oauth_consumer_key%XXX
%26oauth_nonce%3DNjM0MzU3MDgxMDEyMDcwODkw%26oauth_signature_method
%3DHMAC-SHA1%26oauth_timestamp%3D1300111301%26oauth_version%3D1.0

Any pointers as to where I may be going wrong?

Thanks in advance
Georgina



--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Please hire a developer relations manager

[Tom van der Woerdt]

Isn't what you are describing the task of a developer advocate, Taylor 
Singletary and Matt Harris (and others?)?


Tom


On 3/14/11 2:44 PM, Adam Green wrote:

First of all, I honestly believe that Twitter HQ values developers and
appreciates their contribution. That is why I decided to devote myself
to this area a couple of years ago. I was amazed that when a dev
reported a problem the engineer responsible replied here and tried to
solve it. That is better than any big product I know of today. That is
why you have so many developers putting in all this work.

I also believe that the last few announcements from Ryan and others
have been the worst examples of third party developer management I
have seen in 30 years in this business. I can see what Ryan wanted to
accomplish in his latest message. He wanted to provide guidance. He
ended up telling us that Twitter no longer wanted anyone to build
clients, didn't explain clearly what a "client" meant to him, and
pointed out that hundreds of apps that fail to meet his undefined
"high bar" were cut off every week. Not good. Sorry, Ryan. You are
right. You are not good at communicating with third party developers.
At least not in written form. You look like a very cool guy with a lot
of personal charm. Maybe it works better in person. You should spend
some time talking directly to developers in small groups. It might
help you develop some canned responses that work.

Here is a simple way this could have been prevented. If you had a
developer relations person with experience and skills in dealing with
third party developers, who have completely different motivations from
in-house coders, he or she could have quietly passed around a draft of
what you wanted to say. This would have gotten very strong negative
reactions. You would have been able to reformulate it to strip out the
implied threats and turn it into a positive roadmap. It could have
been framed as "Here are some areas we promise to leave open for
developers. If you work here, we will give you all kinds of extra
support and promotion."

Here is another simple way this could have been prevented. Create an
advisory board of developers. Rotate people through it every 6-12
months. Let them vet announcements in advance. Let them respond to the
questions. It works in every other company I have worked with.

Here is what could be done instead of these repeated bombs you keep
dropping on the community. Give people a present. Announce that you
will use some of your precious ad space to promote third party apps,
and not just the ones with millions of dollars of VC who happen to
work in your building. Find new ways to rev share with developers.
Offer all expense paid trips to select developers to visit your office
for a day to hang out. HOLD A DEVELOPERS CONFERENCE.

There are many other things a good developer relations person could
do. Talk to Guy. That is how he started for Apple.

One last thing. Give this developer relations person a seat at the
table when big decisions are made. I can read lots of signals, like
this "high bar" nonsense, that there are negative attitudes inside
Twitter towards developers. They are a pain in the ass. Yes. But they
do hundreds of millions of dollars in development and promotion for
you for free. Hire someone good for $100K+. Give them a million dollar
budget to really take care of developers and run conferences and get
togethers around the world. It will pay off many times over.



--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Re: consistency and ecosystem opportunities

[Taylor Singletary]

Hi Adam,

Thanks for your comments as always. I can help clarify a bit around how
clients will be held to higher standards.

Criteria we may examine include: is the application in tune with the spirit
of the developer guidelines? Does the application refrain from storing
username & password if it's using xAuth? Are tweets displayed with the
proper attribution? Are the actions presented for the tweet appropriate in
respect to it being a tweet? Does the application frame portions of our
mobile site? Does it store non-public user data in a public way? Does the
application provide a privacy policy? Is the client application paying for
installation on mobile carriers?

The new terms also offer some examples that are reasonably specific:

>
>> A. Your Client must use the Twitter API as the sole source for features
>> that are substantially similar to functionality offered by Twitter. Some
>> examples include trending topics, who to follow, and suggested user lists.
>
>  B. You may not pay, or offer to pay, third parties for distribution of
>> your Client. This includes offering compensation for downloads (other than
>> transactional fees), pre-installations, or other mechanisms of traffic
>> acquisition.
>
>  C. Your Client cannot frame or otherwise reproduce significant portions of
>> the Twitter service. You should display Twitter Content from the Twitter
>> API.
>
> D. Do not store non-public user profile data or content.
>
> E. You may not use Twitter Content or other data collected from end users
>> of your Client to create or maintain a separate status update or social
>> network database or service
>
>
Using a Twitter client is like using an extension of Twitter, and though the
user interfaces may change we want to ensure that the user experience is
consistent, whether it's consistency in the actions a user can perform with
a Tweet, the way their private information is treated, or how slowly,
quickly, and with what tact advertising flows or does not flow through the
network.

Taylor


On Sun, Mar 13, 2011 at 9:55 PM, Adam Green <140...@gmail.com> wrote:

> Yes! Transparency!  That is what we are really craving. That is the subtext
> for every developer responding to this thread. What we all want is
> transparency about being shut down. Why does Twitter "revoke literally
> hundreds of API tokens / apps a week" as Ryan said? Is it for something
> obvious, like pumping out thousand of spam tweets or abusive follows, or is
> it for something innocent, like not putting the right text on a tweet
> button? I have never seen a description of an app that was blocked, except
> for a few loons like Edward H. What if you told us about apps that get
> blocked as examples, and explain what they did wrong? You don't even have to
> identify them by name. Just explain exactly what type of transgressions are
> causing rejection. That could calm people down.
>
> Who doesn't meet the "high bar" and why? I know "high bar" has a lot of
> meaning to you Twitter guys, since you all use the same term (a real example
> of groupthink, BTW), but it means nothing to us. Tell us where this high bar
> is exactly, by showing examples of not reaching it. Then we can learn and
> improve, rather than guessing at what you mean.
>
> Nobody here would bitch and moan if they didn't really want to learn
> something. Please, help us by giving us examples.
>
> On Mon, Mar 14, 2011 at 12:07 AM, Matt Harris  wrote:
>
>> Innovation and development with the APIs are not being prevented. There
>> have always been guidelines, and rules of the road so we all know what is
>> and isn't allowed.
>>
>> If you build a client you are touching the majority of Twitter features.
>> The APIs allow you to do this, and Twitter and your users trust you to use
>> them in the way the terms or service allow. The high bar covers your use of
>> these methods, and how you present information back to the user. The ToS
>> covers this but there are always situations where the application of them
>> isn't clear. — Let's have those discussions with your use cases applied for
>> the benefit of everyone.
>>
>> The direction, and motivation here is transparency. You asked us what it
>> looks like from the inside out. It can be uncomfortable, sure, but I believe
>> it's better we all know how it looks on both sides.
>>
>> Without us saying how we see it, how can we have these discussions?
>>
>> @themattharris
>>
>>
>> On Mar 13, 2011, at 20:21, Lil Peck  wrote:
>>
>> > On Sun, Mar 13, 2011 at 7:45 PM, @siculars  wrote:
>> >> @raffi @rsarver, I wrote up my two cents earlier,
>> >> http://siculars.posterous.com/twitter-monoculture. I just don't
>> >> appreciate the direction you all are going in. @raffi, I spoke with
>> >> you at the CU recruiting event a few weeks back and I got to tell you
>> >> that if I were asked I would tell those kids to reconsider working at
>> >> twitter and possibly consider a Twitter competitor. you say "building
>> >> clients is ... Thinking too small" I

Re: [twitter-dev] Please hire a developer relations manager

[Peter Tomtin]

The TOS defines a client clearly:

Your Service may be an application or client that provides major
components of a Twitter-like end user experience (a "Client"). An
example of a Client is a downloadable application that displays user
timelines and allows users to create and search for tweets.

Your primary suggestion of being less than forthright and clear with
client developers would make matters worse.

Peter



On Mon, Mar 14, 2011 at 6:44 AM, Adam Green <140...@gmail.com> wrote:
>
> First of all, I honestly believe that Twitter HQ values developers and
> appreciates their contribution. That is why I decided to devote myself
> to this area a couple of years ago. I was amazed that when a dev
> reported a problem the engineer responsible replied here and tried to
> solve it. That is better than any big product I know of today. That is
> why you have so many developers putting in all this work.
>
> I also believe that the last few announcements from Ryan and others
> have been the worst examples of third party developer management I
> have seen in 30 years in this business. I can see what Ryan wanted to
> accomplish in his latest message. He wanted to provide guidance. He
> ended up telling us that Twitter no longer wanted anyone to build
> clients, didn't explain clearly what a "client" meant to him, and
> pointed out that hundreds of apps that fail to meet his undefined
> "high bar" were cut off every week. Not good. Sorry, Ryan. You are
> right. You are not good at communicating with third party developers.
> At least not in written form. You look like a very cool guy with a lot
> of personal charm. Maybe it works better in person. You should spend
> some time talking directly to developers in small groups. It might
> help you develop some canned responses that work.
>
> Here is a simple way this could have been prevented. If you had a
> developer relations person with experience and skills in dealing with
> third party developers, who have completely different motivations from
> in-house coders, he or she could have quietly passed around a draft of
> what you wanted to say. This would have gotten very strong negative
> reactions. You would have been able to reformulate it to strip out the
> implied threats and turn it into a positive roadmap. It could have
> been framed as "Here are some areas we promise to leave open for
> developers. If you work here, we will give you all kinds of extra
> support and promotion."
>
> Here is another simple way this could have been prevented. Create an
> advisory board of developers. Rotate people through it every 6-12
> months. Let them vet announcements in advance. Let them respond to the
> questions. It works in every other company I have worked with.
>
> Here is what could be done instead of these repeated bombs you keep
> dropping on the community. Give people a present. Announce that you
> will use some of your precious ad space to promote third party apps,
> and not just the ones with millions of dollars of VC who happen to
> work in your building. Find new ways to rev share with developers.
> Offer all expense paid trips to select developers to visit your office
> for a day to hang out. HOLD A DEVELOPERS CONFERENCE.
>
> There are many other things a good developer relations person could
> do. Talk to Guy. That is how he started for Apple.
>
> One last thing. Give this developer relations person a seat at the
> table when big decisions are made. I can read lots of signals, like
> this "high bar" nonsense, that there are negative attitudes inside
> Twitter towards developers. They are a pain in the ass. Yes. But they
> do hundreds of millions of dollars in development and promotion for
> you for free. Hire someone good for $100K+. Give them a million dollar
> budget to really take care of developers and run conferences and get
> togethers around the world. It will pay off many times over.
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Signature generation issue

[lappynet]

Hi

I'm using C#.NET to produce an oob client. I've fallen at the first
hurdle though as I'm failing to make the token request.

I've gone through many iterations, and am no longer receiving a 417,
404, or 401. This is very positive! Now my application hangs whilst
waiting for a response from twitter. (I left it running for an hour
over lunch and still nothing happened, and the code didn't appear to
want to step through.)

I've tried with the values detailed in the documentation to have a
look at the variables that have been produced from them in my
algorithm. I think that I've traced it down to being the way I
generate the signature string:

string signingKey = Uri.EscapeDataString(ConsumerSecret) + "&";
HMACSHA1 hasher = new HMACSHA1(new
ASCIIEncoding().GetBytes(signingKey));
string signatureString = Convert.ToBase64String(hasher.ComputeHash(new
ASCIIEncoding().GetBytes(baseString)));

My base string is:

POST&https%3A%2F%2Fapi.twitter.com%2Foauth
%2Frequest_token&oauth_callback%3Doob%26oauth_consumer_key%XXX
%26oauth_nonce%3DNjM0MzU3MDgxMDEyMDcwODkw%26oauth_signature_method
%3DHMAC-SHA1%26oauth_timestamp%3D1300111301%26oauth_version%3D1.0

Any pointers as to where I may be going wrong?

Thanks in advance
Georgina

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Please hire a developer relations manager

[Adam Green]

First of all, I honestly believe that Twitter HQ values developers and
appreciates their contribution. That is why I decided to devote myself
to this area a couple of years ago. I was amazed that when a dev
reported a problem the engineer responsible replied here and tried to
solve it. That is better than any big product I know of today. That is
why you have so many developers putting in all this work.

I also believe that the last few announcements from Ryan and others
have been the worst examples of third party developer management I
have seen in 30 years in this business. I can see what Ryan wanted to
accomplish in his latest message. He wanted to provide guidance. He
ended up telling us that Twitter no longer wanted anyone to build
clients, didn't explain clearly what a "client" meant to him, and
pointed out that hundreds of apps that fail to meet his undefined
"high bar" were cut off every week. Not good. Sorry, Ryan. You are
right. You are not good at communicating with third party developers.
At least not in written form. You look like a very cool guy with a lot
of personal charm. Maybe it works better in person. You should spend
some time talking directly to developers in small groups. It might
help you develop some canned responses that work.

Here is a simple way this could have been prevented. If you had a
developer relations person with experience and skills in dealing with
third party developers, who have completely different motivations from
in-house coders, he or she could have quietly passed around a draft of
what you wanted to say. This would have gotten very strong negative
reactions. You would have been able to reformulate it to strip out the
implied threats and turn it into a positive roadmap. It could have
been framed as "Here are some areas we promise to leave open for
developers. If you work here, we will give you all kinds of extra
support and promotion."

Here is another simple way this could have been prevented. Create an
advisory board of developers. Rotate people through it every 6-12
months. Let them vet announcements in advance. Let them respond to the
questions. It works in every other company I have worked with.

Here is what could be done instead of these repeated bombs you keep
dropping on the community. Give people a present. Announce that you
will use some of your precious ad space to promote third party apps,
and not just the ones with millions of dollars of VC who happen to
work in your building. Find new ways to rev share with developers.
Offer all expense paid trips to select developers to visit your office
for a day to hang out. HOLD A DEVELOPERS CONFERENCE.

There are many other things a good developer relations person could
do. Talk to Guy. That is how he started for Apple.

One last thing. Give this developer relations person a seat at the
table when big decisions are made. I can read lots of signals, like
this "high bar" nonsense, that there are negative attitudes inside
Twitter towards developers. They are a pain in the ass. Yes. But they
do hundreds of millions of dollars in development and promotion for
you for free. Hire someone good for $100K+. Give them a million dollar
budget to really take care of developers and run conferences and get
togethers around the world. It will pay off many times over.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] How to write a twitter API application without a site?

[Dims]

The system asks me to enter a web site to register an application and
states that this site should contain an application visitors should be
able to download. Is this requirement strict? What if I want to do
some private or corporate investigation on twitter data? How should I
act?

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: consistency and ecosystem opportunities

[Luca Filigheddu]

Ryan,
we read the updated API TOS and I believe those make a lot of sense,
can't see anything "unusual" or "concerning".

I can't see any issue that could affect us as Twimbow (web based
social media dashboard) since our mid-term roadmap is way more than a
"twitter client" but I can clearly see what you mean in terms of
"consistency". I tried myself many clients that were trying to use the
content coming from Twitter in the wrong way and trying to give a
guidance makes a lot of sense, imho.

That said, I think there is a lot of space for innovation in the
client space, too. There are lots of features that could be helpful
for users in order to get the most out of the huge amount of
information they deal with everyday and we are definitely looking
forward to adding them to Twimbow in the following versions. Most of
them are around filtering and categorizing, all aligned with your TOS,
of course.

Let's keep this conversation going, I think it is very useful for
everyone.

Best,

Luca Filigheddu
CEO, Twimbow
@filos 



-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: consistency and ecosystem opportunities

[Dewald Pretorius]

Sometimes it takes just a slightly different perspective for the sun
to raise its head above the horizon of the blatantly obvious. And
everything suddenly makes perfect sense.

In other news, Echofon Pro is a better iPhone client, IMHO.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Re: IPhone + Twitter + LinkedIn Error : Command /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/gcc-4.2 failed with exit code 1

[Bess Ho]

Congratulation. Are you planning to post photos than updating status on
Twitter, FB, & Linkedin at the same time?

On Mon, Mar 14, 2011 at 2:01 AM, Battan Amit  wrote:

> *Solved *
>
> solved now...I have given the same key and secret to both linkedin and
> twitter ..after changing them it works
> 
> AB
>
> On 14 March 2011 11:55, Battan Amit  wrote:
>
>> I done one thing that is ... I remove the library files of linkedin sdk..
>> and add the source files of it with oAuth files from twiiter sdk... then it
>> works ok for linkedin http://i.imgur.com/cXLXU.png
>> http://i.imgur.com/ntV9G.png then I integrate all twitter code then
>> project run ok without error but for twitter login interface it shows PAGE
>> NOT FOUND ..http://i.imgur.com/8a1ua.png
>>
>>
>> 
>> AB
>>
>>
>>
>>
>> On 12 March 2011 11:44, Bess  wrote:
>>
>>> First of all it is difficult to identify errors esp you don't have the
>>> source code. However the stockoverflow discussion was good enough to
>>> point out the general problems.
>>>
>>> ld: duplicate symbol _EstimateBas64EncodedDataSize in /Users/pratgupta/
>>> Desktop/Settinglinkedin/10_mar_butterfli/LinkedInClientLibrary/build/
>>> Debug-iphonesimulator/libLinkedInClientLibrary.a(Base64Transcoder.o)
>>> and /Users/pratgupta/Desktop/Settinglinkedin/10_mar_butterfli/Twitter
>>> +OAuth/Libraries & Headers/libOAuth.a(Base64Transcoder.o)
>>>
>>> Problem is: duplicate symbol
>>>
>>> It occurs on _EstimateBas64EncodedDataSize from LinkedinClientLibrary
>>> in libLinkedInClientLibrary.a(Base64Transcoder.o) and Twitter+OAuth in
>>> libOAuth.a(Base64Transcoder.o).
>>>
>>> Note: LinkedIn library and Ben Gottlieb's Twitter client include the
>>> same OAuthConsumer code. It is duplicated. libLinkedInClientLibrary
>>> and libOAuth both symbolicate the same method
>>> '_EstimateBas64EncodedDataSize'. Check your #imports.
>>>
>>> Just do a search within your Xcode project on
>>> _EstimateBas64EncodedDataSize. Find out where the duplicated methods.
>>> Determine which one you should remove.
>>>
>>> On Mar 11, 4:56 am, Battan Ror  wrote:
>>> > HI All
>>> >
>>> > I am using MGTwitterEngine oAuth and LinkedIn iOS sdk in my Iphone
>>> > application with facebook-ios-sdk
>>> >
>>> > TwitterEngine :https://github.com/bengottlieb/Twitter-OAuth-iPhone
>>> >
>>> > LinkedInIphone :https://github.com/ResultsDirect/LinkedIn-iPhone
>>> >
>>> > Both integrated well separately, But when I have used both in
>>> > application then error coming
>>> >
>>> > FB + Twitter = working well
>>> > FB + LinkedIn = Working Well
>>> > FB + Twitter + LinkedIn = Not Working
>>> >
>>> > and giving error
>>> >
>>> > Command /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/
>>> > bin/gcc-4.2 failed with exit code 1
>>> >
>>> > Please help me where I am wrong.
>>> >
>>> > Error Transcript Text File
>>> >
>>> > Build butterfli of project butterfli with configuration Debug
>>> >
>>> > Ld build/Debug-iphonesimulator/butterfli.app/butterfli normal i386
>>> > cd /Users/pratgupta/Desktop/Settinglinkedin/10_mar_butterfli
>>> > setenv MACOSX_DEPLOYMENT_TARGET 10.6
>>> > setenv PATH "/Developer/Platforms/iPhoneSimulator.platform/Developer/
>>> > usr/bin:/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin"
>>> > /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/
>>> > gcc-4.2 -arch i386 -isysroot /Developer/Platforms/
>>> > iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator4.1.sdk -L/
>>> > Users/pratgupta/Desktop/Settinglinkedin/10_mar_butterfli/build/Debug-
>>> > iphonesimulator "-L/Users/pratgupta/Desktop/Settinglinkedin/
>>> > 10_mar_butterfli/Twitter+OAuth/Libraries & Headers" -F/Users/pratgupta/
>>> > Desktop/Settinglinkedin/10_mar_butterfli/build/Debug-iphonesimulator -
>>> > filelist /Users/pratgupta/Desktop/Settinglinkedin/10_mar_butterfli/
>>> > build/butterfli.build/Debug-iphonesimulator/butterfli.build/Objects-
>>> > normal/i386/butterfli.LinkFileList -mmacosx-version-min=10.6 -all_load
>>> > -Xlinker -objc_abi_version -Xlinker 2 -framework Foundation -framework
>>> > UIKit -framework CoreGraphics -lOAuth -lxml2 /Users/pratgupta/Desktop/
>>> > Settinglinkedin/10_mar_butterfli/LinkedInClientLibrary/build/Debug-
>>> > iphonesimulator/libLinkedInClientLibrary.a -o /Users/pratgupta/Desktop/
>>> > Settinglinkedin/10_mar_butterfli/build/Debug-iphonesimulator/
>>> > butterfli.app/butterfli
>>> >
>>> > ld: duplicate symbol _EstimateBas64EncodedDataSize in /Users/pratgupta/
>>> > Desktop/Settinglinkedin/10_mar_butterfli/LinkedInClientLibrary/build/
>>> > Debug-iphonesimulator/libLinkedInClientLibrary.a(Base64Transcoder.o)
>>> > and /Users/pratgupta/Desktop/Settinglinkedin/10_mar_butterfli/Twitter
>>> > +OAuth/Libraries & Headers/libOAuth.a(Base64Transcoder.o)
>>> > collect2: ld returned 1 exit status
>>> > Command /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/
>>> > bin/gcc-4.2 failed with exit code 1
>>> >
>>> > Some discussion on the Issue herehttp://
>>> stackoverflow.com/questions/525974

Re: [twitter-dev] Re: IPhone + Twitter + LinkedIn Error : Command /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/gcc-4.2 failed with exit code 1

[Battan Amit]

*Solved *


solved now...I have given the same key and secret to both linkedin and
twitter ..after changing them it works


AB



On 14 March 2011 11:55, Battan Amit  wrote:

> I done one thing that is ... I remove the library files of linkedin sdk..
> and add the source files of it with oAuth files from twiiter sdk... then it
> works ok for linkedin http://i.imgur.com/cXLXU.png
> http://i.imgur.com/ntV9G.png then I integrate all twitter code then
> project run ok without error but for twitter login interface it shows PAGE
> NOT FOUND ..http://i.imgur.com/8a1ua.png
>
>
> 
> AB
>
>
>
>
> On 12 March 2011 11:44, Bess  wrote:
>
>> First of all it is difficult to identify errors esp you don't have the
>> source code. However the stockoverflow discussion was good enough to
>> point out the general problems.
>>
>> ld: duplicate symbol _EstimateBas64EncodedDataSize in /Users/pratgupta/
>> Desktop/Settinglinkedin/10_mar_butterfli/LinkedInClientLibrary/build/
>> Debug-iphonesimulator/libLinkedInClientLibrary.a(Base64Transcoder.o)
>> and /Users/pratgupta/Desktop/Settinglinkedin/10_mar_butterfli/Twitter
>> +OAuth/Libraries & Headers/libOAuth.a(Base64Transcoder.o)
>>
>> Problem is: duplicate symbol
>>
>> It occurs on _EstimateBas64EncodedDataSize from LinkedinClientLibrary
>> in libLinkedInClientLibrary.a(Base64Transcoder.o) and Twitter+OAuth in
>> libOAuth.a(Base64Transcoder.o).
>>
>> Note: LinkedIn library and Ben Gottlieb's Twitter client include the
>> same OAuthConsumer code. It is duplicated. libLinkedInClientLibrary
>> and libOAuth both symbolicate the same method
>> '_EstimateBas64EncodedDataSize'. Check your #imports.
>>
>> Just do a search within your Xcode project on
>> _EstimateBas64EncodedDataSize. Find out where the duplicated methods.
>> Determine which one you should remove.
>>
>> On Mar 11, 4:56 am, Battan Ror  wrote:
>> > HI All
>> >
>> > I am using MGTwitterEngine oAuth and LinkedIn iOS sdk in my Iphone
>> > application with facebook-ios-sdk
>> >
>> > TwitterEngine :https://github.com/bengottlieb/Twitter-OAuth-iPhone
>> >
>> > LinkedInIphone :https://github.com/ResultsDirect/LinkedIn-iPhone
>> >
>> > Both integrated well separately, But when I have used both in
>> > application then error coming
>> >
>> > FB + Twitter = working well
>> > FB + LinkedIn = Working Well
>> > FB + Twitter + LinkedIn = Not Working
>> >
>> > and giving error
>> >
>> > Command /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/
>> > bin/gcc-4.2 failed with exit code 1
>> >
>> > Please help me where I am wrong.
>> >
>> > Error Transcript Text File
>> >
>> > Build butterfli of project butterfli with configuration Debug
>> >
>> > Ld build/Debug-iphonesimulator/butterfli.app/butterfli normal i386
>> > cd /Users/pratgupta/Desktop/Settinglinkedin/10_mar_butterfli
>> > setenv MACOSX_DEPLOYMENT_TARGET 10.6
>> > setenv PATH "/Developer/Platforms/iPhoneSimulator.platform/Developer/
>> > usr/bin:/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin"
>> > /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/
>> > gcc-4.2 -arch i386 -isysroot /Developer/Platforms/
>> > iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator4.1.sdk -L/
>> > Users/pratgupta/Desktop/Settinglinkedin/10_mar_butterfli/build/Debug-
>> > iphonesimulator "-L/Users/pratgupta/Desktop/Settinglinkedin/
>> > 10_mar_butterfli/Twitter+OAuth/Libraries & Headers" -F/Users/pratgupta/
>> > Desktop/Settinglinkedin/10_mar_butterfli/build/Debug-iphonesimulator -
>> > filelist /Users/pratgupta/Desktop/Settinglinkedin/10_mar_butterfli/
>> > build/butterfli.build/Debug-iphonesimulator/butterfli.build/Objects-
>> > normal/i386/butterfli.LinkFileList -mmacosx-version-min=10.6 -all_load
>> > -Xlinker -objc_abi_version -Xlinker 2 -framework Foundation -framework
>> > UIKit -framework CoreGraphics -lOAuth -lxml2 /Users/pratgupta/Desktop/
>> > Settinglinkedin/10_mar_butterfli/LinkedInClientLibrary/build/Debug-
>> > iphonesimulator/libLinkedInClientLibrary.a -o /Users/pratgupta/Desktop/
>> > Settinglinkedin/10_mar_butterfli/build/Debug-iphonesimulator/
>> > butterfli.app/butterfli
>> >
>> > ld: duplicate symbol _EstimateBas64EncodedDataSize in /Users/pratgupta/
>> > Desktop/Settinglinkedin/10_mar_butterfli/LinkedInClientLibrary/build/
>> > Debug-iphonesimulator/libLinkedInClientLibrary.a(Base64Transcoder.o)
>> > and /Users/pratgupta/Desktop/Settinglinkedin/10_mar_butterfli/Twitter
>> > +OAuth/Libraries & Headers/libOAuth.a(Base64Transcoder.o)
>> > collect2: ld returned 1 exit status
>> > Command /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/
>> > bin/gcc-4.2 failed with exit code 1
>> >
>> > Some discussion on the Issue herehttp://
>> stackoverflow.com/questions/5259747
>> >
>> > Amit Battan
>>
>> --
>> Twitter developer documentation and resources: http://dev.twitter.com/doc
>> API updates via Twitter: http://twitter.com/twitterapi
>> Issues/Enhancements Tracker:
>> http://code.google.com/p/twitter-api/issues/list
>> Change your membership to t