Obrzut: My application does exactly what you say is impossible. The user authenticates via the web browser, then my desktop application completes the process using the six-digit PIN.
There's no need to "fix" any XML that comes from Twitter, and there's no need to process any HTML from a web page. I'd be happy to help you work through the issues you're having with your application, but please stop insisting that you're smarter than everyone else here. Bojan: Obrzut's right about the GetAccessToken() call in the Twarp code. GetAccessToken accepts the PIN as an Int; that should be a string so that leading zeroes don't get stripped. I haven't seen any PINs with a leading zero, but that doesn't mean they don't occur. :) --Duane On Jul 1, 8:00 am, Obrzut <[email protected]> wrote: > If you state otherwise - that you CAN use a TCP Client after already > authenticating your VB.Net web browser - you are wrong.
