Yeah, but I think @jlt was arguing in that example that blacks winrate would have to be like 80% or something for it to perfectly balance out the gains/losses over time.
Edit:
I didn’t sit down to find out where the problem lies. Was in glicko, the implementation of glicko, my specific translation of the python code into JavaScript for the calculator (not the rating code, just predicting the changes).
It definitely fell out of sync with the GitHub repo though, since I think there was some tweaks to play around with the uncertainty over time, and probability of winning functions and things.
We were discussing some bit of rating math there. For example what the probability of winning should be with glicko.