GNOME Bugzilla – Bug 746102
Gracefully handle the demise of Facebook XMPP
Last modified: 2018-05-22 18:58:53 UTC
Facebook's XMPP bridge will be deprecated on April 30th [1]. It would be nice if this event is not sudden, inexplicable or confusing for those who use Facebook chat through Empathy. Some suggestions: * If someone is using Facebook chat, give them a couple of warnings in advance of the XMPP deprecation - a notification could be shown, and that could link to a dialog or documentation that provides more information. * When the deprecation happens, don't complain with errors about not being able to connect to the service. Instead, show a notification that explains that the service is no longer available. Again, this could link to a dialog or documentation with more information. * After the deprecation happens, remove any references to Empathy chat in the UI, such as in the accounts settings. * Update the documentation - modify existing references to Facebook chat to explain about the deprecation of the service. [1] https://developers.facebook.com/docs/chat
--- Facebook Graph API Update - Empathy Chat --- The solution maybe easy. Please check that we are doing GET requests from to the correct location at facebook. Empathy has some code that creates a JSON object and then sends a GET request to facebook to view the messages? NEW FACEBOOK API: https://developers.facebook.com/docs/graph-api/reference/v2.4/conversation --- NEW FACEBOOK API 2.4 --- GET /v2.4/{conversation-id} HTTP/1.1 Host: graph.facebook.com --- OLD FACEBOOK API 1.0 --- GET /v1.0/{conversation-id} HTTP/1.1 Host: graph.facebook.com --- Error Message --- (we may need to update the GET request dir to /v2.4/ to get empathy to work) Shows Disconnected - Authentication failed Go online to edit your personal information --- RELATED ISSUES --- https://bugzilla.gnome.org/show_bug.cgi?id=746102 https://bugzilla.gnome.org/show_bug.cgi?id=747623 https://bugzilla.gnome.org/show_bug.cgi?id=746100
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/empathy/issues/823.