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.
I for one welcome slack competitors, self-hostable, open sources ones especially.
Show HN: Kaiwa, a Modern Open-Source XMPP Web Client
51–60 of 142 posts
Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client
#52Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client
#53Earlier quoted context omitted.
OTR also breaks Message Archive Management (MAM) and Carbons - the two features making multi-client operation any useful, and highlighted in the article. And with MAM, there actually are plain-text logs of your conversations on the server. The call is still open on end-to-end encryption over XMPP when multiple devices (or more than two parties) are involved.
The issues you list (message archive being plain text, key management when multiple recipients are involved, maybe even transparently) don't seem to be XMPP specific. Is there any chat system out there with end-to-end crypto and reasonable support for multiple devices?
Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client
#54I think that should say "servers" plural.
Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client
#55Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client
#56Is there any chance we will see webhooks in a future release? (ie. slack integration)
Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client
#57I've been working with XMPP and a number of XMPP daemons. A couple years later I'm not a fan.
I love to receive feedback (of any kind), as it's the only way we know what we're doing right and wrong!
Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client
#58What prevents me from adopting XMPP for my team is the lack of push notifications to my phone. I don't want to have an app constantly maintain a connection and slowly drain my battery.
Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client
#59Earlier quoted context omitted.
OTR also breaks Message Archive Management (MAM) and Carbons - the two features making multi-client operation any useful, and highlighted in the article. And with MAM, there actually are plain-text logs of your conversations on the server. The call is still open on end-to-end encryption over XMPP when multiple devices (or more than two parties) are involved.
The issues you list (message archive being plain text, key management when multiple recipients are involved, maybe even transparently) don't seem to be XMPP specific. Is there any chat system out there with end-to-end crypto and reasonable support for multiple devices?
Besides, it is not available for non-Apple devices.
TextSecure/Signal has a robust crypto system, and they are working on multi-device support.
Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client
#60What prevents me from adopting XMPP for my team is the lack of push notifications to my phone. I don't want to have an app constantly maintain a connection and slowly drain my battery.