[qwertyuiop924]

Yep. Lots of other people are getting this, too. And it sucks. They all seem to be server load problems, but what gets me is that some things just don't need server updates, and they do them anyway. Oh, so you need to check in with the server every time I toss a pokéball. Niantic, it's like you've never heard of caching, combining packets, and client side prediction, or anything clientside for that matter. Sure it's not as secure, but what are you more afraid of, people commiting fraud on your trivial pokeball tossing minigame, or people uninstalling your crashy, broken game, because you didn't understand that releasing a good, free game based on one of the most popular game series the world has ever known would result in a lot of popularity, and that you maybe should have optimized for bandwith? Mmm. I can almost taste the lag.

[lnanek2]

Yeah, the server loading indicator every ball toss is grueling. It would be OK if it was reliable and always loaded after a few minutes, but a large portion of the time it locks up after several failed attempts to talk to the server and you have to kill the app. Then starting the app again shows the server error page 9/10 times, then you have to try the ball toss again, which may or may not work.

[qwertyuiop924]

Well then, why do it? Sure, it lessens the chance of a ball dupe, but is that really worth ddosing yourself over?