So it is down to the client implementation, as @kyb mentioned. Every one will do it different.
In my own (still unreleased) client, I combine queries from the node with cached historical data and optimistic updates real-time. This results in consistently accurate engagement numbers. But behaviour may vary across clients as to how often they update those engagement stats per cast.
(btw I'm just a Terminus fan, not the dev, that's kyb!)
The post this replies to
Terminus needs JavaScript to show replies and pictures.