What I want to investigate at some point is the idea of setting up a web chat client with a hardcoded login to be used as a tech support channel and such. The user would only be able to chat with a predefined contact our #MUC.
I have no *need* for it right now but it is one of those things that you'd just like to see done.
@debacle @0 this is the use case for anonymous login. You can have a fixed MUC and just allow these user sessions to join without hard coding anything. I'm pretty sure it's not hard to configure Converse for this but I've never actually had a need to do that.
Obviously you wouldn't allow outbound federated use of those sessions or you'd be an unpopular figure very quickly heh.
> It probably should not be a fixed JID, but a randomly generated one. Otherwise replies by helpdesk go to all open web clients in parallel
Not if you direct the response to a specific resource (obviously this account wouldn't use carbons). The resource itself would be session specific though.
I only compare it to ConverseJS really since using it in its full-screen mode is the closest we really have to a decent web-based client right now.
Movim is good, but chat isn't its focus really and the social/blogging aspects make it feel very cluttered to me. Compatibility with Movim's WebRTC calling would be an amazing thing to have though.
@stevenroose thanks for the pointer, I missed Opa. I'm more inclined to poke at that one right now, as I intended to MIT license anything I came up with. I'll have a mess around with both over the next couple of weeks though.
Consider this a friendly, local pub. Make yourself at home, bring your friends, have a good time! Meet new people, have a laugh, enjoy the ambience, and the Oxford commas.