Seems to point to a larger issue. With over 100 million users, we need
them in the game. Otherwise, it's just Google on the numbers. Why
isn't this protocol important to Web communities? I'm primarily a web
developer, who has integrated XMPP through BOSH on my own network, and
even integrating with Google is a difficult prospect, since they only
implement a few extensions. Not just that, but the social aspect of
it: people associate XMPP with IM, and this is somehow antithetical to
the old in-out missionary style of server-client HTTP. Personally, I
don't believe this, but from contact with the Web community, I know it
to be true.
I like XMPP, but seriously, from the Web side of things, I think the
perspective must be that this is somehow competing with more HTTP-
centric things like Atom, APP and REST. Or just that this is too
difficult and/or buggy to deal with. Personally, I think it could
bring a new dimension to the Web. And I think a lot of Web folks think
so. For a bit, it seemed that Twitter was almost going to do it, and a
few others too. But something always rears its head to deter people
from experimenting too much with XMPP.
I'd like to see something happen to change this. I know that's kind of
what this list has been about. Just throwing this out there as a
tidbit from the other side, since the list has been quiet for so
long ... food for thought.
Aaron
On Feb 24, 2009, at 10:56 AM, Peter Saint-Andre wrote:
Steffen Larsen wrote:
So I belive that they only use XMPP internally and haven't opened'
it up
to the public?. Anyone know why?..
My understanding is that it's not a high-priority project for them and
they don't have a developer to dedicate to it.
Peter
--
Peter Saint-Andre
https://stpeter.im/
