Closed Bug 954371 Opened 11 years ago Closed 11 years ago

Migrate Facebook chat to use OAuth

Categories

(Instantbird Graveyard :: Other, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 953976

People

(Reporter: bugzilla, Unassigned)

References

Details

*** Original post on bio 938 by Eric Caron <eric.caron AT gmail.com> at 2011-07-20 22:54:00 UTC *** According to EionRobb, Adium is able to accomplish better Facebook chat authentication by relying on OAuth (http://comments.gmane.org/gmane.network.instant-messaging.adium.devel/1024). Incorporating that into Instantbird would hopefully reduce the problems new users are having when setting up Facebook Chat in Instantbird for the first time.
*** Original post on bio 938 by Eion Robb <eion AT robbmob.com> at 2011-07-20 23:49:16 UTC *** http://forum.developers.facebook.net/viewtopic.php?id=93219 has more info
*** Original post on bio 938 at 2011-09-09 12:15:19 UTC *** We already have a bug for "reimplement Facebook chat", marking as duplicate:
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
*** Original post on bio 938 at 2012-10-01 10:01:22 UTC *** OAuth will allow us to use the Facebook API (to fill in gaps that the XMPP gateway only doesn't allow us to fill, see morphed bug 953976 (bio 538) for that now) and from what I've heard it would allow us to login users with their email-adress (and maybe phone number?) too. This would be nice too since some users were struggling to get logged it (we have an FAQ items for that iirc).
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: DUPLICATE → ---
Blocks: 953976
I don't see how this differs from bug 953976. The real request here is to "Support Facebook Chat better", which requires use not to use the XMPP interface. I initially thought (when reading the title of this bug) it meant "Support OAuth for XMPP", which would be a separate bug.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.