Show HN: Kaiwa, a Modern Open-Source XMPP Web Client • Hacker News Board

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

#61

Post by nickysielicki » Wed, Apr 08, 2015, 2:42 PM UTC

ge0rg wrote: post #43

nickysielicki wrote: post #35

screen + ssh + irssi (+ bitlbee, if you need xmpp) > any web based solution. Why? Because I can see it on my phone and on my laptop, and it's as lightweight and simple as a `ssh -t irssi.myDomain.foo screen -DD -R` and I'm all caught up. This is, ofc, my $0.02. Stuck in the old way of doing things, I guess. Still pretty cool, particularly the deploy on DO.

Except for being almost unusable on smartphones (or barely usable on devices with qwerty keyboards), and bitlbee's arcane syntax for joining MUC chatrooms, this is the exact setup I am using.

Juicessh fixed many of those problems when I used an android phone, ymmv.

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

#62

Post by warcode » Wed, Apr 08, 2015, 2:43 PM UTC

davidchua wrote: post #34

Is there any chance we will see webhooks in a future release? (ie. slack integration)

Look for any integration-bot with an XMPP interface.

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

#63

Post by ge0rg » Wed, Apr 08, 2015, 2:44 PM UTC

mosselman wrote: post #47

ge0rg wrote: post #22

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/

Thanks for the suggestions. Do they also provide the group chat support? As, I believe, the 'normal' XMPP protocol doesn't support groups.

Not sure about ChatSecure, but xabber provides MUC (group chat) support out of the box, and for yaxim there is a beta APK you can get here: https://yaxim.org/muc

The beta's limitations are:

* rather broken invitation handling user interface

* cumbersome MUC joining user interface

* impossible to downgrade to non-beta builds

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

#64

Post by thebouv » Wed, Apr 08, 2015, 2:44 PM UTC

userbinator wrote: post #41

tgaussman wrote: post #29

The very first sentence irks me: "[…] for the only standardized chat protocol [XMPP]" Haven't they heard about IRC (RFCs 1459, 2810–2813)?

I noticed that too, plus the fact that the "Rooms" are preceded by # signs in the list. There's probably some IRC influence.

Slack uses that # convention as well (also probably inspired by IRC).

That and the use of hashtags to group things together on Twitter, etc.

I guess it's just a "thing" now.

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

#65

Post by xorcist » Wed, Apr 08, 2015, 2:55 PM UTC

There has been a deluge of web chats lately (which is a good thing).

Has anyone tried Let's Talk, Shout, Echoplex, and/or Kaiwa in practice and have some experiences to share? Stability, searchability, general functionality?

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

#66

Post by Brajeshwar » Wed, Apr 08, 2015, 2:57 PM UTC

Wow! Nostalgia.

If I remember correctly, "Kaiwa", was the codename for the first Macromedia's Flashcom Server (before Adobe's acquisition).

Flashcom Server at that time made it possible to run 2+ ways multi-threaded communication (audio/video) via the Flash Player (2003-ish).

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

#67

Post by jkire » Wed, Apr 08, 2015, 2:57 PM UTC

tgaussman wrote: post #29

The very first sentence irks me: "[…] for the only standardized chat protocol [XMPP]" Haven't they heard about IRC (RFCs 1459, 2810–2813)?

There's also http://matrix.org ; though it's not going down the RFC route (at the moment at least).

There seems to be this general assumption at the moment that a) XMPP is the only open chat protocol about and b) its dead, so everyone decides that the only logical course of action is to write and use custom proprietary protocol. This, of course, massively sucks from a UX perspective where I end up having 100s of identities and apps and logins that I use (semi-)regularly to not just chat with people, but also comment on articles, discuss things on mailing lists etc.

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

#68

Post by 13 » Wed, Apr 08, 2015, 3:04 PM UTC

ge0rg wrote: post #43

nickysielicki wrote: post #35

screen + ssh + irssi (+ bitlbee, if you need xmpp) > any web based solution. Why? Because I can see it on my phone and on my laptop, and it's as lightweight and simple as a `ssh -t irssi.myDomain.foo screen -DD -R` and I'm all caught up. This is, ofc, my $0.02. Stuck in the old way of doing things, I guess. Still pretty cool, particularly the deploy on DO.

Except for being almost unusable on smartphones (or barely usable on devices with qwerty keyboards), and bitlbee's arcane syntax for joining MUC chatrooms, this is the exact setup I am using.

I don't have any trouble at all using Colloquy on iOS and connecting back to my bouncer. It's about as seamless as you could expect all things considered.

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

#69

Post by hsivonen » Wed, Apr 08, 2015, 3:04 PM UTC

No mention of OTR. :-( When your client is a Web app on a trusted server (i.e. OTR key on the server), you could avoid multi-client issues by having only that on XMPP client that you connect to from multiple browsers.

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

#70

Post by jkire » Wed, Apr 08, 2015, 3:06 PM UTC

LaSombra wrote: 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.

> 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

And its nice to be able to choose which apps you want to use on all the different platforms; and choose differently than everyone else. The app that works for me isn't necessarily the app that works for others, but I still want to be able to talk to them using the app I want.