I wonder if the problem is to do with the supernodes jumping supernodes too often...
Supernodes are just someone else's clients after all, if they are jumping supernodes too much while searching for more sources (does an automatic tool do that?), then there could very likely not be enough time elapsing for a stable network to exist, it's almost like having a changing kaleidoscope of a network. This may cause the "number of users" algorithms to behave erratically, which is what seems to be happening.
Personally, I don't think it's anything Sharman have done, especially as the problem has been reported on all versions of KMD. I also don't believe Sharman have any control over the network anymore, I believe this capability was removed to protect the network from being shut down.
