fix: resolve turning off disappearing messages empty messages in most cases

still requires more tweaking

ts/node/migration/sessionMigrations.ts

@@ -1226,7 +1226,7 @@ function updateToSessionSchemaVersion30(currentVersion: number, db: BetterSqlite
     db.prepare(`ALTER TABLE ${CONVERSATIONS_TABLE} ADD COLUMN hasOutdatedClient TEXT;`).run();
 
     // TODO update to agreed value between platforms
-    const disappearingMessagesV2ReleaseTimestamp = 1680339600000; // unix 01/04/2023 09:00
+    const disappearingMessagesV2ReleaseTimestamp = 1706778000000; // unix 01/02/2024 09:00
     // const disappearingMessagesV2ReleaseTimestamp = 1677488400000; // unix 27/02/2023 09:00
 
     // support disppearing messages legacy mode until after the platform agreed timestamp

ts/util/expiringMessages.ts

@@ -290,10 +290,12 @@ export async function checkForExpireUpdate(
   const isLegacyDataMessage = Boolean(
     isLegacyContentMessage && checkIsLegacyDataMessage(dataMessage as SignalService.DataMessage)
   );
-  const isLegacyConversationSettingMessage =
-    isLegacyContentMessage &&
-    isLegacyDataMessage &&
-    dataMessage.flags === SignalService.DataMessage.Flags.EXPIRATION_TIMER_UPDATE;
+  const isLegacyConversationSettingMessage = isDisappearingMessagesV2Released
+    ? isLegacyContentMessage &&
+      isLegacyDataMessage &&
+      dataMessage.flags === SignalService.DataMessage.Flags.EXPIRATION_TIMER_UPDATE
+    : isLegacyContentMessage &&
+      dataMessage.flags === SignalService.DataMessage.Flags.EXPIRATION_TIMER_UPDATE;
 
   let expirationTimer = isLegacyDataMessage
     ? Number(dataMessage.expireTimer)

ts/util/releaseFeature.ts

@@ -1,7 +1,7 @@
 import { Data } from '../data/data';
 
 // TODO update to agreed value between platforms
-const featureReleaseTimestamp = 1680339600000; // unix 01/04/2023 09:00
+const featureReleaseTimestamp = 1706778000000; // unix 01/02/2024 09:00
 // const featureReleaseTimestamp = 1677488400000; // unix 27/02/2023 09:00
 let isFeatureReleased: boolean | undefined;