Some notes about the transition from API 2.5 to API 3.0
Posted by Suzanna Soyinka on December 27 2014 17:07:09
Just a heads up. We've identified a few problems with the roll out of CCS 1.0.5, one of those problems appears that due to API 2.5 still being the API standard, a few individuals who I won't directly name have taken it upon themselves to attempt to disrupt the release by abusing the dynchan.

Now...I should bring up that the only reason this can be done is because the API is still in the process of being swapped over to the new system.

I could have very easily shut down API 2.5 and told people to like it or lump it. But I wanted to be considerate of our players and the money they have spent on weapons over the years, so I set up the 2.5 to 3.0 release scenario to be a slow shift, also with the intention to give our 3rd party developers a 60 day period to update their weapons to the 3.0 system before shutting down 2.5 entirely.

One thing certain individuals can still do is mess with meters via the API 2.5 dynchan...mostly just meter resets, level up notices and the like, nothing horrific...its also possible for these people to go into high volume combat regions and spam the dynchan and cause region performance and CCS performance to tank as well.

Now, this isn't me dodging the responsibility that the meter will need to have further testing and potential patches if we identify problems with how our system is working. But the recent problems reported to me are all mostly attributed not to actual problems with the meters, but a few...rather unfortunate individuals that have made it their business, while in SL, to attempt to disrupt CCS at any level possible. And I could go into a long winded explanation as to why they do it, but I won't bother, because in the end it really won't matter what I say, people will believe whatever they want to believe. But I can assure you that their issues with CCS are mostly based in self interest and the fact that they were denied access to the API and/or banned from Second Life for selling modified viewer executables designed to allow individual users to exploit CCS.

Anyways, simple facts are the only reason this is happening at all, is because the API 2.5 door is still open, we do have the 3.0 API done, its being encrypted and as soon as we can get the bulk of the weapon base shifted over to it (keep in mind some older developers may not update their weapons at all and we do not have any control over that..they just may no longer be in SL at all), we will shut down API 2.5 and this becomes a non-issue from there.

So overall most of the problems currently being seen with the 1.0.5 meter can be attributed to a small handful of people making a minor effort to attempt to make 1.0.5 look like "it doesn't work" and or "isn't secure"...when the only reason they can do that is because I've tried to be considerate to our players in regards to the money they've spent on weapons. I could very well have shut the API down entirely til the 3.0 API was implemented and told you all to fight with rocks and sticks...but I didn't feel that was very considerate as approaches go. good deed goes unpunished right? Hopefully this gives people a frame of reference on some current issues as they've been reported with the 1.0.5 meter. Its not the meter, its just a bunch of assholes abusing a door we had to leave temporarily open to try to show everyone how smart they are.

Advice to region owners, should you notice any CCS oddities or bad performance, check your region list for names you don't really recognize, I'd be interested in the names you find to check them against the data I'm getting server side.

Anyways, sorry for the bumpy road here, and...sorry that people, are, sometimes, assholes. But we're working as fast as we can to make it a moot issue. CCS 1.0.5 was one part of the solution, the other part is finally getting API 3.0 out to replace 2.5....and from there, it won't really matter how clever someone is.