3 ms·
Edit: Github link at [3], couldn't find it when I originally wrote my comment below I wonder how this compares to alternatives like [1] and [2] that you can al
by jeroenhd 4y ago
Edit: Github link at [3], couldn't find it when I originally wrote my comment below
I wonder how this compares to alternatives like [1] and [2] that you can also host yourself.
There was also a Matrix project *that I can't find for the life of me) featuring multi-agent live chat support with multiple agents being able to join and leave a room. I suppose the E2EE support is what sets it apart, though I'm not sure if that's actually a feature you really need.
Half the features advertised seem to be existing EMS features (like talking across chat services). I suppose you can use this to portal a web chat box into Slack but honestly I think there are better solutions.
[1]: https://github.com/osousa/livematrix https://github.com/osousa/livematrix
[2]: https://github.com/nomadic-labs/safesupport-chatbox https://github.com/nomadic-labs/safesupport-chatbox
[3]: https://github.com/vector-im/chatterbox https://github.com/vector-im/chatterbox
- Arathorn 4y agoYou can host chatterbox yourself too - it’s apache licensed FOSS (https://github.com/vector-im/chatterbox https://github.com/vector-im/chatterbox).
- jeroenhd 4y agoOh, I see! I was looking under the matrix-org Github account so I couldn't find the source code, I probably should've looked at the vector-im tag as well.
- tcfhgj 4y agoThe former doesn't have encryption, but good question
- osousa 4y agoHi there. I wrote [1] (Thanks for the reference) , and i skipped encryption for the sake of simplicity. I'm enabling encryption as we speak. If you host the server yourself, on a controlled setting (VPS), it should allow for a fairly secure way of communication if TLS is used. The communication channel would resemble this rough ASCII drawing: [Browser] <---TLS---> [livematrix] <---e2ee---> [Matrix homeserver] In the end you always have to trust the person hosting the service. Host things yourself. I don't see this channel of communication as being truly secure, without audits where and how its deployed. Web apps are riddled with vulnerabilities, how much of the attack surface from a website would compromise the live chat embedded is a guess until it happens. I should point out that my "solution" is intended for personal websites, people who enjoy Matrix a lot :) . Not for corporations at all.
- jeroenhd 4y agoTLS for browser communication should work great; if the website can't control its scripts, then there's no reason to trust its execution anyway. The main problem space, in my opinion, is encryption support between your service and the Matrix server, as messages get stored long-term in that space, which comes with possible privacy risks. Your solution would probably mitigate that problem perfectly!