@RwSF75 said:
Why did I bother linking the source code if you are just going to ignore it and say "I'm pretty sure"...
Sorry, I didn't see your post. So it looks like it is based on the time control and only checks the last and second to last move, like you said.
@ronin3b said:
It happened many times in a row to my games in the past. Not recently, but still.
Maybe the algorithm was more aggressive then (see commits e7cc6e2 and 776c108 made in 2021 for example), but like I said, I've never had it happen to me many times in a row. I don't think I've ever had it happen even twice in a row.
I don't like your accusatory, ad-personam tone, by the way.
Sorry if you interpreted it like that, because that wasn't my intention. I was simply stating my viewpoint that it extremely rarely happens to me, and was asking if it happens frequently to you (which it sounds like it did), or if you are guessing that it might happen frequently to other people.
If you are going to have that tone, I'd recommend you check your sources first, as also Rw pointed out, as it seems the one "just guessing" is you.
You're right, I should've checked. I was just too lazy to look it up myself, and I missed @RwSF75's post.
Anyway, I still stand by not having the "unreasonable time" in the message itself, since it would allow malicious users to more easily cheat the system (by waiting just under the unreasonable time). Of course it is easy to calculate yourself, but most people aren't going to do that.
@RwSF75 said:
> Why did I bother linking the source code if you are just going to ignore it and say "I'm pretty sure"...
Sorry, I didn't see your post. So it looks like it is based on the time control and only checks the last and second to last move, like you said.
@ronin3b said:
> It happened many times in a row to my games in the past. Not recently, but still.
Maybe the algorithm was more aggressive then (see commits e7cc6e2 and 776c108 made in 2021 for example), but like I said, I've never had it happen to me many times in a row. I don't think I've ever had it happen even twice in a row.
> I don't like your accusatory, ad-personam tone, by the way.
Sorry if you interpreted it like that, because that wasn't my intention. I was simply stating my viewpoint that it extremely rarely happens to me, and was asking if it happens frequently to you (which it sounds like it did), or if you are guessing that it might happen frequently to other people.
> If you are going to have that tone, I'd recommend you check your sources first, as also Rw pointed out, as it seems the one "just guessing" is you.
You're right, I should've checked. I was just too lazy to look it up myself, and I missed @RwSF75's post.
Anyway, I still stand by not having the "unreasonable time" in the message itself, since it would allow malicious users to more easily cheat the system (by waiting just under the unreasonable time). Of course it is easy to calculate yourself, but most people aren't going to do that.