wojciech.kapcia@tigase.net opened 6 years ago
|
|
|
|
It looks like the code which I thought was not working properly is actually working just fine. However, to make carbons be created, packet |
|
Andrzej Wójcik wrote:
This follows https://xmpp.org/extensions/xep-0280.html#which-messages but - this list is only suggestion so, for the sake of having something convenient (i.e. read status propagated to all client), also forward carbons for receipts? %kobit %bmalkow what do you think? |
|
See below extract from XMPP mailing list from a few days ago:
which suggests that clients should respond with the message of the same |
|
Andrzej Wójcik wrote:
In theory - yes, but this requires client to actually follow it (and this is still "recommendation". IMVHO we could still handle this on the server and make it work for any message type. |
|
To be honest if user would be offline, then thanks to MA/MAM/Offline Message Delivery it will be delivered to all clients, so we should apply the modification which @wojtek suggested. |
|
I've made a modification and verified that it works for me. Please check it on your own if everything works for you as well. |
|
Fix is ready for deployment |
|
Deployed:
|
|
It works but… it doesn't solve the original problem - you have two clients (let's say desktop and mobile), you receive the message, both devices create notification and marks chat with unread count (and at this time delivery receipt is generated). Now you open the chat on one device, it clears the unread status on that device but notification/unread status persist on the other devices. But it looks like there is not XEP that could handle this use case... |
|
On the server side now everything works as expected. |
|
Referenced from commit 1 year ago
|
|
Referenced from commit 1 year ago
|
Type |
Bug
|
Priority |
Normal
|
Assignee | |
RedmineID |
8927
|
Version |
tigase-server-8.1.0
|
Spent time |
6h 15m
|
Read recipients are not copied to other resource connections via message carbons.