Opened at 2010-01-16T11:22:49Z
Closed at 2015-10-13T06:47:34Z
#556 closed enhancement (notabug)
Extra Characters in Jabber Messages
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | wishlist | Milestone: | |
| Component: | BitlBee | Version: | 1.2.4 |
| Keywords: | Cc: | ||
| IRC client+version: | IRSSI 0.14 | Operating System: | Linux |
| OS version/distro: |
Description
In an new Conversation with some People using Jabber over Pidgin I got some strange extra characters
11:57:28 < ...> schon wach und noch nich im training? I IIII I I I I I I II I
Attachments (1)
Change History (4)
Changed at 2010-01-16T11:23:02Z by
| Attachment: | bitbee_bug.png added |
|---|
comment:1 Changed at 2010-01-16T11:28:15Z by
comment:2 Changed at 2010-01-18T23:54:03Z by
| Priority: | normal → wishlist |
|---|---|
| Type: | defect → enhancement |
This happens when the other party uses an OTR plugin (end-to-end encryption of IM traffic). It sends messages with tabs and spaces at the end to indicate support for OTR and to start the negotiation. It was designed like that because the tabs and spaces are supposed to be invisible, but sadly IRC clients (or at least irssi) does show them like this. :-/
BitlBee could filter them out but it shouldn't since some people actually use an OTR plugin in their IRC client.
I'll mark this as a wishlist bug for adding a "trim messages" setting
comment:3 Changed at 2015-10-13T06:47:34Z by
| Resolution: | → notabug |
|---|---|
| Status: | new → closed |
Trimming these messages isn't something bitlbee should do. The real problem here is irssi displaying tab characters as an inverted "I", no other client does this. Those characters are supposed to be invisible. The "tab_stop.pl" script can be used as a workaround.
Oh, just to clearify this: This happens only in the first (like max. 4) Messages the User sends. After that, this doesn't happen anymore until the query is closed.