Yahoo Changes Protocol, Blocks Third Party Clients

NaDrew writes "ZDNet reports that Yahoo is once again blocking connections from Trillian (the alternative multi-protocol client). Yahoo tried this a few times last year and it looks like they're trying again. Cerulean, maker of Trillian, employs some excellent protocol engineers, who I have no doubt will quickly figure out Yahoo's latest obfuscation and release a patch. A quick fix discovered late this evening: Change your Y!IM host from scs.msg.yahoo.com to scs.yahoo.com, port 5050, and it should work. This is on Trillian 0.74H, not Pro."

Comments

Re:The business case sadly makes sense

[TheRaven64]

So why do people still use proprietary IM systems? When was the last time you used a proprietary email protocol on a closed network? Does it make any more sense to do so IM?

Most of the people on my contact list use Jabber. A few use MSN and one uses ICQ. I regard these as legacy systems, and often don't bother upgrading the transports on my server unless there's a security hole discovered. If these providers block me from accessing their service, then these people will receive an email from me explaining how to contact me via Jabber, and apologising for the inconvenience.

If google made an IM client...

[yuGufoT]

If google made an IM client... It would read all your instant messages, and then hide some advertisements that are relavent to your personal conversations.