911930 - Twitter mashup is not working any more.

Status: RESOLVED WONTFIX

(Mozilla Reps Graveyard :: reps.mozilla.org, task)

Description

[Giorgos Logiotatidis [:giorgos]]

We got IRC reports that twitter integration is not working anymore. This was expected to happen at some point, after twitter announce their new API. 

We now have to:
1. Verify that this is the case (and not something failing from our side)
2. Decide whether we'll drop this functionality altogether or if we'll implement another provider.

Comment 1

[jbonatakis]

I would like to work on this.

Comment 2

[Justin Crawford [:hoosteeno] [:jcrawford]]

jbonatakis, that's great news. Are you comfortable working with the Reps.mozilla.org codebase? If so we can assign this one to you and will be glad to have the help!

Comment 3

[jbonatakis]

i feel comfortable although i am new here. Can u provide more info? What should I implement exactly?

Comment 4

[Giorgos Logiotatidis [:giorgos]]

We chatted with jbonatakis on IRC about this one. John if you decide that you want and can work on this, reply here to assign the bug to you.

Comment 5

[jbonatakis]

Sorry for the missing update and the late responce. I m going to make a research on this as soon as I finish this another bug. I have already take a glance on this but i am not ready yet to answer. If someone else want to try it is ok.

Comment 6

[jbonatakis]

1. Verify that this is the case (and not something failing from our side)

I suppose the code was removed because i dont find anything about, so i dont have mentioning for that.

2. Decide whether we'll drop this functionality altogether or if we'll implement another provider.

The regular implementation after Twitter API 1.1 is to create a Twitter Application on Twitter Developer Site (https://apps.twitter.com/app/new) and make use of consumer key and secret key. There are many apps to make the work done. I mention somes that looks interesting:

* twython ->                   https://github.com/ryanmcgrath/twython
* django-twitter-oauth ->    https://github.com/ccg/django-twitter-oauth
* python-twitter ->            https://code.google.com/p/python-twitter/

Another aproach may be Pierros suggestion at 778090 for topsy. I couldnt find anything better of this. Many Features and give API (http://api.topsy.com/doc/resources/content/tweets/).

Finally there is someone who implements a js script to skip API1.1. He uses the widgets of twitter to achieve it.It is very simple and it works. I sent a mail to him for update. here[0] is a link to his page where he represents the script. 

According to above notes I think this can be implemented with a small or with zero cost.

[0] http://www.jasonmayes.com/projects/twitterApi/

Comment 7

[Giorgos Logiotatidis [:giorgos]]

John thank you for researching this.

From the presented solutions, the third one is exactly what we want to do, display a widget. We'll discuss next steps for this in our next reps-dev meeting and update here.

Comment 8

[Giorgos Logiotatidis [:giorgos]]

We agreed that this is low-priority so we do not plan to work on this now.

The widget part is what we need but as :agibson said we need to make sure that it respects our privacy guidelines.

Comment 9

[Giorgos Logiotatidis [:giorgos]]

Closing this one as WONTFIX since this is broken and there're no plans to fix this. I filed bug 1270084 to remove any left over code.