Login Register
Previously Deported Illegal Arrested After Brutal Stabbing On Charlotte, NC Train --- --- Demonic! Country Artist Zac Brown Displays Satanic Imagery During Song Performance At “The Sphere” Las Vegas --- --- White House Doubles Down After Pop Singer Sabrina Carpenter Whined About Her Song Being Used In Pro-ICE Video --- --- Texas Congressional Candidate Valentina Gomez Humiliates Piers Morgan on His Own Show --- --- Putin and Modi Forge Eurasian Front with Launch of RT India --- --- ANOTHER Muslim Terror Attack? 10 Dead After Individual Rams Car Into French Christmas Market --- --- FBI Raids Home of Top Obama-era DEA Official, Accuses Him of Laundering Millions for Cartel --- --- Illegals To Be Hit with $5,000 Apprehension Fee --- --- Pro-Trump Podcast Host Tim Pool Says Vehicle Approached His Property, Opened Fire --- --- DeSantis Calls for AI “Bill of Rights” To Protect Citizens --- ---



[Reply]
Forum Index > AIM/ICQ Discussion
* excellent work *
Posted on: 12-30 11:02 pm
aolproggies

Did you find the book on the protocol or something? really good job !! be sure to write up a post when your done.
Posted on: 01-01 5:09 pm
tonyshowoff

There's no real book anymore, but there are people in the know who have contributed some information, but most of the work iWarg (the creator of Phoenix) did himself or gained from other projects.

The fact is that there were changes made over the years which were not reverse compatible, though largely with non-primary functionality like weather notifications, but also with buddy rights information and so on where the information was all position/length based, and that changed so much that in some cases it's vastly different from version to version. The underlying assumption was always people would be using the latest AIM client, but so long as older ones "just mostly worked" it was fine. This is hell on a project like Phoenix.

Ironically there was a way to deal with this (tool IDs, SNAC versioning was better, etc) in versions of AIM 3 or so and beyond, so the biggest messes are in the oldest versions. Third parties who documented and/or implemented the protocol did so with different versions so they all contradict each other or make different assumptions which are themselves not compatible.
< - 1 - >

[Reply]