32GG Sara Willis

Actually, I don't think the page has crashed. We think this may be related to the IP limiter they always had on the site. They have always had a limiter on it that prevented people from refreshing the page infinitely and racking up pixels each time and there was a limit of 10 total per IP address. We believe now what's happening is that if you get past 10 and try it again, you get that server crashing error. If some of you want to try this and see, please post your feedback.
 
Actually, I don't think the page has crashed. We think this may be related to the IP limiter they always had on the site. They have always had a limiter on it that prevented people from refreshing the page infinitely and racking up pixels each time and there was a limit of 10 total per IP address. We believe now what's happening is that if you get past 10 and try it again, you get that server crashing error. If some of you want to try this and see, please post your feedback.

After refreshing 10 times I got this...

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>
 
Yeah, okay... that all makes sense. We've let them know about the error. In the meantime, we are rapidly approaching 200,000...
 
Two days later and it's over 282,000 now. Not bad.
 
Flew past the 300,000 mark -- nice work, everyone.

Premium Link Upgrade
 
About 30000 pixels in 12 hours. If that speed would be constant, this will happen in the next 8 days. Of course it's not going to remain constant, it's just going to accelerate as more people become aware of this. So she's not going to be bogged down with that shitty contract with candycrib for too much longer..
 
Just ****** the 700,000 mark... :)
 
Blasted past the 800,000 mark...


Premium Link Upgrade
 
Pixels Revealed: 859,577
Pixels Remaining: 140,423

We should be able to hit the 1 million mark sometime early this coming week.
 
It's over 900,000 now so I'm guessing sometime late Monday evening.

Premium Link Upgrade

BTW, Trance who is the gal in your sig?
 
Back
Top