Russian Google Competitor Embraces Open Source Messaging

rm writes "Internet search and mail provider Yandex, which many view to be Google's main competitor in Russia, has recently added an instant messaging capability to its mail notifier application Ya.Online. As it turns out, the IM service is based on the open XMPP protocol, with connectivity to all other public Jabber servers available from day one. MacOS X and GNU/Linux versions of the app were also released (complete with sources under the GPL) and are determined to be based on the Psi IM client. Yandex looks to be a firm believer in open-source, also running a mirror site for FOSS and actively promoting its branded version of Firefox. Here's hoping that its affair with XMPP will help eliminate ICQ's enormous foothold in Russia."

Comments

Missing info

[Bogtha]

As it turns out, the IM service is based on the open XMPP protocol

The summary makes it sound like this is some major advantage over Google. GTalk is also based on XMPP.

But hey, Slashdot needs to pay the bills, and this makes a great Slashvertisment for Yandex.

Re:Missing info

[t0tAl_mElTd0wN]

I've worked with XMPP, and despite having it's own organization devoted to developing the standard, it suffers from a lot of issues regarding actual standardization. Most of these issues are in the form of deprecated extensions. I think that will be the biggest hurdle for XMPP - yay standardization and open source and all that, but when old clients do things in a deprecated way and new clients do things the right way and don't bother with the deprecated features (because they're deprecated) then you start having some issues. Just look at all the extensions and tell me that this is a viable protocol for interoperability: http://www.xmpp.org/extensions/

Re:Missing info

[Brian Gordon]

Well when we say "an XMPP account with someone somewhere" we mean an XMPP account with any federated XMPP server; any domain. Can you set up your own AIM server and add it to the network? Also, Jabber is extensible and has voice chat through Jingle, which is what gtalk uses.

Re:Missing info

[Bogtha]

Yeah because you can't talk with people using MSN, ICQ, so on so on as long as they have an MSN, ICQ-compatible client and an account for that ..

An account for that... on MSN. Accounts on those networks are tied to the operator of the network. XMPP is decentralised, like email, so ISPs can provide their own servers, or you can use your own server.

I'd like to try to convince people to use XMPP but as long as it don't support voice and webcam there is no reason to even try.

XMPP supports voice and video through the Jingle extension, which originally came from and is supported by GTalk, if I recall correctly.

Re:Hmmm

[Jerf]

Cultures vary surprisingly widely on what constitutes "good design". Many Asian cultures, for instance, all but require you to have a very busy page.

In a way, I'm surprised at how some of it turns out. If you came up to me and asked me which of the "East" or "West" would prefer Google to Yahoo, I'd have picked East to prefer the Google aesthetic and West to prefer the Yahoo approach, but I would be wrong. (Very, very broadly speaking. I am aware I am generalizing, this is a Slashdot comment, not a sociology PhD thesis. Please don't cite "a counterexample" at me and think it proves anything.)

Re:Gchat

[Tubal-Cain]

That's the beauty of it: GoogleTalk doesn't need to be open source. Because it uses an open protocol, we can make our own tools to communicate with it, rather being stuck with Google's.

Re:Hmmm

[sulfur]

Yandex has a light version of their website (even more minimalistic than Google), just like Yahoo. The reason why Yandex is still more popular than Google in Russia is because it handles language-specific morphological variations of words better.

True of all but the smallest open protocols

[BitZtream]

Thats not really fair.

Show me a public/open protocol used on the internet that has a peice of software that supports ALL of its features.

I don't suspect you'll even be able to find a FULLY compliant SMTP or HTTP client or server. Possibly something on the FTP client list.

HTTP is extensible, once you take that into account its practically impossible to have 100% interoperability. My web browser for instance could give a damn about the fact that IIS says its running ASP.NET crap.

Even my browser doesn't know what to do with the ASP.NET header, it still works. Actually, it does know what to do with it, which is nothing, but thats coincidence in this case. Some other web server could possibly send me a header that DOES require action of some sort, and my browser may not know what to do with it. But I'm not really worried about not viewing pages.

I've been using Openfire as an XMPP server for a few years, a good year within the current company I work for, I've yet to have a problem with connecting between clients for sending IMs, internal or external. I communicate with several people on googles service, and many scattered across the Internet with their own servers, god knows how many clients shared between Linux, OS X, Windows and even an OpenSolaris machine or two.

If you think the xmpp extensions are bad, you should take a look at specs like HTML and CSS. They are certainly 100% doable, but NO ONE does. You do what you need to do to work with most clients/targets the rest is gravy.