[Bug 77360] New: Turning off Facebook Platform prevents log in to Facebook chat

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=77360

          Priority: medium
            Bug ID: 77360
          Assignee: telepathy-bugs at lists.freedesktop.org
           Summary: Turning off Facebook Platform prevents log in to
                    Facebook chat
        QA Contact: telepathy-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: michael.lutynski at gmail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: gabble
           Product: Telepathy

For the longest time, I could not log into Facebook chat using KDE Telepathy,
and could not determine why because it worked perfectly for awhile.

I finally found the problem, but it's not immediately intuitive. 

If you go to this link: 

https://www.facebook.com/settings?tab=applications&section=opt_out&view 

...and click the "Turn Off Platform" button, then Telepathy will *never*
connect to Facebook chat. However, if you turn the platform back on, then
Telepathy will log in and work as expected. 

If the platform is turned off, according to Facebook: "This means you can't use
the Facebook integrations on third party apps or websites. If you want to use
these apps and websites with Facebook, turn Platform back on." 

"Turning Platform back on resets related settings (such as your "Apps others
use" setting) and allows Facebook to receive information about your use of
third party apps and websites." 

I didn't realize that me wanting to limit the way that Facebook connects to
other websites would affect Telepathy chat. 

An idea: is it possible that Telepathy could query the Facebook API and see if
the user has Platform integration turned on? And pass that back to the UI?

(This bug was first reported on KDE's Telepathy bug tracker:
https://bugs.kde.org/show_bug.cgi?id=333224)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.