QIP Kill cannot be pardoned.

    Probably at least once in your life you had to deal with the problem of encodings when communicating in ICQ, messages come "crackers" to one or both opponents. You have to write transliteration or switch to another client / protocol. For me personally, ICQ communication is part of the work and IM client is the same tool as IDE development. Probably I'm not the only one who got such problems.


    Well, actually to the point. I myself have been using Trillian Pro 2.013 for about five years, the only patch was released 2 years ago due to regular surprises from AOL, except for this the program did not change at all. There are no problems with users of official clients, Pidgin and Miranda, messages in both directions come as they should. As for the QIP and QIP Infium software updates, I usually learn one of the first, the normal work with encodings may break or it will be repaired with each next update.

    Why do I sin on QIP? Just an analysis of the problem indicates exactly this, we will examine the symptoms:
    1. my client has not been updated for the last 5 years, according to the data taken from other clients, it uses version 8 of the protocol
    2. Work with other clients is going fine, although Miranda had similar problems a few years ago, but they apparently resolved
    3. Offline messages from QIP users come in normal encoding, apparently not without the help of the AOL servers on which they are stored
    4. If you drive the crackers away through Lebedev's decoder www.artlebedev.ru/tools/decoder , then it gives out a completely readable text making the transformation WIN1252 -> UTF-8
    5. and the most important. Over the past years, communication with QIP users has been a variant of Russian roulette, after the next update of the program, messages suddenly start coming in as crackers, after another update - kosher cyrillic.

    Given the popularity and numerous advantages of QIP, it’s silly to lure users to other clients, the client is good. For its part, I am also not ready to change my client, which has been serving faithfully for so many years without any updates (which QIP just cannot boast of). Once I wrote a letter to the QIP developers with a description of the problem and a request to enter the “encoding” setting, as it is in the same Pidgin, but I did not receive a response.

    The request is not to arrange a holivar regarding clients, the problem is partially in the protocol (I do not offer Jabber, and so I use it), it is known that AOL likes to create problems, and Trillian uses the old version. But there are no problems with other clients, but QIP ... well, in general, you understand.

    psfrom the comments it turned out that the problem also occurs with other clients when communicating with qip, regardless of the platform. It seems that the developers of the quip are jealous of supporting the OSCAR protocol, supporting only the latest version, because of which the program stops working with every update by AOL and does not have backward compatibility with clients using a different version.

    Also popular now: