3 ms·

I gave it fifteen minutes and bailed.

• jqueryin 16y ago
  Thanks for the reply. I'll check the error and access log files from this morning and see if there's anything fishy going on. It's not uncommon for it to take 5 minutes, but 15 is definitely indicative of something far worse... EDIT: found one issue; the secondary server was missing php-mbstring, which caused problems with my utf-8 checks and conversions. sorry!
  • mikecane 16y ago
    Does it matter that I was coming in with Firefox 2.x? Never had any problems with other Twitter API services.
    • mikecane 16y ago
      OK, I started it a second time, let it churn while I was busy with other things ... half hour later, still churning. Not going for a third time.