Repository navigation
Conversation
r10s
force-pushed
the
r10s/clarify-receive-time
branch
from
November 7, 2026 23:21
df761f0 to
ee4111e
Compare
r10s
force-pushed
the
r10s/clarify-receive-time
branch
from
November 7, 2026 23:24
ee4111e to
3e5cb0d
Compare
Collaborator
|
Would be great to also document this in |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
this PR clarifies that the "received timestamp" may also be set to the last webxdc update (which is always "received" from the view of the webxdc app).
this is the case since more than two years, since #5388, however, got into focus only recently by the new Message Info views.
UI shall use a different label, i started that on android at deltachat/deltachat-android#4823