Live data from Hacker News

Show HN: Kaiwa, a Modern Open-Source XMPP Web Client

getkaiwa.com

51–60 of 142 posts

Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client

#51
post #31
post #7

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.

Maybe you'll be interested in Talqee [1] which offers a self-hosted version. It's coming really soon :)

[1] https://talqee.com

Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client

#53
post #44
post #26

Earlier 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?

They aren't XMPP specific, but OTR as implemented in e.g. Pidgin goes above and beyond in making them bad – archiving is either plain text or disabled, keys cannot be changed at all (so not even manually syncing them is possible), and session handover doesn't work (there's a session management implemented, but it doesn't do anything except silently eating messages).

Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client

#57

I've been working with XMPP and a number of XMPP daemons. A couple years later I'm not a fan.

If you have tried Prosody and have any feedback on it, I'm all ears (or drop us an email at developers (at) prosody.im).

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

#58
post #55

What 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.

The Conversations app for Android works pretty well. I've used it for a few weeks with a handful of persistent rooms on a Nexus 5 and I haven't noticed any battery issue.

Re: Show HN: Kaiwa, a Modern Open-Source XMPP Web Client

#59
post #44
post #26

Earlier 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?

As funny as it sounds: iMessage. The only crypto-related problem with iMessage's encryption is that Apple controls the key servers. -- http://techcrunch.com/2014/02/27/apple-explains-exactly-how-...

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

#60
post #55

What 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.

Push has been formally specified very recently in XEP-0357 (https://xmpp.org/extensions/xep-0357.html), now is the time for implementors to show what they have !
Post reply on HN