What is everyones thoughts on CakePoker?

[sdfsdf]

i also cashed out yesterday, games are soft but the software is just too awful. they've been saying [censored] about working round the clock for months now and only recently have they addressed the deposit freezing bug but their "fix" caused more problems than it solved. it is seriously not hard to fix these bugs, no other site has these problems, if they fix everything i might come back but i dont think that will happen unless they fire their entire software team and hire some people that know what they are doing.

[steamboatin]

I included a link to this thread in my communications with Cake Poker Support. I doubt it makes any difference.

[JPFisher55]

I have been playing at CakePoker for about 3 weeks. I have had some freezing delay issues, but not as many as reported here.
I have only been booted from a table once.

[ilya]

It does look like they've finally fixed the worst bug (after 4 months of knowing about it!) so, umm, I guess that's better than nothing?

[mother_brain]

software still sucks, unplayable for me the last two days, and now getting flooded with 2+2ers. Good work guys.

[EvanJC]

yeah, its totally unplayable for me at the moment.

[sputnik365]

Are their servers down at the moment? haven't been able to log on for several hours.
As far as cashouts go, no prob via Neteller. Usually 1-2K. Two to four days.

[EvanJC]

site is broken.

[EvanJC]

website is also down.

"Server Error in '/' Application.
--------------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>"

str8 quality

[Naked Penguins]

it's working again