Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Trivial Trivial
    • Resolution: Later
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      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)

      1. twitter.wgt
        82 kB
        Bryan Copeland

        Issue Links

          Activity

          Hide
          Scott Wilson added a comment -

          Twitter API is a moving target

          Show
          Scott Wilson added a comment - Twitter API is a moving target
          Hide
          Scott Wilson added a comment -

          We have a read-only twitter widget, but not one that supports posting new tweets, for which we really need to wait until Twitter supports OAuth 2.0

          Show
          Scott Wilson added a comment - We have a read-only twitter widget, but not one that supports posting new tweets, for which we really need to wait until Twitter supports OAuth 2.0
          Hide
          Scott Wilson added a comment -

          This needs oAuth to be implemented to work properly

          Show
          Scott Wilson added a comment - This needs oAuth to be implemented to work properly
          Hide
          Scott Wilson added a comment -

          Lets finish this up and put it in 0.8.2

          Show
          Scott Wilson added a comment - Lets finish this up and put it in 0.8.2
          Hide
          Ross Gardler added a comment -

          In order for this widget to work http;//www.twitter.com needs adding to the whitelist - it would make sense to add this to config.xml

          Show
          Ross Gardler added a comment - In order for this widget to work http;//www.twitter.com needs adding to the whitelist - it would make sense to add this to config.xml
          Hide
          Ross Gardler added a comment -

          In addition to the issues in the previous comment a code review shows:

          /**

          This code is (c) and we cannot include it without permission from the author. Looking at the site I'd say that the author is happy for it to be reused but permission is not explicitly granted, hence we will need to contact them. Of course, it may be easier to rewrite that bit of code as it is not exactly rocket science.

          Show
          Ross Gardler added a comment - In addition to the issues in the previous comment a code review shows: /** gup Get URL Parameters Credit: http://www.netlobo.com/url_query_string_javascript.html */ This code is (c) and we cannot include it without permission from the author. Looking at the site I'd say that the author is happy for it to be reused but permission is not explicitly granted, hence we will need to contact them. Of course, it may be easier to rewrite that bit of code as it is not exactly rocket science.
          Hide
          Ross Gardler added a comment -

          Thanks for the patch.

          If this is intended for inclusion in Wookie (and I do hope it is) there needs to be some changes in the code:

          • all files must contain the appropriate license headers
          • we need an icon that we are sure we can use (I've not looked at the license for the twitter logo currently used)
          • do we really need jQuery in this widget? A version is provided by default by Wookie itself.
          • cssbuttons.css is not license compatible (it's GPL)

          I've not actually tried using this yet, but do have a need for a twitter widget and am happy to help maintain this.

          Show
          Ross Gardler added a comment - Thanks for the patch. If this is intended for inclusion in Wookie (and I do hope it is) there needs to be some changes in the code: all files must contain the appropriate license headers we need an icon that we are sure we can use (I've not looked at the license for the twitter logo currently used) do we really need jQuery in this widget? A version is provided by default by Wookie itself. cssbuttons.css is not license compatible (it's GPL) I've not actually tried using this yet, but do have a need for a twitter widget and am happy to help maintain this.
          Hide
          Scott Wilson added a comment -

          One solution is for Wookie to manage consumer keys and secrets for widgets (i.e. each Wookie server needs to register each widget it serves) and then have these accessed by oAuth middleware.

          I've got bits of a working solution using SignPost, but didn't really want to check it into the core yet.

          Show
          Scott Wilson added a comment - One solution is for Wookie to manage consumer keys and secrets for widgets (i.e. each Wookie server needs to register each widget it serves) and then have these accessed by oAuth middleware. I've got bits of a working solution using SignPost, but didn't really want to check it into the core yet.
          Hide
          Bryan Copeland added a comment -

          OAuth signing not working... going to investigate using YQL or local/protected config xml or json (to not give away secret key or OAuth consumer)

          Show
          Bryan Copeland added a comment - OAuth signing not working... going to investigate using YQL or local/protected config xml or json (to not give away secret key or OAuth consumer)
          Hide
          Scott Wilson added a comment -

          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.

          Show
          Scott Wilson added a comment - 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.

            People

            • Assignee:
              Unassigned
              Reporter:
              Bryan Copeland
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development