Skip to content

chore: bump pre-pro char receiving limit #1502

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 14, 2025
Merged

chore: bump pre-pro char receiving limit #1502

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions ts/receiver/queuedJob.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -304,11 +304,13 @@ async function handleRegularMessage(

handleLinkPreviews(rawDataMessage.body, rawDataMessage.preview, message);

// TODO: add pro status check for sender
const isSenderPro = false;
const maxChars = isSenderPro
? Constants.CONVERSATION.MAX_MESSAGE_CHAR_COUNT_PRO
: Constants.CONVERSATION.MAX_MESSAGE_CHAR_COUNT_STANDARD;
// TODO: Once pro proof validation is available make this dynamic
// const maxChars = isSenderPro
// ? Constants.CONVERSATION.MAX_MESSAGE_CHAR_COUNT_PRO
// : Constants.CONVERSATION.MAX_MESSAGE_CHAR_COUNT_STANDARD;
// NOTE: The truncation value must be the Pro count so when Pro is released older clients wont truncate pro messages.
const maxChars = Constants.CONVERSATION.MAX_MESSAGE_CHAR_COUNT_PRO;

const body =
rawDataMessage.body.length > maxChars
? rawDataMessage.body.slice(0, maxChars)
Expand Down