This is for Escargot, specifically. Also, I wanted to start from the oldest Yahoo client that works on modern operating systems. So why not Yahoo! Messenger 5.5, which uses YMSG10?
P.S.: With Escargot’s YMSG support, don’t expect random server shutdowns like a certain Wildman’s server
The last time your Yahoo! server had fully shut down, I had assumed the server itself had malfunctioned. I haven’t really touched server stuff up until last year, so I had thought that server software wouldn’t malfunction in terms of stability. Guess I was wrong.
Well, shoot. I’ve hit a snag with contact management. Specifically, when sending contact requests. I tried every twist and turn, and nothing seems to work. I am working with YMSG9/10, so I guess things are different in terms of key-value fields. Please bare with me here.
I congratulate our fellow Messenger fanatics on the progress of their project. It’s possible I may be able to lend some assistance. I’m working on a similar project targeting Messenger 5.6, 6.0, 8.1, and 11.0 with connectivity to XMPP, IMPP, and a custom back end and other components to support voice and webcam support. I do not recommend targeting 7.x, 9.x, or 10.x as there is very little value in supporting that many versions of the protocol and that many work arounds.
There are a lot of XML files that are downloaded post-login which contain configuration information for audibles, emoticons, websites, etc. These files are signed and cannot be modified without making Messenger tilt on itself or if you’re lucky if just ignores it. There are other services provided by websites such as my.yahoo.cominsider.msg.yahoo.com, etc. that will need to be provided as many features will not function without them. This includes the chat category list and topic/room list. If these files are not present the features either work incorrectly (i.e. crash, hang, do nothing) or can be disabled. In other cases you can end up with features that shouldn’t be active at all (voice chat or create chat room in Messenger 8.1.
Nice job on your end! You’ve made much more progress than I’ve had, but that’s only because I had trouble with contact manangement on YMSG10 (specifically, directing contact requests).
Sucks that the config files server-side were signed, unless the signatures are hard-coded into the executables.
If you don’t mind, could you share the details on the “contact request” packet structure, a.k.a. the packet that displays the contact request dialog? Via reply or PM would be fine.
A little bit of critique on your videos:
They’re good. Very insightful, but I’d HIGHLY recommend getting OBS to remove any pesky watermarks (unless you’re not interested lol). It’s mainly a streaming program, but with the right configuration, it will probably become your next best screen recorder.
Thanks. I’m not concerned with the file signing, I’m just patching Messenger to ignore it. Once I get home I’ll drop the specs out. I still have one issue to resolve with it but I should have that taken care of tonight. It just requires some additional state management in the mock session.
If you’re that interested as to why I’m concerned about the XML config files being signed, I do plan to implement Audibles once I get to Yahoo! Messenger 6.0.