#1024 closed defect (notmyfault)

Facebook oauth token failing on bitlbee (page not found)

Reported by: freakgame@… Owned by: wilmer
Priority: normal Milestone:
Component: Jabber Version: 3.0.6
Keywords: Cc:
IRC client+version: Client-independent Operating System: Other
OS version/distro: Synology


Facebook oauth token failing on bitlbee (page not found)

It seems when you try to ask for an oauth token it does not work:

09:56:31 <jabber_oauth> Open this URL in your browser to authenticate: <URL HERE FAILS> 09:56:31 <jabber_oauth> Respond to this message with the returned authorization token.

Facebook tells me: ERROR: An error has occurred. Try again later.

It seems it has trouble getting an oauth token from facebook itself?

Attachments (1)

facefuck.png (8.3 KB) - added by wilmer at 2013-01-19T11:22:05Z.

Download all attachments as: .zip

Change History (11)

Changed at 2013-01-19T11:22:05Z by wilmer

Attachment: facefuck.png added

comment:1 Changed at 2013-01-19T11:22:12Z by wilmer

Facebook broke it. Please send them a complaint. I'm *very* angry.

I've clicked the "Appeal" button and asked them why it was "okay" to just do this without giving any explanation, but I assume this GUI around /dev/null is not very good at sending useful responses.

comment:2 Changed at 2013-01-20T16:46:38Z by anonymous

I see, bad luck, I already figured I couldn't see bitlbee app anymore at the security settings for apps. Hopefully they will fix this ASAP.

comment:3 Changed at 2013-01-21T10:51:29Z by seed419@…

Damnit Zuckerberg.

I barely even use FB chat that much, but I'm still upset about this over just the principle. What could possibly be the reason for them revoking bitlbee? I'd like to hear the explanation for their actions here.

Also, I can't get the password auth to work either. I just get

jabber - Login error: Authentication failure

Not sure if it's just me or what. I've never used this before, but I'm typing the commands verbatim from the wiki so I have no idea.

comment:4 Changed at 2013-01-21T18:48:07Z by anonymous

thanks, facebook.

comment:5 Changed at 2013-01-21T22:05:44Z by sandycameltoeniggah

hmm, maybe create a new "app" and "app key" on facebook?

comment:6 Changed at 2013-01-21T22:09:30Z by wilmer

See the message, they've completely revoked my ability to register them. But oF course you could do it yourself and just put the API keys into the source.

comment:7 Changed at 2013-01-21T22:12:29Z by wilmer

Resolution: notmyfault
Status: newclosed

Strange. It seems to be working again, actually. I've never received any notification, but hey.. I've verified, it works again now. Have fun, all!

comment:8 Changed at 2013-03-27T23:59:09Z by anonymous

i confirm, its works again

comment:9 Changed at 2013-04-17T19:40:32Z by anonymous

This has resurfaced. Potential fix:
acc fb set oauth off
acc fb set username <yourusername>
acc fb set password <yourpassword>
acc fb on

comment:10 in reply to:  9 Changed at 2013-04-19T06:45:26Z by anonymous

Replying to anonymous:

This has resurfaced. Potential fix:
acc fb set oauth off
acc fb set username <yourusername>
acc fb set password <yourpassword>
acc fb on

This fix worked for me. Thanks!

Modify Ticket

as closed The owner will remain wilmer.
The resolution will be deleted.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.