Custom Query (1098 matches)
Results (4 - 6 of 1098)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1302 | fixed | Concatenate messages without an unintended newline | ||
| Description |
When sending a longer than 512 bytes message, paste_buffer joins this with a newline as usually the IRC client splits the long message in chunks and sends it as individual messages. In some instances that breaks long URLs or introduces an unintended newline. It would be great if there is a mechanism to detect and mitigate this. |
|||
| #1300 | invalid | Support Wire protocol | ||
| Description |
Hello, I think it would be nice to have Wire protocol support. This messaging system was opensourced in july 2016. https://github.com/wireapp Thank you. |
|||
| #1299 | fixed | jabber: Mismatch between real jid and local jid might cause Bitlbee not to send JOIN | ||
| Description |
I'm using Biboumi component as a transport between IRC and XMPP. It's also serving as my bouncer, and it's providing me with XEP-0313-based scrollback history of a channel. By observing the IRC traffic with Wireshark, I see that JOIN messages are not coming in. IRSSI seems to not be bothered too much by that; Konversation, Pidgin and HexChat seem to not open the chat window at all. From what I could interpret, the issue *might* be that Biboumi includes realname address as real JID. As this includes the local user too, I think the join logic might be getting confused, and never deciding to mark the user as having joined the channel at all: https://github.com/bitlbee/bitlbee/blob/a04705bfde7c623605ee0e8449efd61ecc5c0b62/protocols/jabber/conference.c#L357 https://github.com/bitlbee/bitlbee/blob/a04705bfde7c623605ee0e8449efd61ecc5c0b62/irc_channel.c#L251 This seems to have other consequences: it seems impossible to PART the conference, and impossible to send another JOIN. I'm using latest stable Biboumi 3.5.1 on Debian (which seems to be unlisted below). |
|||
