You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by "Scott Wilson (JIRA)" <ji...@apache.org> on 2010/05/06 09:33:48 UTC
[jira] Commented: (WOOKIE-142) Twitter API Widget
[ https://issues.apache.org/jira/browse/WOOKIE-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864683#action_12864683 ]
Scott Wilson commented on WOOKIE-142:
-------------------------------------
Yes, in general there needs to be a mechanism for Wookie acting as an oAuth proxy - if nothing else you don't want to distribute widgets with their token and secret in plain view.
> Twitter API Widget
> ------------------
>
> Key: WOOKIE-142
> URL: https://issues.apache.org/jira/browse/WOOKIE-142
> Project: Wookie
> Issue Type: Improvement
> Reporter: Bryan Copeland
> Priority: Trivial
>
> This is just a first stab to extending the same methods as Flickr and YouTube widgets into Twitter...
> It works for read only right now (search by Tweet text or User tweets)
> For Tweeting/status updates, there is a slight problem with the authentication in the OAuth signing directly from Javascript via the OAuth JS library, so, this may be one case of a widget which does require a server-side OAuth proxy to relay access tokens securely (although, I have seen Yahoo! YQL used to authenticate remotely to Twitter, so it may still be possible)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.