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

Avoid using the client clock for anything #6

Open
Amalthea opened this Issue Jun 2, 2011 · 2 comments

Comments

Projects
None yet
3 participants
@Amalthea
Collaborator

Amalthea commented Jun 2, 2011

Twinkle uses the client clock for numerous tasks: section headers in user warnings and list pages for various XfD tasks come to mind.
Since client clocks are often a bit off (this comes up regularly), it would be beneficial to ask the server for the time, and use that one.

@hartman

This comment has been minimized.

Show comment
Hide comment
@hartman

hartman Jun 5, 2011

Collaborator

When you request a page for later editing from the api, you already get the starttimestamp in UTC. Can't that be reused ?

Collaborator

hartman commented Jun 5, 2011

When you request a page for later editing from the api, you already get the starttimestamp in UTC. Can't that be reused ?

@Amalthea

This comment has been minimized.

Show comment
Hide comment
@Amalthea

Amalthea Jun 5, 2011

Collaborator

Of course, very good! I kept thinking it needed another request to expand #time or something.

Collaborator

Amalthea commented Jun 5, 2011

Of course, very good! I kept thinking it needed another request to expand #time or something.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment