Thursday, January 14, 2016
Yes, today we were down for several hours and we would like to apologize for the inconvenience of that. Apparently, our webserver host decided to prevent access to our website while they claimed there was content in a thread that was "phishing" which violates our Terms of Service ... After notification of this, they promptly took action which was clearly unprofessional and ignorant. Speaking with one of their technical support persons - who didn't understand why I would be requesting access to the site to see this content they claimed was against the TOS - I realized they don't have our best interests in mind, as they wouldn't provide me access to see the content, nor would they let me see the "report" they received. All they provided was a link to the page, which turns out had nothing like that on it, nor does any of our site have "phishing" links or anything like that. If and when we do - they are quickly removed, and the user is banned. So, turns out they made a "mistake" - blaming their 3rd party company that deals with these reports - and brought the site back online. I told them it is not acceptable to prevent access to the site without giving me a chance to deal with reports such as that beforehand and will likely not be a customer much longer. Their response - we apologize - let us credit you a day of service ... are you kidding me?? This has got to be the most idiotic response. Of course you will credit us for the service, you thought we paid for downtime? No, we pay for uptime. Needless to say, as I have previously commented in other posts, we are looking into some upgrades this year - one of which will be finding a new host that has our best interests in mind and aren't going to make ignorant mistakes that cause unnecessary downtime. In addition to that, we are looking into changing the forum software to something more capable than what we currently are using. We appreciate the continued support and loyal membership that we have and will always attempt to give the best possible outlet for your gossiping needs! Thank you and have a Happy New Year!!!
Thursday, November 19, 2015
Sunday, November 8, 2015
Sunday, October 11, 2015
Looks like we've finally reached a point where the site is stable, due to code changes and some other behind the scenes changes, I've gotten us to a point where nothing more can be done with a single server setup. Yes, I realize I've been talking about it for months, but we are going to move to a better host with multiple servers to handle the extra load we get sometimes. On top of that I've removed offensive Tapatalk coding that was causing multiple errors. To those who think I don't know what I'm doing, please feel free to enlighten everyone with your extensive knowledge, clearly showing those who believe you, that I don't know what I'm doing. Until that happens, (which likely never will - as it hasn't happened yet) you will likely just have to deal with it. If I didn't know what I was doing, I wouldn't be here in the first place. Now quit bashing me and making up lies about what I've done or haven't done.... Because I'm sure you are the pot calling the kettle black here ... but I'm sure you feel safe posting anonymously. Lastly - to all those loyal visitors - thank you. We appreciate the fact that you stick by us, waiting patiently for a resolution. And to all those who hate - enjoy your karma.
Friday, September 18, 2015
Yes, We know, we apologize, over and over again.... However, until we are able to switch hosting providers and setup multiple servers, we will have these problems. Sorry, remember though, we are a free site, so at least you aren't paying for downtime. Please have patience, we are working to resolve this major issue... EXAMPLE ERRORS: Service Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. or error 524 from Cloudflare...
Monday, July 27, 2015
Sunday, July 5, 2015
Noted slowness today, while there are many options to resolve this issue, the decision still hasn't been made on which solution will best fit the problem. Understandably we will be working towards a faster resolution to future issues, once we've come up with the best solution to this overloading problem. Sorry for the inconvenience. Please direct all complaints directly to firstname.lastname@example.org, Thanks!