...
The facts here is that chess.com is STILL charging for a service that they have now admittedly known for TWO months they can not provide. ...
The issue really started in early January. It hasn't been two months.
Completely disabling new premium and/or pausing all premium renewals would take coding work to do. Almost all work being done now is toward stabilizing the site and upgrades and changes to fix things long term. A lot of other suggested changes, by other members, would also take coding work.
Once things are stable and changes are getting implemented to move towards handling the higher loads, I would imagine there will be additional communication on low the site is going to handle everything else. Once it's known exactly how long issues were experienced, then the site will know what makes the most sense and is possible to implement. (this latter part is speculation on my part but makes the most sense to me)
Martin, I think you proved my earlier point. You appear to be a mod, and I can tell by the talking points you just put here, that you too have been lied to. I don't believe any of what you wrote not because I don't believe you, I don't even know you, but the post I read earlier said they started experiencing this enormous growth in December. That means they knew this was inevitable in December. You are being lied to, and for that I'm sorry.
With that said, if you have any sway with those lying liars who are lying to us, could you please have them expedite my refund so I can leave this site and all of us will be happier?
Thanks!
...
The facts here is that chess.com is STILL charging for a service that they have now admittedly known for TWO months they can not provide. ...
The issue really started in early January. It hasn't been two months.
Completely disabling new premium and/or pausing all premium renewals would take coding work to do. Almost all work being done now is toward stabilizing the site and upgrades and changes to fix things long term. A lot of other suggested changes, by other members, would also take coding work.
Once things are stable and changes are getting implemented to move towards handling the higher loads, I would imagine there will be additional communication on how the site is going to handle everything else. Once it's known exactly how long issues were experienced, then the site will know what makes the most sense and is possible to implement. (this latter part is speculation on my part but makes the most sense to me)