That causes the browser to block waiting for a response.
It was a couple months ago, but I think it was olark19 not responding.
While I appreciate what you guys are doing a lot, I'm not willing to be a beta tester for your networking. Stuff like that absolutely needs to be hosted on an architecture that just doesn't go down. Ever.
<script src="http://server.not.responding.com></script>;
That causes the browser to block waiting for a response.
It was a couple months ago, but I think it was olark19 not responding.
While I appreciate what you guys are doing a lot, I'm not willing to be a beta tester for your networking. Stuff like that absolutely needs to be hosted on an architecture that just doesn't go down. Ever.