cocoaforge

I looked into the trac.... but the keyword ICQ provided too many results

I have a contact using AdiumX, I use AdiumX myself sometimes, and I use Trillian on my Windows machine. After the recent ICQ protocol change (and probably AIM as well), most ICQ messages didn't get through. Trillian has by now fixed their plugin, but I still have problems with some ICQ contacts using AdiumX (and all others when I use it myself).

I can of course use Jabber in the meantime, but it would be nice if AdiumX would soon be back to ICQ ^^ (already updated to 0.89, but that didn't fix anything in that regard yet)

More about the protocol change:
http://www.ceruleanstudios.com/forums/s ... adid=79067
http://www.heise.de/newsticker/meldung/69505

Same Problem here. It seems to me, that the length of the message is associated with this bug (longer messages don't get through).

Length? Interesting idea...
I had the feeling that it also had to do with linebreaks...
Could be the same - longer messages have a bigger chance to have line breaks

CCRDude wrote:I looked into the trac.... but the keyword ICQ provided too many results

So instead of filing a ticket, you made a forum thread?

Go file a ticket

Yes I did

First because I wanted more details before doing that (a developer myself, I hate lazy incomplete cases) and I thought the forum could provide more details before filing a ticket.

Second because I used that bug search, and it's 201 entries where more than I cared to read through I now went through the ticket reports, and found the proper one (and also the duplicates I wanted to avoid ) here:

http://trac.adiumx.com/ticket/3038
http://trac.adiumx.com/ticket/3024

So lets hope for a quick fix

Something to keep in mind:

If you want developers to volunteer their time to fix problems you should be willing to take the time to make it as easy as possible for them to do so.

Trac is the bug tracking system, and whether it seems daunting or not, it's what is used and the forums are simply for discussion.

I'm not quite understanding what you mean?

I was willing to invest the time to discuss this here first - to maybe get more details from NON developers that could be filed later so that the developers would need less time to investigate themselves - and you're telling me that was the wrong way?

Thanks, next time when I don't have enough information for a bug entry, I won't come to the forums to ask for more information that could be provided in the bug entry, but I'll simply file a bug "it doesnt work".

Yeah, I'll keep that in mind, thanks.

(PS: If you don't understand irony: pissing me off by telling me to make easy cases, when I came to the forum only to make the case easier before filing it is quite illogical and offending)

You don't need to take offense and lash out. Forum topics spiral out when discussing, oh, just about anything. Thus bug reports are not meant for the forums, they go in Trac, and discussions about it in the Trac comments. Thus we directed you to the recommended way of doing it. You stated yourself that you didn't want to wade through the 200 odd results that came back, thus my comment.

Now for another: chill, I meant no offense