Differences between revisions 10 and 12 (spanning 2 versions)
Revision 10 as of 2015-02-21 06:42:26
Size: 5859
Editor: dx
Comment: new branch url
Revision 12 as of 2015-05-31 03:30:40
Size: 6564
Editor: dx
Comment: mention git master branch
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
'''Update:''' New location for the branch: https://github.com/bitlbee/bitlbee/tree/feat/hip-cat - the old one won't be updated anymore and may be removed. I (dx) have a [[https://github.com/bitlbee/bitlbee/tree/feat/hip-cat|branch]] that adds special support for hipchat accounts. It's not yet completely ready to be merged but it has several nice improvements that make it much less painful.
Line 15: Line 15:
I (dx) have a [[https://github.com/bitlbee/bitlbee/tree/feat/hip-cat|branch]] that adds special support for hipchat accounts. It's not yet completely ready to be merged but it has several nice improvements that make it much less painful. For debian/ubuntu, builds should be available in the APT repo at http://code.bitlbee.org/debian/ (just pick hip-cat branch instead of master. Or pick master, and read the section below)
Line 20: Line 20:
apt-get install -y git libglib2.0-dev
Line 26: Line 25:
Then do the rest of the build as usual Then do the rest of the build as usual (assuming you have the build dependencies installed)
Line 33: Line 32:
Line 65: Line 65:
 * Reconnecting may create duplicate channels in the list (like #chat_000)
 * If you're using gtalk/facebook with oauth, you'll need to remove the accounts and re-add with "account add (gtalk|fb) username"
 * You might get some duplicate channels in your list (with underscores added at the end)
 * If you use another client (web/desktop/mobile hipchat clients) to join to a channel when bitlbee is connected, you might get an invite from it, and Bad Things™ will happen
Line 68: Line 68:
But, well, that's nothing compared to the issues in the rest of this page. But, well, that's nothing compared to the issues with plain jabber.
Line 76: Line 76:
== Workarounds for mainline bitlbee == == git master branch ==

''Most'' of the changes above are now merged to the git master branch.

The main exception is the channel handling - it won't fetch the list from the server for you, which means you won't be able to /join them directly. As stated above, that was an experimental feature, and it's still not stable enough to have it for everyone.

These changes are going to be part of the 3.4.1 release, which will happen soon™

Usage is the same thing as above:

{{{
account add hipchat your@email.com <password>
account hipchat on
}}}

<<BR>>

-----

<<BR>>

== Workarounds for mainline bitlbee (up to 3.4) ==

Setting up Hipchat with BitlBee

Hipchat is a chat service by Atlassian that provides an XMPP server. It's the choice of many businesses, as it supports mission critical features like pasting images and having them show up inline in the chat, and silly meme-like things that happen if you type things like "(awwyeah)".

As such, it's only used by people who have no other choice. If you can decide what chat service to use, please get a real XMPP server with real XMPP clients instead.

Official information on their XMPP, including technical details, is available here


hip-cat branch

I (dx) have a branch that adds special support for hipchat accounts. It's not yet completely ready to be merged but it has several nice improvements that make it much less painful.

For debian/ubuntu, builds should be available in the APT repo at http://code.bitlbee.org/debian/ (just pick hip-cat branch instead of master. Or pick master, and read the section below)

To get it:

git clone https://github.com/bitlbee/bitlbee.git
cd bitlbee
git checkout feat/hip-cat

Then do the rest of the build as usual (assuming you have the build dependencies installed)

./configure
make
make install

Or for debian/ubuntu: dpkg-buildpackage

Initial setup

If you had a "jabber" account with hipchat, delete it with account jabber del (ensure it's the correct one before doing that)

Use the same account username you'd use in the official client, and protocol "hipchat" instead of "jabber":

account add hipchat your@email.com <password>
account hipchat on

That's all.

Improvements

  • Your mention name is set for all group chats automatically.
  • Mention names for other people are used as nicks by default. You just need to add @ in front of them to actually 'mention' other people.
  • As an experimental feature, the whole channel list is fetched from the server and added locally. Use "channel list" or just /list to view them.
    • Because of this, you can just do "/join #channel"
  • "Message from unknown participant" are now shown as coming from "[unknown]"
    • Also those should happen less often when joining channels.
  • Fixed channel topics.

Known issues

If you have any problems with this branch, please join #bitlbee (irc.oftc.net) and ping me (dx)!

  • HTML handling from hipchat bots is still weak.
  • You might get some duplicate channels in your list (with underscores added at the end)
  • If you use another client (web/desktop/mobile hipchat clients) to join to a channel when bitlbee is connected, you might get an invite from it, and Bad Things™ will happen

But, well, that's nothing compared to the issues with plain jabber.




git master branch

Most of the changes above are now merged to the git master branch.

The main exception is the channel handling - it won't fetch the list from the server for you, which means you won't be able to /join them directly. As stated above, that was an experimental feature, and it's still not stable enough to have it for everyone.

These changes are going to be part of the 3.4.1 release, which will happen soon™

Usage is the same thing as above:

account add hipchat your@email.com <password>
account hipchat on




Workarounds for mainline bitlbee (up to 3.4)

If you can't use the hip-cat branch for any reason, here's the list of workarounds you need to apply.

Again, ignore all this if you used the hip-cat branch.


Initial setup

Get your account details from this page, and use your jabber ID here:

account add jabber 123456_789012@chat.hipchat.com
account jabber set tag hipchat

The jabber IDs of hipchat accounts are in the format 123456_789012@hipchat.com where 123456 is the company-wide account ID and 789012 is your user account ID.

Fix nick display by setting nick_source:

account hipchat set nick_source full_name

Groupchats

Groupchats require you to have a "nick" set to your real name (Givenname Surname), otherwise you'll get an error on /join ("not-acceptable: Please use the nickname...")

Additionally, the channel names are in the format #123456_chat_name where 123456 is the company-wide account ID.

The best way to get this working is to avoid using the usual "invite" method of joining channels and add the channels manually before you join them.

chat add hipchat 123456_chat_name@conf.hipchat.com #channel_name
channel #channel_name set nick 'Givenname Surname'

Note that you can't rename channels - you have to remove and re-add them.

Highlights/mentions

Do @mention_name instead of username:. Otherwise people won't notice your messages are addressed to them. A great feature.

This mention_name comes from <item mention_name="..."> in the roster. This value isn't parsed by bitlbee, so the only way to get it is enabling xmlconsole or using one of the official clients.

"Message from unknown participant" when joining channel

Since the server sends wrong JIDs for the "from" field (123456_chat_name@conf.hipchat.com/real name here), all you can do is using client scripts to fix this up. If you write something to do this, add it here.

Using the trigger.pl script from Wouter Coekaerts (download here), you can add the following trigger to replace "Message from unknown participant " with a blank string to hide it:

/TRIGGER ADD -all -nocase -regexp '^Message from unknown participant ' -replace ''

For weechat:

/filter add hipchat_unknown_participant * nick_root ^Message from unknown participant  

For emacs erc:

(defun my-reformat-jabber-backlog ()
  (save-excursion
    (goto-char (point-min))
    (if (looking-at
         "^<root> Message from unknown participant Your Name:")
        (replace-match "<yournick>"))))
(add-hook 'erc-insert-modify-hook 'my-reformat-jabber-backlog)

Debugging

If you want to figure out something, you can try enabling the XMPP xmlconsole to your contacts. Good luck with that.

BitlBee Wiki: HowtoHipchat (last edited 2018-08-04 05:58:56 by dx)