Examples here and Twitter docs have very different approach

Authorization flow here is very diffrent than the shown in the docs.

I'm just making a note here.

[andypiper]

Is this a reference to a specific example - could you point to the page in the docs, and the code sample you are looking at?

Yes, this example here on github should be like this in the docs.

Also the authorization flow is quite different in the docs use a simple curl with oauth and here use Pin Based Oauth but Pin Based oauth is not even mentioned in the docs.

Maybe it's just me not understanding but I do think docs and here should sync. And look at #this page is doing exactly what I want to do.

[andypiper]

Thanks for the feedback, we will discuss how to handle these thoughts - appreciate you taking the time to identify the areas we can improve!

I'm also running into this problem - the code references CONSUMER_KEY and CONSUMER_SECRET

Are these supposed to be API_KEY and API_SECRET? That doesn't seem to work

[Imagineer99]

Did anyone get this to work? none of the sample codes seem to function.