111–120 of 142 posts
I am glad projects like these are being worked on. Desktop XMPP programs are terrible. I have had a hard time hosting my own chat service for friends,family and work because the clients never work together for file transfers. I just wish these were easier ''FOR ME'' to install on FreeBSD.
I am glad projects like these are being worked on. Desktop XMPP programs are terrible. I have had a hard time hosting my own chat service for friends,family and work because the clients never work together for file transfers. I just wish these were easier ''FOR ME'' to install on FreeBSD.
There doesn't seem to be much in the way of install instructions for anything, except the digital ocean automated installer, which also sets up a prosody server.
[0] https://github.com/digicoop/kaiwa-server/blob/master/README....
Earlier quoted context omitted.
Besides of the ones referenced in the article, there is also ChatSecure [0] for Android and iOS (with a strong focus on security) and Xabber [1] and yaxim [2] for Android (I am the maintainer of yaxim). [0] https://chatsecure.org/ [1] http://www.xabber.org/ [2] https://yaxim.org/
I've been using Monal " rel="nofollow">http://monal.im/> on iOS - decent UX, supports groupchat, doesn't put a "proxy" between you and your server, etc.
Any plans of making LDAP optional? I am already running a prosody server and have no use for it.
This looks great - I'd like to give it a try. Does it work with ejabberd?
I'm planning on setting this up for myself later today but a few questions before I do that: - Will this stay connected to my account and the history will be there if I close the tab / browser / computer in the meantime? - Is it possible to replace certain strings with images? This is not at all an important feature but just something I got used over the years. (Example: :string: replaced with image.png and displayed…
On the homepage they mention they use Message Carbons, so your history should be retained, yes: Using Message Carbons (XEP-0280) all of your active conversations will be synced to your Kaiwa client. Don't know about the second question as I haven't looked at the source, but it doesn't seem all too hard to implement even if its not there.
I understood the question as "will I be able to receive messages while the tab isn't open" (offline messages) and "will I be able to read my history on a different device later on" (MAM). Carbons serve a different purpose and sync connected clients (i.e. you chat on your desktop, but your phone receives the same messages as a carbon copy to stay in sync).
In my opinion, it doesn't matter if it looks like Slack. What matters is that I can deploy it on an existing infrastructure and still have control over the service instead of handing over control to a third-party.
In my opinion, it does matter. Slack is pretty and familiar, so an app looking alike is a good thing.