Our major goal here is to help clocks be more accurate when there is a lot of lag and make sure that when you lose connection that you can reconnect without losing access to your board.
For those of you using Chrome: you can throttle your connection to force lag like this:
Yesterday I reported a bug that club tournaments couldn't be created. But today I've discovered that turning off Beta fixes the issue. So a recent code release on Friday must have been the issue (since I create club tournaments usually every day).
Hey Beta!
This is a big one and major overhaul to clocks!
Our major goal here is to help clocks be more accurate when there is a lot of lag and make sure that when you lose connection that you can reconnect without losing access to your board.
For those of you using Chrome: you can throttle your connection to force lag like this:
https://screencast-o-matic.com/watch/cbQVrvIfYj
Please let me know if you notice anything strange with clocks jumping around or losing on time when you clock still shows you have time etc!
Also please try Long Polling and Websocket connection type.
Here is how to switch:
https://screencast-o-matic.com/watch/cbQVryIfY3
This really is an important code change and we want to make sure its great before we move this code out to everyone.
Thanks for all your helps!