It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
The contest is delayed of 30 minutes, because of tecnical issues. Get ready to post within 25 minutes, at 18:30 CET, ok?
avatar
WrathOfTheAngels: The contest is delayed of 30 minutes (...)
Have you double-checked the script this time? ;)
Causing another massive spam wave for nothing would seem like a true crime :p
loil =) u think in 30min there will be less lag? ;-)
avatar
AdiJager: loil =) u think in 30min there will be less lag? ;-)
Are these technical issues caused by our spamarama?
avatar
WrathOfTheAngels: The contest is delayed of 30 minutes (...)
avatar
Fujek: Have you double-checked the script this time? ;)
Causing another massive spam wave for nothing would seem like a true crime :p
I checked the script a lot of time yesterday, and that error appeared only one time -.-' That should appear if there is sometingh wrong in the URL used, but URL is ok...

If there will be another problem (I hope not), I'll make a draw between the ones that posted here.
Post edited March 22, 2011 by WrathOfTheAngels
avatar
WrathOfTheAngels: That should appear if there is sometingh wrong in the URL used, but URL is ok...
There are actually other possible reasons, such as DNS lookup issues.
Have you considered using the actual IP instead and thus avoiding all the DNS resolving trouble (and delay!) ;p

Edit:
[url=http://70.38.122.100/en/forum/general/a_fast_contest]http://70.38.122.100/en/forum/general/a_fast_contest[/url] ;)
Post edited March 22, 2011 by Fujek
avatar
adambiser: Though it could have been you.
avatar
Damuna: By the time I posted, three more posts were there, inside the time limit, the third being yours.
Whichever way, it all comes down to whatever clock WrathOfTheAngels uses to check the thread.
avatar
adambiser: it all comes down to whatever clock WrathOfTheAngels uses to check the thread.
Actually, there are even more factors involved on that one.
DNS lookup time, HTTP request latency,... that could very well take up to several hundred or even a thousand milliseconds, depending on the connection and the GoG server/ networking setup.
So, in the end, it's a rather blind guess after all.
avatar
adambiser: it all comes down to whatever clock WrathOfTheAngels uses to check the thread.
avatar
Fujek: Actually, there are even more factors involved on that one.
DNS lookup time, HTTP request latency,... that could very well take up to several hundred or even a thousand milliseconds, depending on the connection and the GoG server/ networking setup.
So, in the end, it's a rather blind guess after all.
True enough (everything you said).
Seems there's no flood of posts this time
Post edited March 22, 2011 by adambiser
avatar
adambiser: True enough (everything you said).
Seems there's no flood of posts this time
Good try! ;)
Everyone leave?
avatar
Fujek: Have you double-checked the script this time? ;)
Causing another massive spam wave for nothing would seem like a true crime :p
avatar
WrathOfTheAngels: I checked the script a lot of time yesterday, and that error appeared only one time -.-' That should appear if there is sometingh wrong in the URL used, but URL is ok...

If there will be another problem (I hope not), I'll make a draw between the ones that posted here.
~ Hopefully resubmitting ~ Molto grazie WrathOfTheAngels
avatar
adambiser: True enough (everything you said).
Seems there's no flood of posts this time
avatar
Fujek: Good try! ;)
Thanks
again! again! again!
*claims*