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.
Show HN: Kaiwa, a Modern Open-Source XMPP Web Client
11–20 of 142 posts
Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client
#12Looks just like Slack.
Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client
#13Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client
#14Excellent work. Is there a reason why you chose Prosody over MongooseIM or ejabberd?
Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client
#15Excellent work. Is there a reason why you chose Prosody over MongooseIM or ejabberd?
Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client
#16It's not like it's revolutionary. They put two and two together in the only reasonable manner for a single-page application.
Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client
#17Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client
#18Can I chat with Google Talk users from this?
Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client
#19I'm curious how E2E encryption (OTR e.g.) could be implemented with a client like this (preferably without having the keys leaked all over the place), it's the only interesting feature I miss from a quick glance.
Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client
#20- 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 inline. That's possible with Adium but I'd really like to replace Adium)
Thanks!