-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
[Feature Request] Add feature to set the message as delivered. #10708
Comments
I don't think this is something we can implement. Technically for us it's delivered the very instant you send it. If we had a single device as the receiving device we could do it(like signal/WhatsApp). Otherwise we would have confirmation from 1-infinite number of devices. |
@geekgonecrazy I think the logic of this problem like the read receipt logic. I mean Why we do not implement REST API to mark the message (or even the whole subscription) as delivered like when we mark it as read using "subscription.read" API. Then I think the problem is related to an account not to a device whether this account received the message or not (not important to which device the message delivered). |
@mohanadrefaai On most devices though when its delivered to that devices its basically read. Mobile for instance. When you see you have unreads in a DM. You open the DM. Those are delivered and a few seconds later they are read. Same for desktop. @RocketChat/core thoughts? To me in cases like whatsapp if i'm having a conversation its useful to know its delivered because they have one device and that one device is mobile. So I know its actually reached their phone(and I know its the phone because that is the device and messages are actually delivered there straight away) I think it loses all value in multi-device where its delivered to the servers DB. Then its fetched and marked as read almost immediately |
Unfortunately after discussing this with the team, we realized this is not technically possible. |
Using read receipt is very useful to check whether the message is seen or not. But it does not include the "delivered" status which means that, a user received a message and maybe he did not see it.
And this status is also different from the "sent" status which means that, the message has been sent successfully to the server.
Depending on #9717 issue I see that there is no feature yet to detect the "delivered" status.
The text was updated successfully, but these errors were encountered: