cocoaforge

OK, I don't know if this is an Adium issue or a Yahoo issue:

I'm using Adium 1.0.1, buddy is using Yahoo (either on PC or Mac). We chat back & forth, them we stop getting messages from each other. We don't know the other sent anything. We can see what we sent the other person, but apparently, it's not getting through to them. Weird thing too is that when that person logs off, you see it happen. Oh, and the whole time we appear to be online, just rude and unresponsive (that is until someone logs off, then you see that action.)

SOMETIMES it seems like after logging off of Adium and logging back in messages they sent come though. Not always. And they come through with a weirdly late timestamp. Hours after conversation ended, during an offline period of time.

Weirdest is that it happens to BOTH of us, and I am the only one using Adium, so I am inclined to think this is a Yahoo issue. Thoughts?

Anyone else getting this and is it Y!? I'm thinking about just using Y Messenger for a few days to see if it happens there.

The same thing has been happening to me.

Except I'm usually using AOL. Sometimes my buddy doesn't see my IM and I don't see his. Seems to be rather sporadic.

I thought that it was his computer or connection or something, but it seems to have happened with another friend this morning on Yahoo, so maybe Adium is the problem.

It seems to have only been doing this very recently.

same here.
It all started with Adium 1.0 and 1.0.1 is the same.
I'm using gaim on the same network, no trouble at all.

Compare your server settings in Adium to those in Gaim. There should be nothing different between how Adium and Gaim 2.0.0b interact with the Yahoo servers.

I think I'll try some testing this week to see if I can narrow it down. I prefer Adium, but I'll keep one account signed in with YIM. If we seem to have that silence, I'll message him from another account on YIM to see if that gets through. That may eliminate one of the clients as the responsible element.

If I find anything out (hard since this is sooo sporadic), I'll let the developers know.

The only other thing I have seen is where messages get mixed up in chat history when a contact disappears from your contacts. I disappeared from my housemate's (running Adium 1.0.1) and his history with me got jumbled with someone else. A bunch of log-ins and log-offs (including with the YIM client) got me to reappear on his contacts list (but the history is still gone).

Thanks.

I've been having this problem, between myself and Y!IM users, for several weeks now.

Unfortunately, I started having these problems on 0.89.1, which is why I upgraded to 1.0/1.0.1 in the first place! Mid-conversation, I'd either stop seeing messages from people, or they'd stop seeing messages from me.

Additionally, I think I may have screwed up my logs by switching back and forth between 1.X and 0.89.1. Now, some chat sessions show up blank, and occasionally, Adium 1.0.1 crashes out when opening the Transcripts Viewer.

Is there a utility to down-convert my logs, so I can try 0.89.X again? This problem is so serious, I'm thinking of switching away from Adium, but I don't want to lose my logs...

1.0 logs will not display in .89.1 but they are not deleted or screwed up. There is no back conversion. Also, the most likely fix for the transcript viewer crash will be in 1.0.2

This problem happens to me quite frequently too after switching to 1.0+. I'm going to switch back to 0.89.1 to see if this will fix it temporarily.

It's unfortunate that version 1.0 is so nice but is infected with this major bug.

I have encountered this problem recently.

My friend is also using Adium 1.0. I can see him typing but I don't get his messages; although he receives mine. So our temporary workaround for this is just to Initiate a conference with him/her and our messages will go through.

I suspect the problem lies with the encryption. A day before, I was notified by Adium that an encryption/fingerprint thing is in place. After I deleted that encryption in the Advanced preferences, everything was back to normal.

I am not sure if this is also the case with you guys. Hope this major bug gets resolved soon.