that alternate method was mostly a test to see if I could make it work, I still encourage using the PIN system :) I like it tbh, even with the annoyance of havign to login and retrieve the pass for the user, it's only required once. ill most likely remove this alternate proc in next revision, and add XAuth support instead.
On Sun, Feb 27, 2011 at 7:25 PM, RTT <p...@sapo.pt> wrote: > On 27-02-2011 17:18, brian - wrote: > >> use an alternate method to wont require the user to visit the twitter site >> to get the PIN code, the app will simulate a browser login, catch the >> cookies and proceed to auth on its own to retrieve the PIN. >> > This will work until twitter decide to change these html pages. > But with Twitter you can even bypass the need of a PIN. Just remove all the > "oauth_verifier" references and you will see that works without PIN. > > > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be > -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
