The Old Chat Is Back – wtf

Word was that the original chat aka the old chat was destroyed and lost forever.

old-chat-back-none-in-room

Yes. The OC as we had it before was terminated, and I had lost the install files and everything. Our original code partners with this OC system bailed years ago – all was lost.

The New Chat is Old and a newer chat coming

Somewhere around mid-October (estimating) we started having congestion issues with the NC system causing lag and disconnects – and this led to additional problems with the MV Chat system as well. For many weeks our visitors have likely dealt with slow connections, and some down time. We’ve been working to sort the issues, tried several things, and had some patches, but things are just not as smooth as they should be.

It may be that the old code for the NC is just not going to make it much longer. We’ve tried patches, and updates, but this old code base was made with different hardware and software in mind.

Coming changes to the new chats

I’ve got a long list of upcoming changes to the new chats that are being worked on. Some of these changes will be a huge change in the way things work, many are minor improvements suggested by users, and some will be in the update pipeline for some time later this year.

Old Chat Post Mortem

I’d love to have accurate stats for the amount of people that have used and enjoyed the OC aka Original Chat aka Old Chat system. From watching some logs over the years I have a few numbers I can guesstimate, but we have not kept the kind of logs that many other web sites consider gold. I do know that a lot of people have used our OC system over the years, and I assume that at least a percentage of those that did had some fun!

The Old Chat Not Coming Back

Lots of people loved the OC, and I was certainly one them. More about that in the post mortem post to follow.

Details here are to the best of my knowledge, but some things are guesses without confirmation from people that are actually there, however if you read the associated news stories, I think you may agree that this all makes sense.

what happened?

hiccup de ja vu in the sex chat matrix

Some may have noticed a little hiccup, and perhaps experienced a bit of de ja vu in our little sex chat matrix here in the past several hours, and perhaps the bigger picture of the past couple weeks has been a bit of that as well. I am guessing that most people would not have noticed a rewind of our systems, at least I hope there was as little impact as possible.

In my quest for excellent security I decided to put a pause on the peeps section, and there was a brief interruption of the blog section and the associated pages. Moved some files and changed some things, then went back to the data that was live a few hours previously.

privacy policy update mar 16

Added some additional information to the sites privacy policy today. Also updated some of the info on the privacy info page made for the peeps / mv-chat systems on that page.

Read the added info on the privacy policy page here: http://www.sexchatsexchat.com/html/sex-chat-privacy.html#03222016

Tried to answer some QnA and about registering the peeps section and using the mv-chat here: http://www.sexchatsexchat.com/peeps/peeps-registering-info/

and then realized we should add that info to the main privacy page, and got to writing, so I added a bit more info on the main privacy page.

User levels coming

We’ve been kicking around this idea for a long time, and now it seems we have little choice but to start creating user levels.

Whatever system we start with will likely change drastically, so don’t think whatever we start out with is going to be the system that everybody must deal with forever. I’m also looking for ideas and feedback from everyone to make the system better. I have some ideas, and hopefully others will be able to chime in and make them better.

scsc-user-levels-up

Something like this:

broken anti-spam token prevented comments

Apparently some people were not able to leave comments here in the blog section for a while due to some server permissions error that prevented our “anti-spam captcha” thing from working properly. Big apologies to anyone who tried to leave a comment here and then got some weird frustrating token error or something. I have removed this captcha thing for today while I investigate what the issue was.

broken-token-fail

Blog Comments and Notifications changes / updates

In the process of rolling out some updates for the blog section.

At this time this update has causes some changes to the commenting system, and any previous “subscribe to comments” notifications. In the middle of this update I realized that we had lost all of the comment subscriptions / notifications settings! I know many of our users depend on the email notifications they would get when new comments were added to some of our popular pages, so I am trying to determine if we should revert back to our old code.