Opened at 2016-08-24T15:40:45Z
Last modified at 2019-06-17T18:20:18Z
#1264 new defect
No self-messages in telegram
| Reported by: | sqrt | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Purple | Version: | 3.4.2 |
| Keywords: | Cc: | ||
| IRC client+version: | irssi v0.8.19 | Operating System: | Linux |
| OS version/distro: | Debian 8 |
Description
I'm using bitlbee-libpurple 3.4.2+20160808+master+51-g88cde4e-git, telegram with telegram-purple, and I don't receive self-messages in groupchats while using same telegram account from another machine. Although, I get my messages using same telegram-libpurple library with pidgin/finch, that's why I think it's a bitlbee bug.
Might be related to the self-messages removing mechanism that can't separate my connection in bitlbee and connection from other places. Any ideas?
Attachments (0)
Change History (4)
comment:1 Changed at 2016-08-24T17:03:46Z by
comment:2 Changed at 2016-08-24T18:42:11Z by
Thanks for clarifying!
I see, so it is a libpurple problem.
I guess it would be nice to have an option to enable echo on a protocol, so one can filter his own messages using his client. Looks ugly but solves the problem.
comment:3 Changed at 2019-06-14T23:11:52Z by
comment:4 Changed at 2019-06-17T18:20:18Z by
Not really, as that flag needs to be implemented on the plugin side, and due to the way messages are routed internally with libtgl it's hard for the plugin to tell which messages to flag that way.
See my comment at https://github.com/majn/telegram-purple/issues/382
https://wiki.bitlbee.org/SelfMessages says "Libpurple private chats". Not group chats. Those can't be supported because both echoes and self-messages messages look exactly the same with libpurple's API.