Skip to content
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

Days in chat doesn't take into account user timezone #5281

Closed
churik opened this issue Jul 24, 2018 · 5 comments
Closed

Days in chat doesn't take into account user timezone #5281

churik opened this issue Jul 24, 2018 · 5 comments
Assignees

Comments

@churik
Copy link
Member

churik commented Jul 24, 2018

User Story

As a user, I want to see in chat history split by days according to my timezone (always started from 00:00 and to 00:00 next day)

Description

Type: Bug
Summary: in public, 1-1 chats day for every user starts at 00:00 UTC. this means that i.e. "Today" for the user from Tokyo starts at 10 AM, all messages sent before 10 AM were placed in "Yesterday" history.

Expected behavior

Every day starts from 00:00
(screen from Telegram, UTC +3)
right_beh

Actual behavior

Every day starts from UTC 00 (in my case from 3 AM)
(screen from Status, UTC +3)
img_d639ad88272e-1 jpeg 2018-07-24 15-44-56

Reproduction

Prerequisite: you should be located not in UTC 00

  • Open Status
  • Join any public channel
  • Send message in 00:01

OR

  • join #status channel
  • check messages for 23-24 Jul

Additional Information

  • Status version: status nightly 23/07/18

  • Operating System: Android, iOS

@ghost
Copy link

ghost commented Oct 22, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@ghost ghost added the stale label Oct 22, 2018
@ghost
Copy link

ghost commented Oct 22, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@churik churik removed the stale label Oct 22, 2018
@ghost
Copy link

ghost commented Oct 22, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@ghost ghost added the stale label Oct 22, 2018
@ghost
Copy link

ghost commented Oct 22, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@ghost ghost removed the stale label Oct 22, 2018
@churik
Copy link
Member Author

churik commented Nov 29, 2018

Still reproducible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants