2009/7/1 Obrzut <sa...@peyoteuk.com>: > > Did I state otherwise? > > You are not reading my words - you are being blinded by the noise from > your own head. > > What I stated is this; > > I authenticate my VB.NET web browser via PIN etc > > THIS means my browser is authenticated. > > If I try to access a page via the program with a TCP Client - I have > to re-authenticate via PIN. > > This WAS a problem - my solution is to continue to use the web browser > for authentication and extract the XML pages into an XML Document. > > Hence the above code. > > If you state otherwise - that you CAN use a TCP Client after already > authenticating your VB.Net web browser - you are wrong. > > I imagine you think I am wrong - and that I am an idiot. Believe me - > I am very skilled at programming. And this is my experience. > > The library is faulty. It does not process leading zero pins. > > The OAuth implementation is stupid - because it does not authenticate > an program but a TCP method. > > Hence, you guys are soooo off the mark here it hurts me to talk to > you. > > Really, srsly, it's pathetic that you DO NOT LISTEN.
And it's pathetic that you take a piece of code that someone has generously donated to the Twitter developer community and then complain because *you* can't get it to work with an attitude that would be barely acceptable if you'd paid for it. You clearly think you can do better, so go ahead and write your own Twitter library for VB.net. Nobody is forcing you to use that code. -Stuart -- http://stut.net/projects/twitter > On Jul 1, 4:58 am, DWRoelands <duane.roela...@gmail.com> wrote: >> You can absolutely authenticate in a web page, even if your >> application is not a web application. Mine works that way. >> >> Here's how it should go. Bojan, please correct me if I'm wrong. >> >> 1. Your application calls GetAuthorizationLink() to get the URL of the >> authorization page (you've got this already). >> 2. Your application opens a web browser to that link. In .NET, you >> can do this with Process.Start(The URL that you get from >> GetAuthorizationLink). >> 3. The user sees the six-digit PIN on the screen. >> 4. Your application prompts the user to enter the six-digit PIN that >> they see. >> 5. Your application calls GetAccessToken(), passing the six-digit PIN >> as the input parameter. >> 6. The OAuth object has two properties that should now be populated: >> Token and TokenSecret. These are the items you will use for all >> subsequent OAuth requests to Twitter. >> >> Your application should now be authorized via OAuth. >> >> On Jun 30, 8:58 pm, Obrzut <sa...@peyoteuk.com> wrote: >> >> >> >> > This is because of OAuth. It uses HTML pages to validate. Perhaps I am >> > wrong - but once I use a web browser to validate - I cannot use a TCP >> > Client to get the XML because I authenticated via a web browser. When >> > I tried to (for example) send the pin back via a HTTP Web Request it >> > failed. I am not sure if I am using the OAuth library Interface Class >> > I have for VB.NET correctly!?
