Regarding missing scores.

[choof]

For those saying "lesson learned" or "mistakes happen" or "well at least it was only scores," you are all missing a significant point.

There's been a recent influx of threads that point at staff, there's a history of people making threads about staff. Whether the community is misinformed or not about the inner workings of FFR, their concern is only perpetuated by things like this. I'm slowly moving myself away from FFR because I think, for the most part, the community's pretty toxic and the people I do care about I already have on Skype so I don't need FFR to stay in touch. But there are still people who use things like prochat, profiles, people still actively play the game. There's a lot of community investment in the site.

So, what does it say about the future of FFR when precautions are not being made to keep the community, the site, up and running?

Absolutely, without a doubt, having a 6 month old backup as the primary backup is wrong. Absolutely, without a doubt, performing experimental changes on a live site is wrong. From what I'm gathering, the only reason there even was a backup to roll back to, was due to the server move that occurred around October. Where the fuck would we be if we had to roll back scores to, like, fuckin' 2010 when the site came back up? This basically tells us that the only reason there was a backup was because the people involved in the server move were forced to make a backup (presumably by someone who's a capable and competent staff member).

Performing changes on a live set is even worse, because not only does it tell us that there is no test environment, but whatever script Velocity wrote was rash and impulsive. The raw scoring implementation should have been tested through and through. I would think that the community would have been fine with 2-3 days of site downtime to make sure everything would be working properly, but instead now we have to deal with ungodly site load times, and 6 months of "work" destroyed because someone thought it was a good idea to drop a fucking table in an environment with end users on it.

So, yeah. This was rectified pretty quickly and calmly, but that's not the issue. This never should have happened in the first place. Is this going to foreshadow what the site might see in the coming days?