>>9
"XMPP is a different protocol from HTTP, it requires a server running on a different port. on a Heroku install, you only get 1 outbound port: 80. Since we want to maintain compatibility with Heroku, and we recognize that Heroku installs make up the bulk of DIASPORA pods (as well as being the most dead-simple way to get a pod going and "own your data"), I don't think XMPP would be the right solution for us at this time.
The use of XMPP itself would be an interesting exploration for a social network, however. it kind-of has federation built in to the protocol, and separating federation to its own application protocol would allow us to focus the Rails app development on making the site look nice and behave well. If we had double the contributors and a whole team dedicated to implementing federation over XMPP, and Heroku magically allowed us to run XMPP servers on their network, this might be an option. But unfortunately, I don't see it being in the realm of reality. Again, I'd be extremely excited to integrate XMPP with DIASPORA because I think it would change the game for us, but I don't see a way we can do it while maintaining backwards compatibility..."
__________________________________________
"Here is the problem :
Heroku only accepts communication using the port 80, so we can't use a solution already created like jappix mini. The only way to add a chat for Diaspora (as far as we know) is to implement it directly inside Diaspora. And, as everybody here is volunteer, nobody has the time to work on it for the moment, unfortunately.
So, if you want a chat in Diaspora, just find someone who can develop it. We will enjoy introduce the project to him."
__________________________________________
https://github.com/diaspora/diaspora/pull/1750