Google, Jabber, and Jingle
An anonymous reader writes "Jabber has published the experimental draft Jingle specs, which extend XMPP for use in voice over IP (VoIP), video, and other peer-to-peer multimedia sessions.
Google released an open-source library called 'Libjingle' on SourceForge. Libjingle is a set of components provided by Google that let your programs interoperate with Google Talk's peer-to-peer and voice calling capabilities. The package includes source code for Google's implementation of Jingle and Jingle-Audio."
I have the only w33n0r I think I need to see when logging on.
Now if google would just implement server-to-server jabber connections, this might be useful!
Let's hope someone can now develop a Gtalk pocketpc application with voice. While they are at it: add conference mode to Gtalk; in business environments it's very handy.
All these instant messagers and voice applications could somehow communicate so would not need to have so many on my computer. Even if the communication was on lowest common denominator, could use the ones I like and atleast communicate somehow with people using others.. oh well.. not likely to happen soon I guess.
Using transcoded XML for binary audio support... I wonder if some bandwidth is wasted just because of the format (XML can't contain random binary data, so there's bit loss). Anyone checked deeper?
...their system where the advertisers call you? It's safe to assume they'll be adopting the platform and munging it with some sort of phone connection to achieve this. This could be just the step they're looking for to lower costs and make more profit. And on top of that, how many other messengers have an open voice protocol? How long before we see extensions etc? And how long before some wisespark tries that Skypecasting thing with it? Since jabber can technically support any mime type, all we would need is for someone to plug theora into it and instantly it can be done.
~HTP~ Hug that tux
...where 2 comments saying exactly the same thing have +5 and -1 respectively.
I don't buy this. Spam in Jabber is much more difficult to achieve (some people say it's impossible but they're probably wrong) and Jabber without server to server is not fully Jabber.
There was talk of google potentially buying AOL.. If this happened, they could migrate the existing AIM/ICQ networks over to a jabber based protocol, while maintaining the existing protocol for compatibility..
They could retain gtalk as it is too, and allow server to server jabber communication between both their servers and external jabber services..
AIM already has a large userbase, and with such ease of communication between services it may be large enough to convince yahoo/msn to co-operate too.
http://spamdecoy.net - free throwaway anonymous email - avoid spam!
IM clients are the obviousplace to strapon VOIP communication. The jabber system would be a perfect VOIP framework. Your "number" will simply be your JabberID. Which is similar to an email address, so it's easy to remember.
You'll simply dial something like "malda@slashdot.org" to complain to Taco about the preponderance of dupes, and Taco can simply add your address "slashbot@cheapisp.com" to his ignore list.
If telemarketers become a problem, some kind of del.ico.us system might enable VOIP users to share a list of banned domains or addresses. Potential for abuse etc, etc.
Key point here is that a system based on "email" like addresses would be batter and easier to remember than the current telecoms number based system.
May the Maths Be with you!
The main Gaim developer was hired by Google and given the low-down on the Jingle project some time ago, and it'll be added to the Gaim-vv system that's apparently coming in Gaim 2.0.
I thought the intention was to use SIP as the underlaying protocol.
Google should implement server-to-server but drop any incoming messages from users that are not on the recieving user's roster. This way people can still talk to their friends on other Jabber servers but unsolicited messages won't be a problem since they'll be dropped outright.
This may cause difficulties for agents that aren't people, such as services and bots, but at least it would open things up a little for person-to-person communication.