Modify

#1086 closed defect (notmyfault)

Facebook clients rejoin with profile ID

Reported by: anonymous Owned by:
Priority: normal Milestone:
Component: BitlBee Version: 3.2
Keywords: Cc:
IRC client+version: Client-independent Operating System: Public server
OS version/distro:

Description

A while after logging in to Facebook, all clients leave the channel and rejoin with the profile ID as nickname. I've had nick_format set to '%full_name' since I started using FB chat over Bitlbee. Sometimes the clients with IDs rejoin with their nicks, but they'll eventually rejoin with IDs again.

Attachments (0)

Change History (8)

comment:1 Changed at 2013-08-21T14:48:54Z by anonymous

I forgot to mention that when the channel is full of clients with IDs, and someone else comes online, he/she will join with their name as nick.

comment:2 Changed at 2013-08-25T14:23:51Z by orium

I'm also having this issue with version 3.2.

comment:3 Changed at 2013-08-25T14:26:10Z by wilmer

This is really just Facebook screwing up as they like to do sometimes.

An xmlconsole dump could show what's going on exactly, but my guess is that there's little BitlBee can do against this.

comment:4 in reply to:  3 ; Changed at 2013-08-26T07:15:02Z by anonymous

Replying to wilmer:

This is really just Facebook screwing up as they like to do sometimes.

An xmlconsole dump could show what's going on exactly, but my guess is that there's little BitlBee can do against this.

How exactly do I create a dump?

comment:5 in reply to:  4 ; Changed at 2013-08-28T12:59:49Z by anonymous

acc fb add xmlconsole

comment:6 in reply to:  5 Changed at 2013-08-28T18:07:41Z by sjefen6@…

Replying to anonymous:

acc fb add xmlconsole

acc fb set xmlconsole

comment:7 Changed at 2013-08-29T15:53:51Z by anonymous

There are lines like this for each of my online friends:

<xmlconsole> RX: <iq from="xxx@…" to="xxx@…/BitlBee_9955f6d8_4E517A9DB346E" id="fbiq4E518099F3812" type="set"><query xmlns="jabber:iq:roster"><item jid="-yyy@…" subscription="both" name=""/></query></iq>

comment:8 Changed at 2014-07-07T14:16:13Z by dx

Resolution: notmyfault
Status: newclosed

Their xmpp gateway has improved lately (even if it's going to get killed in less than a year), so it's likely this was just their bug from when it sucked.

Modify Ticket

Action
as closed The ticket will remain with no owner.
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.