Closed
Bug 1141674
Opened 9 years ago
Closed 3 years ago
Reimplement Facebook Chat not using XMPP
Categories
(Chat Core :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: pedrogfrancisco, Unassigned)
References
Details
Attachments
(2 files, 1 obsolete file)
3.90 KB,
text/plain
|
Details | |
107.59 KB,
patch
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:39.0) Gecko/20100101 Firefox/39.0 Build ID: 20150310030235 Steps to reproduce: I want to not have to use Facebook web interface after April 31, 2015. The XMPP server is going to be disabled after that date [1] [1] https://developers.facebook.com/docs/chat Actual results: I found an implementation of chat using the newer API, via web calls, at https://github.com/Schmavery/facebook-chat-api . Expected results: I would like someone more knowledgeable than me to evaluate and, if possible, integrate, the new chat API before April 31.
Comment 1•9 years ago
|
||
Not sure why I never saw this, but yes...we should plan to stop using the XMPP interface. It currently has still been working for me, however. My current plan is to switch to the MQTT transport that the Facebook Messenger apps work. This uses MQTT over TCP with JSON/Thrift messaging. libpurple did an implementation of this for GSoC last year, we could either include their C++ code or rewrite it into JavaScript (which would allow use in Thunderbird).
Status: UNCONFIRMED → NEW
Component: Untriaged → XMPP
Ever confirmed: true
Product: Thunderbird → Chat Core
Version: 31 → trunk
Updated•9 years ago
|
Summary: Evaluate Facebook's XMPP server alternative → Stop using XMPP to connect to Facebook
Comment 2•9 years ago
|
||
The libpurple code is available at: https://hg.pidgin.im/soc/2015/jgeboski/facebook/file/6a0a79182ebc/libpurple/protocols/facebook
Comment 3•8 years ago
|
||
Just so you guys and gals know, the Facebook chat is now broken in Thunderbird, so this issue should be patched ASAP.
Reporter | ||
Comment 4•8 years ago
|
||
I think it would be best if you opened another bug for that and then linking it here. Fixing Facebook brokenness may involve other solution than migrating to the new API.
Comment 5•8 years ago
|
||
It's really all the same bug at this point. XMPP has stopped working, we need to do something else.
Comment 7•8 years ago
|
||
FYI we put up a blog post about this if people are interested in more information: http://blog.instantbird.org/2016/01/facebook-chat-issues/
Updated•8 years ago
|
Summary: Stop using XMPP to connect to Facebook → Reimplement Facebook Chat not using XMPP
Comment 9•8 years ago
|
||
I've started some work on this and have gotten authentication working.
Assignee: nobody → clokep
Severity: normal → major
Status: NEW → ASSIGNED
Comment 10•8 years ago
|
||
I have a WIP that downloads the contact list. I wanted to get some feedback on my use of promises from Nihanth.
Attachment #8717599 -
Flags: feedback?(nhnt11)
Comment 11•8 years ago
|
||
This now connects to MQTT and is able to send/parse messages.
Attachment #8717599 -
Attachment is obsolete: true
Attachment #8717599 -
Flags: feedback?(nhnt11)
Updated•8 years ago
|
Component: XMPP → General
Updated•5 years ago
|
Assignee: clokep → nobody
Status: ASSIGNED → NEW
Comment 12•3 years ago
|
||
I don't think we should do this as it would be chasing after Facebook and supporting a non-standards protocol.
I think this is a good example of why we should allow extensions to implement protocols, however.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•