I got some information back from the datacenter as to what happened on this past Tuesday. Apparently their network technician was remotely trying to configure their switch stack to include a new client when they lost connectivity to the switch stack. The remote technician could not assist the onsite technician to fix it so that person had to drive into the datacenter to fix. It started about 5:15pm ET and lasted until about 5:45pm ET and affected 5 clients were affected. And you can guess who at least one of those clients were! At least the datacenter was transparent with the reasonings for the incident and I didn't have to do an excessive amount of digging just to find out what was going on. It was unexpected and fixed relatively quick so just wanted you all to know so you don't start pointing fingers to Chatro directly for the down time.
Sorry folks, I was at the clinic with signs of pneumonia so I missed out on an issue today where Chatro seemed to be down. By the time I got home, it seems to be back up again. If anyone wants to drop a ticket to the Help Desk to describe what all links/pages weren't working then I'll look into it further. My apologies again for not being there when it occurred.
bandwidth. So after getting some rather poignant responses from a lot of you devoted folks, some nice and some not so nice, I was given an idea by another that made me think of something all encompassing that is causing all of our issues with bounced connections, server lag, server availability loss, and this up and down roller coaster we've been on for weeks. Come to find out, not enough bandwidth to keep up with all of you wanting in to Chatropolis to enjoy. That's my mistake. The most obvious reason for the bottleneck and I inspected everything but that. I have corrected that. I reached out to the datacenter and paid for a bump in bandwidth. I'll admit bandwidth is expensive and damned near doubled the operating costs of Chatro but I feel it will easily be worth it in the long term. So it's not the software. It's not the servers, it's not the hardware, I know how to design and build a helluva server. It's just not enough allocated bandwidth. Thank you all for being patient and thank you all for your contributions to the site. Let's make it a helluva 2017.
I bet a lot of you have gotten this particular error. This is a simple error with a simple fix. Your chatting in any room is started by a chat session that is created and a session cookie is created for this chat session. However, some times when disconnected abruptly, or upon leaving and reentering too quickly (before the chat session has a chance to end), or just a chat session that gets hung up. The easiest fix for this is merely deleting your cookies. Deleting that chat session cookie will force the server to request the browser to create and store another cookie for that new session. I get this at the Help Desk quite a bit and you all really do need to know what's up with that so you can quickly get back to chatting again.
Did you know as a member you can reserve URLs the same way you can your screen name? Yes you can. You can reserve up to 5 URLs at any one time. Why would I add this feature? Well we all know of impers that snag your favorite avatar URL and make them their own as they impersonate you. Well that comes to an end. You reserve your favorite URLs and that can't happen. I figure 5 URLs for starters "should" be enough as the life cycle of avatars tend to be short before "on to the next one" but I'll consider upping that limit to accommodate if necessary.