[Syd Thrift]

So... if what's happening is that the game tries to upload a giant packet that includes logo/etc. information every time you save, that is a big, big opportunity for improvement. Speaking as a web developer myself, with a thin client app like this even if you're not having actual logo/etc. issues, you should only be sending images up if they've changed. In fact, if OOTPDev is sending up images *every single time* you update your rotation, etc., I could very easily see where all of the increased bandwidth on the servers could cause an issue where timeouts are plentiful and as a result logo data keeps getting reset.

Even if it's not a literal "every time" thing, even if the thin client is just a little bit too aggressive in sending up images, that could be a massive increase in bandwidth: imagine that instead of pushing up a 5k file (probably way more than you need for simple roster changes in an XML type format), you push up 1 meg worth of data. Now multiply that by thousands of users, thousands of times a day. This might be decried as a bad UX thing but I might go so far as to say that maybe there should be a separate button to upload images, and the only time you ever send them is when that separate button is clicked (and on top of that, the client needs to track changes as well so that jamming on the button would have no effect).

I have not set up Fiddler on my machine to track this because, well, I do this in my free time, but hey, someone feel free to do that...