Forum Replies Created
-
AuthorPosts
-
coded
ParticipantOk, so you got rid of the banner by modifying it to an erroneous url. I understand why the openDNS page comes up now. That’s more or less what I needed to know. Thanks
October 8, 2006 at 2:50 pm in reply to: YTK Pro Now Available! *pre-release to release info tracking* #155852coded
ParticipantAdd wildcard ignores for usernames and chat room spam. I noticed bot names are progressively becoming harder to catch with wildcard ignores, because their usernames are starting to mimic legit usernames, and containing less patterns. However they still spam rooms with the same phrases, thus it could be easy to filter them with a spam wildcard, or something.
coded
ParticipantYeah I’ve noticed this for ages. If you go postal trying to join a room it does seem to lock you out, or something to that effect. I _think_ this is why Yahelite’s knock (which is like an automatic attempt to join a room when it is full) feature extends the time between each knock cycle incrementally.
coded
ParticipantI wish Yahoo published a changelog. I’d like to know what’s fixed or added in this and every other release.
coded
ParticipantIt works again. I assume it was a weird hiccup on their side.
coded
ParticipantI did use a packet sniffer actually. I also tested this on a clean install of Windows XP Pro, with a clean install of yahelite, yazak, oopschat, yaheh and ymessenger. Tested them all with a packet sniffer.
I had two chat room windows open. Window A, Window B. Window A sent text which the packet sniffer saw. Window B did not receive the text, and the packet sniffer confirmed nothing was coming inbound from Yahoo. The instances that text did come back from Yahoo the packet sniffer did show the data of course. I tried many permutations of chat clients and protocols sending and receiving text with the packet sniffer. :/
coded
ParticipantYeah.
It happens in every room, busy rooms, rooms with no activity, etc. I’ve troubleshooted all scenarios I can think of. I tested with old screen names, made new ones, no difference.
Maybe yahoo has my IP cached in the naughty list or something. So all that remains is changing my IP address. But I have some torrents in progress so that’ll have to wait.
I have nothing but the essentials running in the background. Nod32 A/V, Windows SP2 Firewall, keyboard driver, and some Creative X-Fi crap, oh and Miranda IM.
coded
ParticipantThe first message i sent in a chat room didnt go through. The second two did. The fourth didn’t go through.
The waiting 5-10 minutes thing isn’t a solution for me I guess.
coded
ParticipantWindows XP Professional x64
AMD64 3400+
1GB RAM- Yahoo Messenger 7.0.2.120 or YahElite or Yazak
- I always use the default black text.
- It only happens in chat rooms, not private messages.
- No significant installs before this problem occured.
- The messages when sent appear locally on my window but does not appear server side.
- The text “seems” to go through more often when using the CHAT2 server.
- I noticed when using Yazak, after text messages have been blocked and one does manage to go through, the message begins with an extended asci character that looks like a b.
- I “think” the problem started occuring while using Yahelite and going from one room to another fairly quickly, and using the /knock feature a lot. That’s just my suspicion.
- After I noticed my messages were not going through, I used another YahElite window to log into the same rooms to see which messages were going through and which werent. I’m not sure if Yahoo likes that, and would add to the problem.
I read a bit about this problem on this forum after I posted my original message. It was mentioned that the problem is server side and a solution could be to log out of yahoo completely for 5-10 minutes. I usually leave messenger on idling but I’ve had it off for about 24 hours now. I’m going to go into a chat room and see if the problem persists. If so I’ll let you guys know.
-
AuthorPosts