This is an interesting tid bit about the Yahoo! chat room problems. http://www.winbeta.org/forums/index.php?showtopic=8809 To be honest I am kinda scared. When a company has set a hard deadline to resolve “technical issues” I always get the feeling that something else is going to change. Maybe this is another protocol change or something specific to chat. On a personal note, I have noticed the problem getting slightly better over the past few days.
Thank you for writing to Yahoo! Messenger.
We understand that you are unable to enter chat rooms through
Yahoo! Messenger. We do realize the inconvenience and
empathize for your present situation.
“We are currently aware users may experience slow load times
when trying to access or communicate in Yahoo! Chat. These
issues may be intermittent, allowing access to Yahoo! Chat on
some occasions, and on others return the message “Signing
into Chat took longer than expected” or “request refused.”
Our engineering teams are currently investigating an issue
with the Yahoo! Chat servers and working on a resolution.
Unfortunately, we do not expect that this issue will be
resolved until 14 May 2007. We are aware Yahoo! Chat is
important to you, and we want to make sure this issue is
resolved correctly.
We apologize for any inconveniences this may have caused and
appreciate your patience and understanding while we work to
resolve this issue.
Thank you again for contacting Yahoo! Messenger.”
I added a section for HTTP Helper on the code page. I have had several people ask about it when they wanted to compile YCC Bot Maker. Just as a reminder the binary is included in the executable package.
I am still feverishly working on YCC Trainer. I was hoping to release the next version tonight but I forgot the updated code at work. At this point I think I can consider the login stable with all special cases handled. Messaging also works now (barely) but is far from being complete. Hopefully I will not be forgetful and remember the code tomorrow.
It looks like one more person has been added to the forum ban list.
Rollercoaster
58.65.239.18
Congratulations to him (or her) for spreading SPAM.
I hope everyone had a good weekend. I personally just got back from visiting family which was a refreshing break.
It’s been a few weeks since I last updated the website but I have actually put in more work than usual. I have been hard at work on the next version of YCC Trainer. My current goal is to add all the functionality of the previous version (Yahoo! Login Scokets) and fix all the known bugs. As it sits right now, I am about 75% done. I will release the next version once I get everything but the messaging finished (which is about 85% of the original minus the bug fixes). Below is a few of the things that I have been working on.
• There was a bug in the AuthResp that did not allow a full logon. The bottom line is this was due to a copy/paste error. This and also a bug in the DLL signature have been fixed.
• YCC Trainer uses the latest YMSG protocol, 15. The previous protocol was 13. There are no major functionality changes but many of the field identifiers have changed.
• Packet handling has been increased. There are basically four cases when receiving a YMSG packet. One YMSG packet per TCP packet. Multiple YMSG packets per TCP packet, a YMSG packet that spans multiple TCP packets, and a combination of a spanning packet and multiple packet. The original version could only handle the first case of one YMSG per TCP packet. I can now handle the first two with framework for all of the cases. I still have some debugging to do but this should be fully implemented within a day or so.
• There is now a new program structure which incorporates the concept of a YMSG packet. A packet is defined as a uPacket in the modUser class. When dealing with socket communications a programmer has to interact with a byte array. Now all the underlying communications will be broken into individual packets which makes higher level programming much easier.
• The buddy list is now parsed properly. This is mostly due to the fact that spanning packets are now processed.
• You can now sign in as invisible.
• Separate ignore list.
• Improved debug window.
I also have several things that I intend to implement that will not be part of the next release.
• Ability to send instant messages and typing notifications. This includes all of the window handling functions.
• Improved debug routines.
• Booter code?
• The ability to get the IP of someone in your buddy list. I know this is possible if direct P2P communication is set up. I need to find the format and limitations. I have also read on other sites that when someone is in your list, a P2P packet is the default. The GAIM (or whatever they are called now) code seems to confirm this.
• Custom packet generator.
• Protocol fuzzer. This one is a long way down the road but still a goal.
• Make a new tutorial based on protocol version 15.
In order to run my main account and try out the new YCC Messenger account I tried a Messenger polygamy program called Y!Messenger 8.0 Multi Patch. I have added the link to the links page. It works just as advertised but it has magnified a problem that I have been having for quite some time which is Messenger decides to reconnect every 5 minutes or so. This is not a major problem but certainly an irritation, especially when I am running my cam.
I don’t know how this will work but I have assigned a special Messenger account for Yahoo! Coder’s Cookbook. I should have an icon on the main page soon, otherwise the username is tansqrxatycc.
I updated the links with the Yahoo! Messenger Blog (http://blog.messenger.yahoo.com/), Y!Amp (http://elitenick.com/?page=yamp), BigBlueBall (http://www.bigblueball.com/), and Dark Yahoo! (http://darkyahoo.com/index.php). I also didn’t realize that I did not have product pages for YCC Trainer or Yahoo! Trainer, the pages are now in the code section.
I am starting to get a little scared. I have posted some new content but I am not getting any feedback at all. It has been almost three weeks since anyone posted in the forums (besides myself). At least make a post to let me know that someone is out there. From the website statistics I know you are looking.
I am also thinking about posting my Yahoo! ID on the site so you can talk to me. This will not be my main account but I am planning to get either YCC Trainer working well enough or use one of the Messenger polygamy programs out there.
I am a developer so I am thankful when someone points out a flaw in one of my programs. Many times a user will simply quit using your program because of the flaw and the developer is none the wiser. I figured I would be nice and tell Yahoo! about the problem with DEP. I was very descriptive about the problem. I explained that DEP was triggering the failure and that I suspected the problem was with allocating the memory pages as data and not setting the executable bit. I then explained how I solved the problem and I was just letting them know that there was a problem. Below is the response that I received.
Thank you for writing to Yahoo! Messenger.
We understand that you are unable to install Yahoo! Messenger 8.1. We
are sorry for the inconvenience this has caused to you and we empathize
with your present situation.
Do you happen to have any ad removal, firewall or virus protection
programs installed on your system? These can act as roadblocks on the
way to a fabulous Messenger experience.
If you have any applications of this type installed, it’s time to bid
them adieu. Please disable them on your computer and then reinstall
Yahoo! Messenger.
It appears that another program that is running on your computer is
getting in the way of the Yahoo! Messenger installation. To fix this
problem, you’ll need to turn off all of the other programs and then try
installing the Yahoo! Messenger again. You won’t lose your friend list,
as that is stored on our servers.
Not exectally what I was hoping for but at least I tried.