Opened at 2010-10-20T20:55:22Z
Closed at 2014-07-08T16:36:26Z
#696 closed defect (fixed)
nick_source gets ignored in facebook chat (libpurple's jabber)
| Reported by: | Owned by: | wilmer | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | Purple | Version: | devel |
| Keywords: | Cc: | ||
| IRC client+version: | Client-independent | Operating System: | Linux |
| OS version/distro: |
Description
Setting nick_source for the facebook account to full_name doesn't result in the contacts being shown with their names as nicks. They still use their numerical facebook id when they first connect (to facebook) after the bitlbee server is started.
Once they leave and later reconnect they show up with their actual names (as they should with nick_source set). This information does not seem to persist from session to session though; on restarting bitlbee the whole process starts from the beginning.
This behavior was observed on the libpurple bzr build of 19.10.2010 on arch linux with erc and irssi.
Attachments (0)
Change History (6)
comment:1 Changed at 2011-06-20T12:17:39Z by
comment:2 Changed at 2011-06-20T13:05:31Z by
Note the component on this bug, this is definitely libpurple-specific.
The reason is probably that libpurple passes nickname *after* reporting that someone's online. BitlBee then doesn't change nicks anymore because it'd result in a flood of nick changes.
comment:3 follow-up: 4 Changed at 2011-06-21T09:31:11Z by
Now all I get is bunch of numbers getting and losing voice privs. So I should go back to normal BitlBee if I want facebook chat.. This is facebook specific and I don't see libpurple slowing their XMPP implementation because facebook XMPP cuts some corners.. this is IMHO :)
comment:5 Changed at 2014-07-08T16:33:36Z by
| Priority: | normal → minor |
|---|---|
| Summary: | nick_source gets ignored in facebook chat → nick_source gets ignored in facebook chat (libpurple's jabber) |
This bug confused me at first, so changing title to clarify.
Does this still happen?
TBH libpurple's jabber module isn't great for facebook chat to begin with, since there's no oauth, but the bug is valid. Also, in 3.2.2 you can get the builtin jabber module *and* libpurple by configuring it with --purple=1 --jabber=1
comment:6 Changed at 2014-07-08T16:36:26Z by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Hmm, I'm pretty sure I fixed this actually. Feel free to reopen if this does still happen.
nick_source doesn't work and save command doesn't save it. Seems to affect libpurple version only? /var/lib/bitlbee didn't include any mentions about nick_source.