I doubt live support care whether a player posts to Casinomeister or not. Such threats seem to make little difference, so don't threaten, just do it!
In a similar vein, problems that have been brought to their attention again & again, with empty promises to deal with it seemingly never lived up to.
Today, bog standard weekend match, but rather than having any bonus credited automatically, it now has to be claimed first.
1) Claim
2) Purchase
3) Action
Well,
I didn't even make it past 1)
(PS. The claims link IS THROUGH C-F-1.com!!!!!!!)
This might work BETTER if a "plain vanilla" URL was used, rather than this "via c-f-1.com" construct, which is like going from New York to Vegas via London
This error happens again & again, but was mostly fixed by changing over to an automatic crediting system, with no need to claim. WHY change back then to a failed system, one which AGAIN failed in it's first week back in operation - rather proving my point.
Server Error in '/' Application.
--------------------------------------------------------------------------------
Request timed out.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.HttpException: Request timed out.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[HttpException (0x80004005): Request timed out.]
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.3082; ASP.NET Version:2.0.50727.3082