Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
briar
briar
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 680
    • Issues 680
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 11
    • Merge Requests 11
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • briar
  • briarbriar
  • Issues
  • #1491

Closed
Open
Opened Jan 02, 2019 by Matemàtic@matContributor
  • Report abuse
  • New issue
Report abuse New issue

Future dates display as "now"

Steps to reproduce:

  • Use two devices with a 1h clock offset
  • Add both to a private group
  • Exchange messages
  • In the device which is behind, all messages will show a time of "now"

This is very confusing and makes it difficult to notice that the devices clocks are off.

Possible solution: show "invalid time" instead, to help the owner of the misconfigured device notice the issue.

The correct solution is #1098, but even if that were in place, there may be cases where this could help, and I can't think of it doing much damage.

Edited Jan 02, 2019 by Matemàtic
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: briar/briar#1491