slack-libpurple
slack-libpurple copied to clipboard
Messages sent by me from other clients don't show up in bitlbee/irc
This is similar to https://github.com/sm00th/bitlbee-discord/issues/7 which has some discussion around difficulty/desirability of doing this and a potential fix.
Do you have everything described here working: https://wiki.bitlbee.org/SelfMessages In particular, do self messages from other libpurple-based protocols show in in bitlbee? slack-libpurple is sending these messages to libpurple in what I understand to be the right way.
Same problem here, with self_messages = `true' irssi 1.0.7-1~deb9u1 bitlbee-libpurple 3.5.1-1
Same issue. Using Irssi v1.1.1 - self_messages = `true' - Works for Discord....
Is that libpurple-discord or bitlbee-discord?
bitlbee-discord 0.4.1
If someone can get this to work in bitlbee with another libpurple-based plugin, I can take a look at what it does. It's not clear to be that bitlbee-libpurple supports self messages, but I may well be missing something.
Works with hangouts 0.1 (both from web interface and android app).
Okay, it looks like hangouts does not use serv_got_im
for these messages (since they're not RECV
) but instead just does a conversation_write
. I'll try that.
Actually, now that I'm looking at it, that should already be the case because the sender is not the IM target. Also, it wouldn't affect chats. @EionRobb - any thoughts on this?
I had a conversation in #bitlbee with the developers there that indicated to me that there was something on their end that they needed to push to enable self-messages being handled correctly from libpurple, so you might need/want a really bleeding-edge bitlbee build. Having said that, I tried to upgrade and still see the same behavior in my bitlbee+slack-libpurple set up.
Sorry for being vague here.
I had a conversation in #bitlbee with the developers there that indicated to me that there was something on their end that they needed to push to enable self-messages being handled correctly from libpurple, so you might need/want a really bleeding-edge bitlbee build. Having said that, I tried to upgrade and still see the same behavior in my bitlbee+slack-libpurple set up.
Sorry for being vague here.
Is this fixed?