Confessions of a Social Tools Architect
24 Jun
For what must be years now, I have avidly used and recommended Trillian as my IM client of choice. For anyone that does not know, Trillian is a meta-chat client that provided many interesting and useful functions. For the most part, users were attracted since it allows a single client that connects to all of the major chat systems. Other key features included secure communications between Trillian users and automatic chat logging.
Unfortunately, the infighting that exists between the major IM clients has made remaining committed to Trillian tedious at times. Originally, there were many instances where AIM, MSN, and Yahoo! would intentionally alter their connection protocols to block Trillian (and sometimes other meta-chat tools).
Quite some time ago, MSN officially shut the door and forced most users to return to the Microsoft client to connect to their Messenger accounts. The latest blow came today as Yahoo! drops the hammer and shut out Trillian once again.
Beginning at about 6 p.m. Wednesday, Yahoo changed its instant messaging language to prevent third-party services, such as Trillian, from accessing its service. Like previous statements, the company said the block is meant as a pre-emptive measure against spammers from its Yahoo Messenger service.
“Spammers are being aided by entities that are abusing our systems, where they effortlessly gain knowledge of pathways and back-alley access to send spam,” Yahoo spokeswoman Mary Osako said.
Of course, there are some issues that really are important to note here:
Money Maintains Separation - SPAM IM (SPIM), as they call it, is a very real force and will only seek opportunities to expand its reach in the long-term, that’s not to be disputed. However, the underbelly of Yahoo’s explanation leaves room for one other option - money. Yahoo’s Messenger not only requires a login process that yields advertising dollars, it also yields ad revenue from other ads placed through the IM process. Subverting the IM system tapers their revenue stream.
Though Microsoft did not give in directly because of ads, they did cite a license was going to have to be paid before Trillian could connect again. At least that sounds like an honest answer.
Jabber Growth Stalled? - I’m not a diehard user of Jabber, though I do believe in the both the promise and technology behind it. The major IM players are so well entrenched that it’s very difficult to ease people off of them. IM Gateways provided a means for bridging those users and getting to work with a Jabber-based solution without sacrificing their familiar networks. If the gateways disappear, will Jabber be able to grow to the size of even the smallest major player?
I should note that one interesting way to get some numbers, would be to auto-register/enable existing social networks with Jabber servers/systems (like Gush). Imagine getting 7 million Friendster users all tied into a Jabber network - that’s some size.
ZeroConf to Rise? - Systems like Rendezvous, Pocketster (formerly Pocket Rendezvous), and the like (thanks Pete) provide what are known as ZeroConf (Zero Configuration) networking. Using this, for example, Apple users are able to chat with each other directly, not requiring centralized networks. Mobile Social Networking Apps are starting to evolve that utilize networks of this nature to enable chat. It won’t assist with the relationships that span georgaphy, but it may become a viable substitute in some circumstances.
10 Responses for "IM Networks Uphold Isolation: Death to Trillian"
Hey Greg,
Just for the record, the domain is under .cc, not com. Talk about a suprise when I landed in a whirl of icons ;)
Cheers,
Robby
Thanks Robby. I’ve updated it.
Unfortunately, Yahoo! says they are going to continue to block so if it works now it most likely is pretty short lived.
“The underbelly of Yahoo’s explanation leaves room for one other option - money.”
Have you seen anything to falsify their original assertion? (iow, the possibility of another motive does not imply the inevitability of another motive.)
There’s a tangential angle for discussion too, in the way that various format/capability paths can lead to different interoperability levels. For comparison, the Macromedia Flash Player *needs* to play existing websites with fidelity, so it’s hard to change functionality out from underneath it… existing SWFs are grandfathered-in. But something which starts as a given moment-to-moment capability for a given audience may not have the same requirements for interoperability and backwards-compatibility. I’m not sure where I’m going with this latter thought, however…. ;-)
tx,
jd
John,
I didn’t mean to indicate that SPIM isn’t/won’t be a valid issue they are combatting. Of course, there’s a certain sanctity to monopoly.
If SPIM were the issue, why not do things like:
1) Never allow messages except from those on your contact list
2) Enable this function by default
If I understand what you are getting at, you mean to say that by closing the doors they open the path to a richer experience, potentially. Though I think that’s totally true, there’s lots of ways to make that still available.
1) Jabber supports quite a few powerful extensions that each IM provider has chosen to implement in a different manner as opposed to a potentially standardized approach
2) Server-side translation of features that downgrade features on the fly. Realistically, this is already happening on some levels.
Thanks for the insights,
Greg
Not accepting messages from strangers seems a good idea. I haven’t researched whether there are counter-costs, however, so I’d hesitate to ascribe pecuniary motives to others based on this suggestion alone, yes…?
Hmm. I’d have to say that looking at Yahoo’s revenue stream, which is significantly based on advertising is an undeniable factor in any decision they make.
As I’ve noted though, I am sure they are genuinely interested in blocking SPIM, of course they didn’t feel inclined in any way to even indicate that SPIM was on the rise inside their network as a result of the 3rd parties.
I’m gonna stick to my gut here though.. money a la securing their ad network, was a factor, even if not the main one.
When MS walked the same line, they came up with money first and foremost. Would you venture those businesses are quite so different?
I dunno. I just get that feeling.
“Unfortunately, Yahoo! says they are going to continue to block”
The only way to isolate trillian (or any other solution out there) would be to say, “if you connect to us, we’ll sue”… other than that, it becomes the coders over at yahoo against the hackers at the trilian (and whoever else’s) camp… i wonder how that would be worded to make sense though… suddenly IM servers are islands/untouchables? take em off the internet then
jd, the more i think about it, the more it seems like anything aside money that is cited as the reason for the block is just face-dressing…
… i mean, have you really read this:
“Spammers are being aided by entities that are abusing our systems, where they effortlessly gain knowledge of pathways and back-alley access to send spam,”
ok… assuming that is true… and u r saying they are using “pathways” and “back-alley access”… blocking Trillian (or anyone else who depends on your network) isnt’ the solution… providing a standard API/protocol to be used by any and all and securing those back-alleys is the solution… herein lies the problem… for as long as you try to remain closed, and disallow other solutions like trillian (which i use btw, together with opensource solutions like miranda and the like) from connecting, you create a veritable reason for them to find those back-alleys… the truth of (whether or not, there’s) SPIM (which is a new word to me) coming out of those newly created connections lies with yahoo… but seriously… yahoo shouldn’t insult anyone’s intelligence
nursing education http://nursing-education.incsx.com/
http://www.gratuitbaise.com/lesbienne/qrestin/pantyhose/arrest/pics.html botherfrigidstraddle
PING:
TITLE: blog and ping
BLOG NAME: blog and ping
this isa niceblog …
Leave a reply