Forum Replies Created
-
Posts
-
There should be plenty of deny-a-buddy programs out there that still work. As long as YMSGv12 protocol is still around you’ll be able to do it (like Ven0m said). However, I have a feeling that Yahoo! will eliminate v12 sometime in early to mid 2009 since there’s absolutely no point in keeping it around as nobody uses 6.0 anymore and the support is now gone for it.
The good news is I stumbled upon a way to deny-a-buddy users without needing to rely on YMSG version 12 at all. As a matter of fact at the moment Ven0m is the only other individual that knows how to do it the ‘undisclosed way’. When it’s time to release it I’ll spill the info and it’ll be added to YTK Pro simultaneously. I’m afraid that if I give any of the details now it’ll be abused and Yahoo! will patch it. This is a different method for denying people and due to the nature of how it works it could be used in a bad way. 😉
Quote:It is ID related. Any of my other ID’s work perfectly with all Yahoo chat clients.What you’re experiencing is definitely ID-related. How would I know? I’ve been around Yahoo! Chat for a long time (many painful years of pleasure, it’s a love-hate relationship) and I started experiencing an ID-related problem as well. One of my accounts (including all aliases on it too) lacks the ability to receive “offline” messages, add buddy requests and so on. LoL. I found this to be quite strange when I first noticed that this was the case way back then. You’re not alone here.Quote:It seems that it only happens for 12hrs or so at a time.Even stranger. Can’t elaborate for you on this one.
Quote:I’ve gotten new WAN IP addresses on my ADSL with no luckIt’s not an IP-related issue at all, it’s a Yahoo! Chat server ID problem exclusively.
Quote:My text does show on my screen but not on anyone else’s.Your text shows up on your chat screen because Messenger is handing your message (what’s called a “string” of data) directly to the MSHTML control which in turn handles the rendering/display of your text inside the chat window in Messenger. This is a local operation so no IP packets (Yahoo! ‘YMSG’ chat room message packets) are sent out & forwarded to the room’s users by the chat servers (the Yahoo! Chat server problem isn’t an issue affecting you when you do this).
Quote:Is there a exploit/script/hack that someone can or could use to text ban my ID in Yahoo chat? And if so How do I stop it or how is it done?Definitely not an exploit at all. If it was an exploit it wouldn’t just be affecting you especially with this particular (and only) ID in question. Others would be getting hit with this in the masses. I can be certain that it’s not an exploit or a “hack” being used on you because I make a living professionally developing various software applications specifically around Yahoo! Chat/Yahoo! Messenger. Believe me if this was something new (or even old) I would’ve either discovered it on my own (I do my own independent hunting) or I would’ve at least heard mention of it.
As to “how” to pull something like this off – along the lines of text banning and completely silencing your messages to the room… well, I can think of only a single way and it definitely wouldn’t work (no need to try it). In theory, if the Yahoo! Chat servers didn’t validate and respect your IP to ID mapping (among other things), it could be done by flooding the chat room with messages spoofed from your ID. The chat server would receive the messages from the ‘attacker’ masquerading as your identity and would text ban your ID from sending to the room. While you’re banned (which is temporary and doesn’t last all too long depending…) none of the chatters in the room will see a single one of your chat messages.
Quote:Our engineers are already working on
this issue and plan to add the fix to the next set of enhancements for
Yahoo! Messenger.LoL. You’re being “played” here. It’s not being “worked on” because they’re totally unaware of how to resolve your issue (maybe ~3% or so of all Yahoo! Chatters experience serious ID-related quirks like yours and mine). They’re only telling you what you’d want to hear to pacify you.
Here’s a proposed workaround for you IF the ID that you are having problems with is an alias on your main account (chances are it’s not but this might be worth mentioning). Try deleting the ID entirely and then recreating it on a totally separate main Yahoo! account… kind of like transplanting an organ into someone elses body.
I don’t see any other logical ways of even attempting to resolve this freakish dilemma. Good luck to you.
YTK Lite was updated to support this new beta build of Yahoo! Messenger. You can get the new YTK Lite beta build 410 here -> YTK Lite : The Anti-Boot Protection and Functional Enhancements for Yahoo Messenger.
YTK Lite has been released! You can get it for free here -> YTK Lite : The Anti-Boot Protection and Functional Enhancements for Yahoo Messenger.
:woot:
Besides having many features that Y!TunnelPro/Basic doesn’t have (that actually work) YTK Lite also has 2 clear advantages over Y!Tunnel.
1) Official Windows Vista Support
2) Official Support for Messenger 9.0
😎
Y!TunnelBasic is a nice free product but YTK Lite will clearly give you more functionality for free.
What Lite will be is a lightly slimmed down version of YTK Pro. It’s goal is to compete with Y!TunnelBasic and Y!TunnelPro because it’s free with, as you guys noticed, a lot of *working* features. There’s no catch here… this is something that isn’t worth missing out on. When it’s made available (hopefully sometime early this week) it will be available for download at http://www.YTKPro.com.
I’ll post back here when it’s available! 😀
Amerikaner08, I’ve seen this happen before. Yahoo! Messenger hangs when making the HTTP connection to the room list (insider) server. Unfortunately there’s nothing that can be done about it but to wait it out.
The last version of Yahoo! Messenger that doesn’t have the ignore bug is version 7.02 which can be found here -> Download Yahoo! Messenger 7.0.2.120 – FileHippo.com
This is true folks. By using one of these servers you will be immune to server-side disconnects and boot flooding. You won’t get knocked off the chat network on these servers even if you’re on a dial-up connection.
Venom is correct in saying what he did because of how the new Add Buddy system works. Last year I posted on the Y!TunnelPro forum a “workaround” that allowed you to DAB from YMSG13 and higher. This was a type 0x86 deny packet (the old YMSGv12 and below packet) that used the header version 0x0C since at the time you could send packets with inconsistent/varying header versions to the server. The chat server thought that the DAB packet was generated from a YMSGv12 login (when it wasn’t) and granted DAB ability. My workaround was used in Y!TunnelPro AND in YTK Pro for many months before Yahoo! patched it (due to recent server changes).
I’m sorry but you can’t DAB with the 0xD6 packet type (which YMSGv13-16 uses) at all. I’ve not only tried it I know WHY you can’t. You can only deny ONCE with it and after that you can no longer use it until you’ve been added to the person’s list again, then the process continues.
When a user adds you with the new Add Buddy system you have the choice of allowing or denying the request. If you accept the request for someone to add you (keeping in mind we’re using the 0xD6 Add Buddy Rejection packet) then you will NOT be able to later on “deny” this user. It doesn’t work that way. This is why YTK Pro (my program) allows for “Protocol Reversion” so that you can use YMSGv12 to DAB users. YMSGv10-12 don’t use a tracking system and don’t rely on accepts and denies for functionality. Once a user is added they’re added… it’s then up to the end-user that was added to “appeal” that add buddy operation if they desire.
Why doesn’t the 0xD6 Add Buddy packet work to DAB users whenever you like?
It’s simple, something I figured out myself early last year when this stuff actually “mattered” to me. The new Add Buddy system keeps “state tables” of when you Accept an Add Buddy Request. This “state” is referred to each time you go to deny/reject users. If you’re already in the table as having Accepted the add buddy request then Yahoo! will not let you deny the user corresponding to the Accepted request. If you aren’t in the state table (the servers keep this state) then Yahoo! considers it a new Add Buddy request and gives you the opportunity to Accept or Deny the user(s) that attempted to add you.
YMSGv10-12 don’t have state with their old Add Buddy system and therefore you can deny anybody you wish at any time you want.
This isn’t just my “opinion” this is fact. The whole purpose of DAB is to be able to Deny users WHENEVER you like and you can’t do that with 0xD6, not after you’ve Accepted an Add Buddy Request from another user.
Ghost wrote:
Quote:The voice lagger problem has been around for as long as I can remember. It seems like Yahoo could find some kind of solution or workaround for that problem. Voice lagging/freezing is a problem that has existed with YM for YEARS!The problem is relatively easy to fix but Yahoo! would rather not implement a fix because of extra overhead on their servers (for validating the RTP voice packets). If they were smart they’d fix it at the client-level (inside of yacscom.dll) and validate RTP sequence numbers and timestamps in the RTP packet headers. These two header fields are what’s causing voice lags to “freeze” you (which in technical terms is known as resource exhaustion).
We, at YTK Pro : #1 Yahoo! Messenger Integrated Companion, were the first to correct this issue with 100% success (in VC Sync) and without having to drop/block a single voice packet. Surely if we can do it then they can too. Yahoo!’s got many times more resources than we’ve got since it’s just us 2 developers involved with YTK Pro and VC Sync.
Quote:has adam figured out how to block the buddy ad in 9.0 michael?All ads are destroyed (optionally) in our new beta build of YTK Pro v1.5 (build 392). Yahoo! Messenger version 9.0 beta build 797 is 100% officially supported now as well as Windows Vista 32-bit Edition operating systems. We more or less have been working our behinds off to get all of this stuff done ASAP.
This service is accurate BUT there’s always a way to get around it.
Quote:FAQMay it happens that someone makes him/herself invisible and Xeeber is not able to find them out?
Never. No one can hide him/herself from Xeeber. The method of Xeeber is reliable and it’s successful on all versions of Yahoo Messenger.There’s ways to “hide” from this type of detection as accurate as it is. If the Yahoo! ID being scanned for on Yahoo! Messenger is an Alias (sub-account profile name) you can turn it off (set it to inactive status) and Xeeber’s scanning will FAIL.
Another thing that can be pointed out is that more and more people are using Yahoo!’s new and improved Web Messenger Yahoo! Messenger for the Web. If you sign in as invisible in Yahoo!’s Web Messenger then once again Xeeber will FAIL at detecting that the user is invisible.
YTK Pro Beta Build 340 adds in a Captcha image viewer in it’s own separate window over our previous beta build 338. Chat Room Auto-Voicing (which causes the freezing when dealing with the Captchas) is OFF by default when the “Auto-Launch Captcha URL in Chat” option is ON. The number of Captcha “tries” remaining is printed to the external event logger.
Note: Please update your forum signatures if you intend on installing and running this new build. Any previous installation of YTK Pro should be removed FIRST prior to installing the new build.
YTK Pro Builds below 340 are NO LONGER SUPPORTED!-Torseq Technologies
Yet another build is coming either today or tomorrow. It will fix some more bugs (small ones), add another feature or two and will work with some more incompatibilities since the server changes were made (Captcha verification).
😎
