Bitlbee thinks gtalk does not support XEP85

[watcom.hecht@…]

Sending my typing status to gtalk users only work if I comment out the check at ​https://github.com/bitlbee/bitlbee/blob/master/protocols/jabber/jabber.c#L657

Can I be doing something wrong? I'm using Irssi with bitlbee_typing_notice.pl if that's of any relevance. Bitlbee version 3.4.2

Receiving the typing status from gtalk users works with or without the patch, but they can only see my typing status if I patch it.

[dx]

Works for me. I even fixed relevant stuff recently, but before 3.4.2, see ​e4145d9, ​0c78bb7 and ​5307e88

The point of that check you commented out is to avoid sending typing notices unless we've received one already from the other side (or a hint that XEP85 is supported with <active>). So first ensure the other side has written a message or .

Try enabling the xmlconsole as suggested in ​https://wiki.bitlbee.org/Debugging and look for <composing or <cha:composing (or active, or any mention of chatstates)

Try disabling the irssi script and sending /ctcp other_contact_nick TYPING 1 manually

[watcom.hecht@…]

Thanks for the suggestions. I tried enabling the xmlconsole and there's only chat, no chatstates. By the way, the client on the other side is the standard chat window from Gmail running on Chrome, but also tried Firefox. Both accounts (Bitlbee's and the browser's) are from Google (different accounts of course) and I'm authenticating using OAUTH.

The same with the latest version from github. I exchange several messages, see "typing" on the status bar before incoming messages but when I type from Bitlbee's side there's no feedback going through. Again, I tried commenting out that line again in the version from github and it worked.

I'm not sure what could be different with my setup that would be relevant. Anyway, I'll be using the patched version for now so it's no big deal, just documenting my issue in case there's anyone else with the same problem.