After we learned today another consequence of generating the correct sequence, it became clear that AOL had known this feature for quite some time (approximately since April 2008), and so far probably used it only for petty pranks with alternatives. And we could not understand what is the reason, naive.
The essence of the existing "pranks" was that no alternative client could move a contact from one server group to another, only using tricks like "remove contact from the server - add it to another group", while authorization could be lost and problems would arise . And today, when the changes were rolled back, we noticed that the patched versions of the protocol version patched for the new changes successfully cope with this operation, and the old ones still get an error
That is, the company began its quiet struggle for quite some time, and in principle could continue to disable its chips for us. And on January 21, apparently it became Day X - when the behavior of some of our companies was finally fed up. The corporation showed all its strength - it took about 12 hours to fully understand the problem. During these 12 hours there was a panic, confusion, loss of clients from those whose business is somehow connected with the use of this network and unofficial clients. The lack of any comments from the icq side caused informational hunger - as it turned out, my article became the main source of information. A day later, when everyone had already adapted to the changes, AOL company returned everything to its place. Play with a kitten. Perhaps in the near future we are waiting for new sessions of shock therapy. Well, time will tell. ')
I advise you to get ready for this and go to Jabber =)