@IamNOTamod said in #20:
> > > You did have a few seconds. You lost the game 10.7 seconds after your opponent moved. Of course it's your fault - you could have easily done it in 0 seconds simply by not quitting the game! You even had to accept a confirmation dialog! (I don't think the site can customize the dialog, so it would have just said "changes you have made will not be saved", but you're supposed to infer that you'll lose whatever you were doing if you accept).
> >
> > How did you know that? You calculated it or you have the timestamp of the moves?
> >
>
> Both are possible.
I know.
I saw you downvoted but your only answer is a nitpick so you don't like what I said but can't produce a simple rebuttal meaning I'm right even if you don't like it.
lichess dev here. The timer is like 90 seconds for normally but is much shorter if you're active on a different lichess page (i.e. if the server thinks you've gone off to play a different game). This is probably what triggered, although obviously was not correct here. Maybe the issue was other tabs open, I'm not sure.
@HommeSaoul said in #21:
> > > > You did have a few seconds. You lost the game 10.7 seconds after your opponent moved. Of course it's your fault - you could have easily done it in 0 seconds simply by not quitting the game! You even had to accept a confirmation dialog! (I don't think the site can customize the dialog, so it would have just said "changes you have made will not be saved", but you're supposed to infer that you'll lose whatever you were doing if you accept).
> > >
> > > How did you know that? You calculated it or you have the timestamp of the moves?
> > >
> >
> > Both are possible.
>
> I know.
>
> I saw you downvoted but your only answer is a nitpick so you don't like what I said but can't produce a simple rebuttal meaning I'm right even if you don't like it.
Nope, it means you're wrong but I considered the energy expenditure for a full-length response to be...not worth it.
@isaacly said in #22:
> lichess dev here. The timer is like 90 seconds for normally but is much shorter if you're active on a different lichess page (i.e. if the server thinks you've gone off to play a different game). This is probably what triggered, although obviously was not correct here. Maybe the issue was other tabs open, I'm not sure.
Interesting, I don't think I had other tabs open but, could it be possible that the timer start even when it is the opponent turn? If it does then that probably explains it.
@IamNOTamod said in #23:
> > > > > You did have a few seconds. You lost the game 10.7 seconds after your opponent moved. Of course it's your fault - you could have easily done it in 0 seconds simply by not quitting the game! You even had to accept a confirmation dialog! (I don't think the site can customize the dialog, so it would have just said "changes you have made will not be saved", but you're supposed to infer that you'll lose whatever you were doing if you accept).
> > > >
> > > > How did you know that? You calculated it or you have the timestamp of the moves?
> > > >
> > >
> > > Both are possible.
> >
> > I know.
> >
> > I saw you downvoted but your only answer is a nitpick so you don't like what I said but can't produce a simple rebuttal meaning I'm right even if you don't like it.
>
> Nope, it means you're wrong but I considered the energy expenditure for a full-length response to be...not worth it.
Okay good talking to you, I don't even see why you are fighting me for something that seems so reasonable.
"Adding 120s before offering the opponent the option to force resign in classical?" How dare he suggest that? Quick the pitchforks! lol.
I tested it on a local version and my result is that it waits 10s.
When both players have accounts and the game is ongoing (I tested it after >10 moves to be sure), after one user leave on their own turn, the opponent sees a timer of 10s after which they can force a victory.
If A and B play and it's B turn, B he only see the option after they played their move but the timer actually started the moment A the opponent left meaning it's not even 10s in many cases, in can be instantaneous.
I'm only talking about the local version, with ws enabled, I'm not a lichess dev so I don't know if I'm missing something but it seems to mirror what happened in my game so I think that's right.
And I don't know if that's wanted, but it doesn't seem adapted to classical to me.
I think I always got to wait much more than 10 seconds.
@HommeSaoul said in #26:
> If A and B play and it's B turn, B he only see the option after they played their move but the timer actually started the moment A the opponent left meaning it's not even 10s in many cases, in can be instantaneous.
This would not be a problem, as A had the allotted time to reconnect (whichever it was in this case). It is benefitting B, but not hurting A. But I guess you could still argue that there's no need to be at the board when it's not your move.
@nadjarostowa said in #27:
> I think I always got to wait much more than 10 seconds.
>
Also I only tested when the user close the tab AND click on the popup, perhaps the rule change when they disconnect without clicking it.
> This would not be a problem, as A had the allotted time to reconnect (whichever it was in this case). It is benefitting B, but not hurting A. But I guess you could still argue that there's no need to be at the board when it's not your move.
Yes you're right, that was probably the thinking behind this, it makes sense.
10s is perfect for bullet and faster tc but too short for the other time controls imo but yes probably it's not a bug.
Just fyi: timeout also is shorter on shorter time control. 90s is my rough recollection for classic TC when the account is disconnected and not active on something else (like playing another game).