81–90 of 143 posts
Yep, I already warned about this a few days ago. I would like to encourage everyone to avoid using this walled garden service and make sure you tell both your friends and Google why. Say NO to proprietary network protocols!
So now Facebook chat, which partially supports XMPP, is the most open of the widely used IM networks. There's a thing.
Earlier quoted context omitted.
Why is it not utilized more widely then? foregoing for a minute that everyone is cultivating their own gardens - what are the weaknesses of XMPP that would make it so easily avoidable for most of these apps?
It's definitely not the lack of features, since XMPP is extendable. I've heard that the protocol is quite chatty and would cause power drain on phones. That could probably be solved with a binary serialization alternative to XML, though.
Earlier quoted context omitted.
Personally I'd love to see a community driven extension to XMPP, with its corresponding RFC, which would allow feature parity with Google's proprietary crap while keeping interoperability and federation, so people could give Google the finger on this one.
I've long dreamed of a resurgence in the open source community, attacking big media much as the community attacked Microsoft in the late 1990s. It's depressing that the PR machine has so thoroughly succeeded that most of those who still call themselves "geeks" now consider building throwaway hacks on big media services cooler and more meaningful than coordinated efforts to replace the services themselves (in the name…
Larry Page seemed very upset [1] that Microsoft is basically leeching off their Gtalk contacts into Outlook, without returning the favor (with Skype I assume), and he said he'd prefer if things weren't like this and everyone was more open. He didn't continue that idea, but I think he would've continued it with "...but since nobody wants to do that, then we won't do it anymore either". So they are probably responding…
As a user, I am upset that it is getting harder to communicate with people. Everyone has their own non-interoperable (but cross platform!) protocols/networks/gardens now. * blackberry bbm * apple imessage * google hangouts * skype * whatsapp, etc. As a user, am I supposed to have an account with one of each of these things? Have nine different apps open all the time? This is as bad as icq/messenger/aim/etc was back i…
Earlier quoted context omitted.
As a user, I am upset that it is getting harder to communicate with people. Everyone has their own non-interoperable (but cross platform!) protocols/networks/gardens now. * blackberry bbm * apple imessage * google hangouts * skype * whatsapp, etc. As a user, am I supposed to have an account with one of each of these things? Have nine different apps open all the time? This is as bad as icq/messenger/aim/etc was back i…
Slight nitpick, Apple's iMessage (edit:) and BlackBerry's BBM) aren't _really_ cross platform (unless you consider OS X to iOS cross platform). It isn't really useful beyond Apple's walled garden.
I need a client for Ubuntu then :(
Just to clarify: If you think you need a client because you are currently using an XMPP client with your gmail account, then you do NOT need to switch. See bullet point 1 — XMPP _clients_ are still supported. XMPP _federation_ is going away :(.
Earlier quoted context omitted.
Why is it not utilized more widely then? foregoing for a minute that everyone is cultivating their own gardens - what are the weaknesses of XMPP that would make it so easily avoidable for most of these apps?
It's definitely not the lack of features, since XMPP is extendable. I've heard that the protocol is quite chatty and would cause power drain on phones. That could probably be solved with a binary serialization alternative to XML, though.
As for a binary serialization, XMPP traffic does compress very well already (TLS/zlib/lzw), but we have started the process on standardizing the use of EXI (https://en.wikipedia.org/wiki/Efficient_XML_Interchange).
Earlier quoted context omitted.
Why is it not utilized more widely then? foregoing for a minute that everyone is cultivating their own gardens - what are the weaknesses of XMPP that would make it so easily avoidable for most of these apps?
It's definitely not the lack of features, since XMPP is extendable. I've heard that the protocol is quite chatty and would cause power drain on phones. That could probably be solved with a binary serialization alternative to XML, though.
However, the XMPP community has been active in quantifying such issues and providing solutions. The beginning of a document with background information is available as http://xmpp.org/extensions/xep-0286.html. There are also various opinions on the topic to be found online, like http://www.deepdarc.com/2008/02/14/mobile-xmpp/, that, as you can see, dates back half a decade already.
Something interesting is going on here. If you log in to Plus, you can use New Hangouts _right now_. And they _do_ interoperate with XMPP users _right now_ -- I just tried it. So does this mean the rollout is not complete, and what they rolled out as Hangouts today is not what they'll ultimately roll out? Or does it mean -- as I suspect -- that New Hangouts is XMPP under the hood, but they plan to flip the 'interoper…
Hangouts CAN NOT communicate with XMPP clients.