Yeah, this has to do with latency from the server, and the way we currently manage the client state. I think we should be able to build something that’s more stable here that does some more intelligent merging of client and server state (right now we just override the client state with the server response whenever it comes in, and that can sometimes cause your actions to replay, if you made a bunch of them in series before the first server response comes back).
Actually, I just found out that we had an unoptimized database query for the votes on a document in our DB, which made it so that it sometimes took up to a second for us to retrieve the correct result. This should now be fixed, and I expect the whole thing to be much less laggy from now.
Yeah, this has to do with latency from the server, and the way we currently manage the client state. I think we should be able to build something that’s more stable here that does some more intelligent merging of client and server state (right now we just override the client state with the server response whenever it comes in, and that can sometimes cause your actions to replay, if you made a bunch of them in series before the first server response comes back).
Actually, I just found out that we had an unoptimized database query for the votes on a document in our DB, which made it so that it sometimes took up to a second for us to retrieve the correct result. This should now be fixed, and I expect the whole thing to be much less laggy from now.