Any Telegram app on UT that shows 2 tick marks for delivered messages? [Solved]
-
Yep, blue => message sent, green => message read.
I experienced some issues a couple of time, but most of the time it works well and update is fast.
-
Cheers, @thilov.
-
Thanks, @AppLee.
-
Showing to the sender if the receiver has seen/read the message, violates the privacy of the receiver, at least if he/she has no chance to disable this.
-
@guru yes, that annoyes me, too.
-
@guru This is baked into Telegram, we cannot do anything about it.
-
@AppLee New with TELEports in contrast to the old App: Grey: Queued for sending, Red could not be sent
-
There is also an error in git about this, some discussion and at least a solution for the telegram cmd client, see:
https://bugs.launchpad.net/telegram-app/+bug/1475915
The final proposal was:
The proposed solution is the following: The application may provide a setting to turn off "send message read notifications for received messages". The user who chooses to do that will in turn not see "message read notifications for sent messages". I think it is fair and that is a solution we are happy to go ahead with.So, it seems it can be implemented in any tg client, at leat at our side.
-
@Flohack said in Any Telegram app on UT that shows 2 tick marks for delivered messages?:
@AppLee New with TELEports in contrast to the old App: Grey: Queued for sending, Red could not be sent
Thanks for the headsup there, Flo.
-
@guru The drawback is that if we do not mark messages as read, your unread count will explode: All groups and chats will show the blue bubble with 999+ unread messages after some time. You will not know which message you have already seen and which not. How will that work?
Telegram server expects in order for you to keep track of unread messages (and also positioning the view when opening a chat on the last unread message) that you submit read receipts. They will be relayed to all other parties in this chat, if needed. You cannot influence this.
I will not implement a "shadow db" that keeps track of "locally read" and corresponding network messages, since that defeats the purpose of the tdlib library which encapsulates the whole Telegram protocol and also message store for us. You m,ight however want to file an issue here: https://github.com/tdlib/td/issues - those guys could in theory provide an option to not send read receipts.
Again I expect they will refuse, since if its not implemented on server side, its complicated and unreliable.
