Closed Flohack74 closed 3 years ago
You need to properly call openChat
/closeChat
, viewMessages
and openMessageContent
for TTL to work correctly.
messageExpiredPhoto
and messageExpiredVideo
appears only in private chats for individual self-destructing messages.
Oh maybe we miss openMessageContent yes ;)
One more question, official clients seem to blur the thumbnails, should dthat only happen when ttl is expired, or already before the user opens it? Probably second.
Another one more question :) - so if a user clicks on a video, video note, audio or voice note content to start playback, when would the timer kick in, i.e. when should we send content opened msg?
Also, should we just send message content opened for every content (whatever opened means in this context), and when should we blur the thumbnails?
One more question, official clients seem to blur the thumbnails, should dthat only happen when ttl is expired, or already before the user opens it?
After TTL is expired, there is no thumbnail to show anymore. Thumbnail must be blurred, if is_secret==true
in messageAnimation
/messagePhoto
/messageVideo
/messageVideoNote
.
Sorry to bug you more, we see that blurring (isSecret == true) happens only when a TTL of one minute or less is set. Whats the logic behind that?
Secret chats are supposed to be used as an end-to-end replacement of ordinary private chats. If TTL is bigger than 1 minute, then this is just an ordinary video with auto-deletion enabled. The same can be done in private chats.
Hi, still tdlib 1.6 (upgrade in the works)...
so we are slowly implementing all missing features in our client. We cam across setting a TTL for messages. That works well but, during testing we found 2 problems: