Message truncation logic and comments

Author: SessionHero01

app/src/main/java/org/session/libsession/messaging/messages/visible/VisibleMessage.kt

@@ -30,6 +30,18 @@ data class VisibleMessage(
     var reaction: Reaction? = null,
     var hasMention: Boolean = false,
     var blocksMessageRequests: Boolean = false,
+    /**
+     * The pro features enabled for this message.
+     *
+     * Note:
+     * * When this message is an incoming message, the pro features will only be populated
+     * if we can prove that the sender has an active pro subscription.
+     *
+     * * When this message represents an outgoing message, this property can be populated by
+     * application code at their wishes but the actual translating to protobuf onto the wired will
+     * be checked against the current user's pro proof, if no active pro subscription is found,
+     * the pro features will not be sent in the protobuf messages.
+     */
     var proFeatures: Set<ProFeature> = emptySet()
 ) : Message()  {
 

app/src/main/java/org/thoughtcrime/securesms/pro/ProStatusManager.kt

@@ -381,8 +381,11 @@ class ProStatusManager @Inject constructor(
         // if the debug is set, return that
         if (prefs.forceIncomingMessagesAsPro()) return MAX_CHARACTER_PRO
 
-        // otherwise return the true value
-        return if(isPostPro()) MAX_CHARACTER_REGULAR else MAX_CHARACTER_PRO //todo PRO implement real logic once it's in
+        if (message.proFeatures.contains(ProMessageFeature.HIGHER_CHARACTER_LIMIT)) {
+            return MAX_CHARACTER_PRO
+        }
+
+        return MAX_CHARACTER_REGULAR
     }
 
     // Temporary method and concept that we should remove once Pro is out