Ask HN: Would you recommend such software in your org?
Hi,
I'm wondering if I'm the only one that feels uneasy with MS Teams, Slack or Google Meets.
I'm thinking of building an open-source communicator:
1. Zero–knowledge server for maximum privacy:
- users have no passwords,
- server doesn’t know who the sender is,
- server is unable to see a message content
2. A client software where every message/call must be encrypted and sender/caller is verified.
3. Can be self-hosted or used as a SaaS offering.
4. No lock-in. Designed in such a way that migration to other server does not require cooperation from the current server’s operator. Client software is server agnostic.
5. Fully open source (probably GPL).
6. No central authority that can disable account or deny service. No global central point of failure.
6 comments
[ 3.2 ms ] story [ 29.1 ms ] threadMeanwhile is https://element.io/matrix-services the people behind Matrix caring about getting this in commercial usage.
This is the part where I'd compare it to the CVEs of other popular messaging apps, but most of them don't have the confidence to be this transparent with their audience. YMMV, but "rolling your own" groupware isn't going to be safer than using an alternative supported by two or more users.
It isn’t a bug in Matrix itself, or Matrix servers or clients, but an IRC-specific thing in that IRC bridge implementation. It’s obviously a nasty bug from an IRC perspective, but it really doesn’t feel like something that should stop you promoting Matrix. It feels a bit like we are being penalised for being transparent on publicising security issues…