Broken User Experience for Flickr Plugin

Bug #155616 reported by Rusty Lynch
4
Affects Status Importance Assigned to Milestone
Moblin Multimedia
Fix Released
Critical
Shane Bryan

Bug Description

The user experience provided by the sample flickr plug-in is awkward and error prone due to an unnecessary dependence on the midbrowser.

We are using the webbrowser to do the actual upload (and therefore forced to switch back-n-forth with a browser window). This is both an error prone implementation approach, and confusing to the user.

The correct way to interact with flickr is to use the publicly available web services API documented via:
http://flickr.com/services/api/

There are several open source implementations of this API listed in the URL above, including several Python bindings like:
http://flickrapi.sourceforge.net/

Tags: bugfest
donald (donald-wei)
Changed in moblin-multimedia:
assignee: nobody → donald-wei
status: New → Confirmed
Revision history for this message
Rusty Lynch (rusty-lynch-intel) wrote :

We would be better off just removing the flicker plugin then using it as an example that will mislead countless other developers.

Either the plug-in is fixed, or completely removed before declaring victory on M9

Changed in moblin-multimedia:
assignee: donald-wei → rusty-lynch-intel
importance: Undecided → Critical
milestone: none → m9
Revision history for this message
Shane Bryan (shane-bryan) wrote :

I have started looking into how this is implimented and what can be done. The current code is using a very out of date flickr API python module and I will be updating it while fixing the bug.

Changed in moblin-multimedia:
assignee: rusty-lynch-intel → shane-bryan
status: Confirmed → In Progress
Revision history for this message
Shane Bryan (shane-bryan) wrote :

Summary notes from my research and IRC logs:

* Looking into the flickr API, it requires an API key that (non-commercial or commercial)
  embedded in the client side implementation
* The current code has an embeded API key in it, but no comments as to where it
  comes from or who owns it, so if it were to get deleted by the owner, or to expire, we'd be hosed
Todo:
* Register new API key for non-comercial use and document who owns it (DONE)
* Convert to correct flickr API implimentation
* Use gconf to store and get default API key(s)
* Document in OEM Branding guide all the default keys that need to be modified to their own
  Commercial registered keys
* Document the recommend that OEM Commercial keys be managed in a secured manner,
  left as an excercise to the student

Revision history for this message
Rusty Lynch (rusty-lynch-intel) wrote :

Given that the new flickr plugin implementation was not ready, and having such a plug-in was only a stretch goal for milestone9, we have decided to remove the existing sample plugin implementation

Changed in moblin-multimedia:
status: In Progress → Fix Committed
Revision history for this message
Churchy Zheng (changqiu-zheng) wrote :

removed this feature, of cuz these issue is gone.

Changed in moblin-multimedia:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.