5 ms·
Excellent work. Is there a reason why you chose Prosody over MongooseIM or ejabberd?
by hackerboos 12y ago
Excellent work.
Is there a reason why you chose Prosody over MongooseIM or ejabberd?
- sebu77 12y agoThank you. We chose Prosody because it supports the XEP we needed and it was originally used by Otalk from which we forked.
- bobzoller 12y agoCould you talk about why you forked Otalk? All I could find was the diff[1], and it seems like Otalk is still active. 1: https://github.com/otalk/otalk-im-client/compare/master...digicoop:master https://github.com/otalk/otalk-im-client/compare/master...di...
- creshal 12y agoRelatedly, why are you recommending only Pidgin, and not Gajim? Gajim covers a lot more XEPs than Pidgin (e.g. editing sent message).
- emixam 12y agoWe have updated the page to recommend Gajim instead. It is a better choice indeed.
- drcross 12y agoAlso Conversations doesnt allow for customer server IP address so it's unusable for me. Yaxim does which is why I will have to stay with it. Custom IP server addresses are important if you have DNS/NAT complications within your internal network compared to outside.
- creshal 12y agoCan you use SRV records for this? Or is that unsupported too?
- vaskas 12y agoAlso, I don't believe that Monal is open source. You might also want to add https://chatsecure.org/ https://chatsecure.org/.
- creshal 12y agoIn my experience, prosody has an easier to configure (and thus harder to fuck up) LDAP integration, and while ejabberd's core is solid, the modules vary wildly in quality (I never managed to get mod_shared_roster_ldap to work, e.g.).