Very long lines should be split up into smaller pieces (e.g. 300 chars each) to prevent decryption issues with mircryption clients. (Single lines longer than ~325 chars won't be decrypted correctly by mircryption)
Very long lines should be split up into smaller pieces (e.g. 300 chars each) to prevent decryption issues with mircryption clients. (Single lines longer than ~325 chars won't be decrypted correctly by mircryption)
## <bountysource-plugin>
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/321233-crypt-module-long-lines-can-t-be-decrypted-by-mircryption-clients?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).
</bountysource-plugin>
<!-- github-sync-id:14220880 -->
This is due to hitting the 512 character limit of each IRC line ("nick!user@host PRIVMSG #channel" + ~330 chars + encryption overhead + base64 overhead is around 512 bytes). It should be fairly easy to work around this by have OnUserMsg split a long line into ~330 byte chunks and send them as multiple lines. I'll see if I can put a patch together to do this.
This is due to hitting the 512 character limit of each IRC line ("nick!user@host PRIVMSG #channel" + ~330 chars + encryption overhead + base64 overhead is around 512 bytes). It should be fairly easy to work around this by have OnUserMsg split a long line into ~330 byte chunks and send them as multiple lines. I'll see if I can put a patch together to do this.
<!-- github-comment-id:46439004 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Very long lines should be split up into smaller pieces (e.g. 300 chars each) to prevent decryption issues with mircryption clients. (Single lines longer than ~325 chars won't be decrypted correctly by mircryption)
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
This is due to hitting the 512 character limit of each IRC line ("nick!user@host PRIVMSG #channel" + ~330 chars + encryption overhead + base64 overhead is around 512 bytes). It should be fairly easy to work around this by have OnUserMsg split a long line into ~330 byte chunks and send them as multiple lines. I'll see if I can put a patch together to do this.
+1 from me for this.