Allow private message content to exceed 255 bytes

[hamzaozturk]

Summary

• Fix TLV encoding for private message content so payloads larger than 255 bytes are accepted.
• Keep messageId constrained to the original single-byte length while expanding only the content field to a two-byte length when needed.

[jackjackbits]

this is a protocol breaking change that we need to sync with android. it also has an error when message is exactly 255 chars. and no tests.

[hamzaozturk]

Is there any particular reason why private messages are limited to 255 characters? Just wondering if that’s intentional.
Also, I’ve fixed the 255-char issue you mentioned and added the relevant tests for it.

[jackjackbits]

arbitrary. i’ll sync with android team.

…

On 10 Oct 2025, at 11:36, Hamza Öztürk ***@***.***> wrote: hamzaozturk left a comment (permissionlesstech/bitchat#784) Is there any particular reason why private messages are limited to 255 characters? Just wondering if that’s intentional. Also, I’ve fixed the 255-char issue you mentioned and added the relevant tests for it. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>