-
-
Notifications
You must be signed in to change notification settings - Fork 222
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
Presence: Last seen seems to be wrongly calculated #125
Labels
stale
The item is going to be closed soon because of inactivity
Comments
Closed
Closed
This issue is stale because it has been open for 120 days with no activity. |
github-actions
bot
added
the
stale
The item is going to be closed soon because of inactivity
label
Mar 6, 2024
This issue was closed because it has been inactive for 14 days since being marked as stale. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When viewing a users details, the shown last active time seems to be calculated wrongly.
e.g.:
User was last seen 15min ago, it would calculate 20:04. A few minutes later it would still be 15min (if the users presence didn't change), but the time would be updated to 20:10, even if there wasn't an update on the homeservers database.
To Reproduce
Additional information:
As far as I could see, the used flutter-matrix-sdk doesn't store/calculate the "received" time of a presence status and probably always takes the
currentTime - last_active_ago
as the last active time.The text was updated successfully, but these errors were encountered: