Modify

Ticket #1024 (closed defect: notmyfault)

Opened 21 months ago

Last modified 18 months ago

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

Description

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

facefuck.png (8.3 KB) - added by wilmer 21 months ago.

Change History

Changed 21 months ago by wilmer

comment:1 Changed 21 months ago 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 21 months ago 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 21 months ago 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 21 months ago by anonymous

thanks, facebook.

comment:5 Changed 21 months ago by sandycameltoeniggah

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

comment:6 Changed 21 months ago 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 21 months ago by wilmer

  • Status changed from new to closed
  • Resolution set to notmyfault

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 18 months ago by anonymous

i confirm, its works again

comment:9 follow-up: ↓ 10 Changed 18 months ago by anonymous

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

comment:10 in reply to: ↑ 9 Changed 18 months ago by anonymous

Replying to anonymous:

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

This fix worked for me. Thanks!

View

Add a comment

Modify Ticket

Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


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

 
Note: See TracTickets for help on using tickets.