Admin Steven Nash

Steven Nash authors many posts and pages here at the sex chat sexchat blog, and other areas of the site here. An accomplished sex fiend who loves to talk, chat, read, and listen.
Began reading books about sex in 1984, and still obsessed with most things sexual. Loves to talk about sex and listen to other's experiences. Looks forward to more of the world learning about Tantric sexual energy practices and furthering research and development with tantra and similar arts.
Enjoys Tai Chi, books, and music of all types. Listens to EDM (electronic dance music), trance, chill-hop, electro swing, progressive, psy chill, and similar genres while coding, learning, and readings / answering support emails and comments here at SCSC.
Is available for sexual liaisons on occasion.

Had the peeps cams chat aka the new chat up and running, then got some emails about it being down. Got it fixed up and then it crashed again. I was not surprised, as the underlying tech for this cool system is ancient in internet years. I got it back up and running again and then dig some digging to see if it was an issue I could easily get a clue about, when I found a terrible chunk of code that has been plaguing me for the past few weeks with another system I’ve been working on.

We finally got some new code put into the mv chat system! I believe this update will fix the biggest problem that our core groups of users were having with the user created rooms aka side rooms. There was a weird bug before where the option to kick people out of a user created side room was not working – this update fixes that!

Did some blog code updates that mainly deal with the theme/presentation of the pages and posts. You may notice a few subtle changes here and there, and many of you will likely not notice any changes at all since most of you stay in the chat rooms the whole time you are on site here. Either way, it was time for some code updates and I decided to tweak a few more things here and there within the blog area here while I was messing with it.

Quite surprised to see so many really want the “new chat” to stay up and running. We are working on several other systems, but the tekor system is not ready for public testing, so I worked out a deal with our hosting company that handles that particular server that the old new chat aka peeps cams chat is running on. It cost a couple hundred bucks, but I’ve got it up and running again for another 30 days.

Parts of Instagram’s terms of Service were broken down into simple English by a lawyer. It took hours, and they did it for the children. Tests show they don’t understand the terms of use, it’s too complicated. I’m betting they don’t understand the basic tech enough either, and they are the lucky ones growing up with it.

I don’t think most of the popular apps today are any different, and I would love to see this same breakdown done with other apps’s terms and permissions, by a professional, like it was done here.

Many people called it the ‘new chat’ for years, it’s not the newest, and it’s not the oldest, but it appears that the NC system will reach it’s end of life In January. I plan to keep it running up to Jan 29th if possible. It has been and continues to act really wonky – lagging big time, and not connecting other times.

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.

Reading about a recent hack / data breach and leak from the friend finder network, which includes cams.com and adult friend finder (both sponsors of our systems) – and others. This is another leak of registered user information that includes perhaps 400 million users – this is different than the hack and leak of data that network had in May of 2015 that leaked 3 1/2 million user credentials.

I don’t have all the details at this time or know exactly what was leaked and what was not. Apparently some of the info like passwords for some people was encrypted with a crappy method that makes cracking that encryption frivolously easy. It appears that 99% of the passwords have already been cracked.

Our chats are not under direct attack, but the amount of internet congestion that is being created with these latest attacks against other people are slowing down huge chunks of the internet, and that is a problem for our chat systems that need to have a constant on / consistent connection in order to function properly.