Lag compensation is flawed????

Reposting here, like I probably should've done in the first place

When I make a series of pre-moves, I lose considerably more time than I should. I don't know why, but here is proof:

http://puu.sh/lBLMt/2f6e588a8c.mp4

Notice how I lost ~200 ms (+/- 50) on the first pre-move, which, according to this: lichess.org/lag would suggest that my ping when I made the move was 200 ms higher than my average ping (see: "After your move, your average network lag is added to your clock")

Since my ping when I made the move was ~616, this would mean that my average ping is around 416 (+/- 50)

I can make another clip showing my ping fluctuate for several hours if you want, but it will show that my average ping is definitely NOT 400, not even close. I personally haven't seen it fall below 500 ever, and most of the time it's over 650 (meaning that my ping at the time of my first move was actually lower than average, and thus I definitely shouldn't have lost any time at all for that move)

The effect is more pronounced on one of the subsequent premoves where I lost ~400 ms (+/- 50). That would mean my ping was 400 ms above average, when my ping was ~600, meaning an average ping of 200

Is that even physically possible from Australia to France? Either I'm missing something or your lag compensation doesn't work

True, same. I can lose 0.1 ms every premove, just because, as I suppose, of ping variations. It would be interesting to research would one lose his milliseconds, if he has stable ping (it needs to be checked both for big pings and low pings, but stable).

I live in New Zealand, and pretty sure ping compensation doesn't work as well...

Especially when you premove endgames and still end up losing on time even though it was a goddamn premove !

@Chesstroll

I don't think it's because of variations because if it really added the average time back to the clock like Lichess claims, the only way to explain my time loss would be if my average ping was significantly lower than it actually is.

A probable solution for gamers: latency fix

To see if the ping problem is local, I would try this:
Command prompt > Cmd
Run > tracert lichess.org

Toscani, and what should be in the result of tracert lichess.org/?

Трассировка маршрута к lichess.org [5.196.91.160]
с максимальным числом прыжков 30:

1 6 ms 7 ms 6 ms MyRouter.Home [192.168.1.1]
2 12 ms 9 ms 12 ms 109-184-128-1.dynamic.mts-nn.ru [109.184.128.1]

3 18 ms 13 ms 10 ms 79.126.125.192
4 13 ms 5 ms 5 ms ae0.nnov.igw1.vt.ru [79.126.126.153]
5 25 ms 10 ms 4 ms 188.254.78.5
6 64 ms 61 ms 63 ms 95.167.95.87
7 * * * Превышен интервал ожидания для запроса.
8 74 ms 70 ms 70 ms sbg-g2-a9.fr.eu [37.187.232.94]
9 79 ms 75 ms 74 ms gsw-1-a9.fr.eu [94.23.122.117]
10 78 ms 80 ms 91 ms gra-g1-a9.fr.eu [94.23.122.84]
11 85 ms 84 ms 86 ms gra-3a-a9.fr.eu [37.187.231.86]
12 82 ms 85 ms 87 ms ns351169.ip-5-196-91.eu [5.196.91.160]

Трассировка завершена.

And what is latency fix?

Toscani, there is no ping problem. I can accept high ping, because I live far away.

The problem is with 'lag compensation'. If you look at this page:
lichess.org/lag
you will see the claim that "After your move, your average network lag is added to your clock. As a result, having a higher network lag than your opponent is not a handicap!"

What I am trying to prove is that this is not true. Having high ping IS a handicap.

Ok, what I want to say:
Let's say you do first 3 moves with ping = 100 ms. So you get 100 ms on 2nd, 3rd, 4th moves. But let's say on 4th move, your ping jumps to 300ms. What is average? 150ms. So you get 150 ms on your 4th move. So you lose 150 ms.
I should guess that you will get them later, because if your 5th move will be with ping = 100 ms, you, it seems, should get about 130 ms, right? But no. Never when I played I saw that if I have, for example, 2,4 seconds on my clock, on my next move it becomes 2,5. It never can be more than it was. So, if your ping goes up sharply, you lose your time, because on next moves, you are not compensated. If you would be, we would see such situations, where once you have 24,5 seconds, and on the next move we have 24,6 seconds. But I never saw this.

Exactly. I proved this in my first post. If I lost 200 ms on my first move, that means my ping must have been 200 ms above the average ping IF compensation worked. For my second move, it must have been 400 ms over. Since both these cases are false (my ping was 600 and my average ping is DEFINITELY neither 400 nor 200, even accounting for the +/- 50 measurement error), lag compensation clearly wasn't working as intended

Having high ping, lot of lag, is certainly a bad thing, in general, and probably more so for your opponent than for you, because you are used to your own lag. Any kind of problem with the server's attempt to compensate for it I would consider rather secondary. But that's just an opinion, of course.