Skip to content

Conversation

@purpshell
Copy link
Member

Handles Live photos as a GIF and prevents attachment duplication.

Resolves BRI-33301

@KishanBagaria
Copy link
Contributor

prevents attachment duplication

are we only mapping the gif/live photo and discarding the regular one? it's better to map both since people will want to see the regular pic too

@purpshell
Copy link
Member Author

prevents attachment duplication

are we only mapping the gif/live photo and discarding the regular one? it's better to map both since people will want to see the regular pic too

Can you provide me with the structure of the normal photo? I am mapping both parent and child photos. Seems like the parent is the still image and the child is the motion version.

@purpshell
Copy link
Member Author

prevents attachment duplication

are we only mapping the gif/live photo and discarding the regular one? it's better to map both since people will want to see the regular pic too

Can you provide me with the structure of the normal photo? I am mapping both parent and child photos. Seems like the parent is the still image and the child is the motion version.

What should happen is that the photo is bridged then edited to be a GIF

@KishanBagaria
Copy link
Contributor

for first iteration, we should leave the original intact and just map the child as a new gif message if possible (does this cause collisions?)

@purpshell
Copy link
Member Author

for first iteration, we should leave the original intact and just map the child as a new gif message if possible (does this cause collisions?)

This will cause a duplicated message, but sure I'll get it working that way, just requires removing some logic.

@purpshell purpshell requested a review from tulir October 16, 2025 00:03
Copy link
Member

@tulir tulir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Otherwise looks good

case *waE2E.VideoMessage:
data.MsgType = event.MsgVideo
if msg.GetGifPlayback() {
pairedMediaType := msg.GetContextInfo().GetPairedMediaType()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, is the context info inside the associated child message or outside? might need to copy it over if it's outside

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, MessageContextInfo is outside, ContextInfo is of course inside. I don't think there's anything important in MessageContextInfo so this should be fine as is

@tulir tulir merged commit 1b24b61 into main Oct 28, 2025
11 checks passed
@tulir tulir deleted the rajeh/BRI-33301 branch October 28, 2025 13:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants