Pidgin but not BitlBee?

[dchmelik]

Works for me in Pidgin but not BitlBee. I've at least triple-checked (on several occasions this year since recent commit and before. What can I do to test? I tried gdb process described on pidgin.im but it said 'no stack' (I guess because it doesn't crash, just never connects with supposed authentication error for same authentication working in Pidgin).

[WillForan]

It looks like #186 is out of date. (related to #189). The current readme suggest user@example.com%<workspace>.slack.com where user@example.com is the email you use to register with your slack workspace and <workspace>.slack.com is the url to your slack workspace.

I had luck issuing commands to &bitlbee like

account new slack email@address.com%WORKSPACE.slack.com
account slack set password SLACKPASSWORD
account slack set api_token "xoxc-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX xoxp-YYYYYYYYYYYYYYYYY"
account slack set get_history true
account slack on
save

If you already have slack working in pidgin, you can also get the token from $HOME/.purple/accounts.xml. In a terminal/shell

grep api_token ~/.purple/accounts.xml

---

Other useful &bitlbee commands

• /query slackbot - talk to slackbot
• chat list slack - list all channels
• chat add slack !4 - add the forth result from chat list (a slack channel), prints instructions like /join #fourth-title-channel to join
• group list see existing groups, confirm actual WORKSPACE name
• group info WORKSPACE see all users (for /query)

(Note: major edit! I had a very long running bitlbee server and hadn't restarted despite major updates to libslack.so)