Just to clarify what this means: the OAuth implementation at Twitter allows several methods of authentication as detailed here: http://dev.twitter.com/pages/auth_overview
Some clients such as qTwitter use the out-of-band method which would require us to add new strings for the PIN code as well as require a browser to be launched. The best method for us to use is the xAuth method since it allows us to retain the current UI while making all the changes in the dataengine. However, xAuth access isn't granted by default. I already obtained permission from Twitter to use xAuth and have had authentication working since last Thursday. Next up is signing requests (for posting tweets, etc.) which I'll finish within the week. Ryan On Wed, Jun 9, 2010 at 10:35 AM, Ryan P. Bitanga <ryan.bita...@gmail.com> wrote: > > In progress. I have it working already. :) Cleaning up the patch by the end > of the week. We have xAuth support from Twitter so we don't need to introduce > any new strings. > > Ryan > > On Wed, Jun 9, 2010 at 10:19 AM, Aaron J. Seigo <ase...@kde.org> wrote: >> >> erf ... >> >> just read: >> >> http://momeny.wordpress.com/2010/06/09/kde-oauth/ >> >> and it looks like we'll need to port the microblogging plasmoid as well, and >> this really ought to be done before the 4.5.0 release (!). anyone feel like >> giving it a go? >> >> -- >> Aaron J. Seigo >> humru othro a kohnu se >> GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 >> >> KDE core developer sponsored by Qt Development Frameworks >> >> _______________________________________________ >> Plasma-devel mailing list >> Plasma-devel@kde.org >> https://mail.kde.org/mailman/listinfo/plasma-devel >> > _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
