-
Notifications
You must be signed in to change notification settings - Fork 291
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] Have a 'message sent' timestamp #428
Comments
Yes, I suggested this 2 years ago. Thanks for the issue. We'll implement it in the new protocol. Right now, it would break the application level protocol, so we'll hold off on it. This feature will be part of the new application level protocol design. |
+1 |
Isotoxin has long able to send message create timestamp. |
I asked for such «client capacity detection» about 30 times, I plan to do it as a standardized custom packet in Konv.im as it'll never gets implemented. |
They have a plan to redesign the protocol. This must be one of the items. |
Standardized custom packet is not enough. How long client should wait such packet from other client? No. Client should know capabilities of other client just in PACKET_ID_ONLINE - first packet from other client. Isotoxin already does it by using modified core. Maybe it makes sense to add this functionality to the core officially? |
It makes sense, but wont happens i guess, as "c-toxcore" focus on tests, not features (yet). |
Currently offline messages are displayed with the timestamp of arrival.
It is important for both sender and receiver to know both when the message was created and sent.
Please add the timestamp for 'send' event (when the user hits the 'send' button), and communicate it to the recipient, so that the recipient can see both times.
References:
The text was updated successfully, but these errors were encountered: