-
Notifications
You must be signed in to change notification settings - Fork 26
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.
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
Request to treat 1 message with multiple attachments as seperate messages #81
Comments
Also on an unrelated note, if I pull out of my GameStop shares at a good time I'll finally be able to donate 😎. In the meantime, HOLD 💎🙌 |
Yes, this is definitely an issue -- I only realized it after releasing the update with tapbacks, but it's been on my list so I'll work on it and let you know once I've got it implemented. GME to the moon, man; thanks for playing your part in this. Mad amounts of respect. |
Unrelated but I have since lost all this money |
Rip to your stocks man, I'm sorry about that. Appreciate what you did though. Also, this issue is now somewhat fixed (once I release the next update, of course); reactions will now show (in the web interface) on the specific attachment that they were actually reacting to. I'm working on adding support for sending to a specific attachment/part of message, and should have that implemented soon as well (either in this update or the next). |
Alright, I think I've got this implemented for most use cases — there are still a few small bugs to iron out but you should expect to see this included in the next update. |
Alright! And the stonks are back 😳😳 |
I updated to 0.7.4 and it looks really nice! {
"id": "D3DBDAD8-5EEE-4D72-ADB7-20A74501706D",
"fromMe": true,
"isTypingMessage": false,
"description": "We'll show up and he'll be like",
"flags": 1081349,
"fileTransferIDs": [
"72D48466-A535-4C93-AA78-6791A8AB53F1"
],
"chatID": "chat526745548997352517",
"time": 1615577622383.0002,
"timeRead": 0,
"isSOS": false,
"timeDelivered": 0,
"isAudioMessage": false,
"isCancelTypingMessage": false,
"items": [
{
"type": "attachment",
"payload": {
"metadata": {
"size": {
"width": 500,
"height": 255
},
"id": "72D48466-A535-4C93-AA78-6791A8AB53F1",
"filename": "AE5727AE-29A7-4E84-B537-17AFD35FEB41.gif",
"uti": "com.compuserve.gif",
"mime": "image/gif"
},
"id": "p:0/D3DBDAD8-5EEE-4D72-ADB7-20A74501706D",
"chatID": "chat526745548997352517",
"transferID": "72D48466-A535-4C93-AA78-6791A8AB53F1",
"fromMe": true,
"time": 1615577622383.0002
}
},
{
"type": "text",
"payload": {
"chatID": "chat526745548997352517",
"fromMe": true,
"parts": [
{
"type": "text",
"string": "We'll show up and he'll be like"
}
],
"id": "p:1/D3DBDAD8-5EEE-4D72-ADB7-20A74501706D",
"time": 1615577622383.0002,
"text": "We'll show up and he'll be like",
"acknowledgments": [
{
"chatID": "chat526745548997352517",
"sender": "*my friend's email*",
"associatedID": "p:1/D3DBDAD8-5EEE-4D72-ADB7-20A74501706D",
"id": "am:F0716C13-6871-4286-A4A6-3CF3FB0B25CD",
"fromMe": false,
"time": 1615577636093.2012,
"acknowledgmentType": 2003
}
]
}
}
],
"service": "iMessage",
"timePlayed": 0,
"sender": "e:*my email*",
"isDelivered": false
} |
Ah man, I thought I had this all figured out. It probably won't make any difference for this specific issue, but did you also make sure to upgrade to libsmserver 0.6.4? It includes many improvements that should improve backend stability. (I'm just wondering since I didn't publish the updates on twickd yet, so you may have missed it.) Also, if possible, could you open up the inspector on your web browser, select the image, and on its parent element (which should be a |
Here is the image's tapback_guid - tapback_guid="p:0/D3DBDAD8-5EEE-4D72-ADB7-20A74501706D" and here is the one for the text - tapback_guid="p:1/D3DBDAD8-5EEE-4D72-ADB7-20A74501706D" Thank you for the updates!
|
|
Regarding the Thanos message, I was able to get this information from MyMessage. p0 should have a 2003 acknowledgment/tapback and p1 should have a 2004 acknowledgment/tapback. Both are from the same person. {
"id": "D3DBDAD8-5EEE-4D72-ADB7-20A74501706D",
"fromMe": true,
"isTypingMessage": false,
"description": "We'll show up and he'll be like",
"flags": 1081349,
"fileTransferIDs": [
"72D48466-A535-4C93-AA78-6791A8AB53F1"
],
"chatID": "chat526745548997352517",
"time": 1615577622383.0002,
"timeRead": 0,
"isSOS": false,
"timeDelivered": 0,
"isAudioMessage": false,
"isCancelTypingMessage": false,
"items": [
{
"type": "attachment",
"payload": {
"metadata": {
"size": {
"width": 500,
"height": 255
},
"id": "72D48466-A535-4C93-AA78-6791A8AB53F1",
"filename": "AE5727AE-29A7-4E84-B537-17AFD35FEB41.gif",
"uti": "com.compuserve.gif",
"mime": "image/gif"
},
"id": "p:0/D3DBDAD8-5EEE-4D72-ADB7-20A74501706D",
"chatID": "chat526745548997352517",
"transferID": "72D48466-A535-4C93-AA78-6791A8AB53F1",
"fromMe": true,
"time": 1615577622383.0002
}
},
{
"type": "text",
"payload": {
"chatID": "chat526745548997352517",
"fromMe": true,
"parts": [
{
"type": "text",
"string": "We'll show up and he'll be like"
}
],
"id": "p:1/D3DBDAD8-5EEE-4D72-ADB7-20A74501706D",
"time": 1615577622383.0002,
"text": "We'll show up and he'll be like",
"acknowledgments": [
{
"chatID": "chat526745548997352517",
"sender": "*my friend's email*",
"associatedID": "p:1/D3DBDAD8-5EEE-4D72-ADB7-20A74501706D",
"id": "am:F0716C13-6871-4286-A4A6-3CF3FB0B25CD",
"fromMe": false,
"time": 1615577636093.2012,
"acknowledgmentType": 2003
}
]
}
}
],
"service": "iMessage",
"timePlayed": 0,
"sender": "e:*my email*",
"isDelivered": false
} |
This one has the tapbacks shown in the correct order, but the images are shown out of order. WebMessage behaves exactly the same and MyMessage is a little different |
See this comment: airmessage/airmessage-android#3 (comment) for more details |
For example, if someone sends me 17 photos in one message, I cannot put different tapbacks on different photos using SMServer because all 17 photos only give one tapback menu at the top. This also applies to a photo sent together with a text caption, a tapback can only be placed on the photo, not the caption.
The text was updated successfully, but these errors were encountered: