Conversation

Diaspora Development Updates

I've gotten a few inputs from #diaspora-dev that merging the current Chat and conversations is not a very feasible solution as it requires two fairy different protocols to be merged together. I personally don't like having two separate ways of private messaging: chat and conversations. My original plan was to find a full page front-end Javascript front-end for XMPP to replace the Conversations page. I was then going to have my Diaspora server automatically reply to any incoming Conversations requests with "This pod has disabled Conversations in favor of the Chat." Unfortunately I couldn't find a front-end Javascript XMPP client that I liked but I did come across an open source instant messaging client Vector. Unfortunately, Vector is not made for the currently used chat protocol but Matrix, a similar decentralized messaging protocol (see Matrix vs XMPP). However, I just love Vector-web's UI, and thus I tried integrating Vector. I currently have Vector integrated into Diaspora to the point where Diaspora can automatically create a Matrix user based on the current user's username in a similar fashion to how the current chat with JSXC/XMPP works. I think the greatest challenge would be helping finish the Matrix-XMPP bridge and figuring out how seed migration for chat history would work (or if it is even possible). While I am pretty motivated to continue down this road, I just want to confirm that there aren't more efficient alternatives of obtaining a full-page front-end chat client within Diaspora.

I've included a picture of a public group chat room of Vector-web embedded within Diaspora.

#diaspora #development #developer #chat #xmpp #matrix