PDA

View Full Version : chat: another user already has that username

Clutch Munny
12-17-2004, 10:39 PM
That's what I always get when I try to log on to chat.

Is this just because Safari blows?

Or is it yet another case of me being e-nept?
livius drusus
12-17-2004, 10:45 PM
Poop. If you get on once and then get dropped it takes a while before the database realizes you're gone. Let me see if I can poke at something without utterly destroying the room like I did last time.

Meanwhile, it's nice to know Farren, lisa and I don't have BO or something.
Clutch Munny
12-17-2004, 10:56 PM
Well, the thing is, I've never been on. At least, not for more than one second before I get that message. Then I just get the login screen, and no matter what name I then type in, I get the aforementioned kick twixt the pockets.

Unless all those names happen to be taken by chatters already (Flaming Dogdish, Snoochie, helplesstechie, etc.) there's something more systemically wrong with my connection to the chat server.
livius drusus
12-17-2004, 10:59 PM
Ooohhh... Okay that sucks quite a bit. I've made a dummy username for you (check PM). Let's see what happens when you try that one.
Clutch Munny
12-17-2004, 11:03 PM
Nope. Just for a second, then off I go.

Ah, well. Thanks tons for trying.
livius drusus
12-17-2004, 11:04 PM
Sorry, Clutch. You wouldn't happen to have another browser lying around, would ya? Firefox is always available for weddings and bar mitzvahs.
viscousmemories
12-18-2004, 06:13 AM
Update: Clutch was able to get in using IE, so it appears to be a conflict between the chat program and Safari. All I can say for now is anyone who wants to chat should use IE or Firefox for the time being.
pzmyers
12-18-2004, 05:22 PM
I just tried it using Safari 1.2.4 (v125.12), using Mac OS X 10.3.6. No problems.

Of course, no one else was there, so maybe that's why there was no conflict.



The conversation was scintillating, by the way. It would only have degraded the quality of the discussion if anyone else had been there.
Clutch Munny
12-18-2004, 05:41 PM
I just tried it using Safari 1.2.4 (v125.12), using Mac OS X 10.3.6. No problems.


So it might have been my Safari 0.0.0, run on OS 10.2.huh? that was the hiccup.