3 ms·
The problem is everyone is making a product not a protocol. Slack,discord,matrix they all care about having thie feature and that feature instead simple e2e enc
by _8j50 4y ago
The problem is everyone is making a product not a protocol. Slack,discord,matrix they all care about having thie feature and that feature instead simple e2e encrypted plain text messaging.
That said, depends on what you mean my hackable. Python and restful api can be much easier to work with and hack than IRC because with IRC if you don't use a library you still have to account for various scenarios and do quite a bit of parsing and server specific command handling.
- lsh123 4y agoThere is no “simple e2e encrypted messaging protocol” ;) the protocols used by Signal, WhatsApp, etc are very well thought out but they aren’t “simple” because keys are changed on every messages and both peers need to maintain and manage keys. With group chats the situation is even more complex. And making group chats with a large number of users (this is what IRC does btw) work well is a very complex technical problem.
- _8j50 4y agoTLS isn't simple but you still use it with IRC. Libolm/e2e is the session layer not the application layer. Why is there no library that handles key management,session handling,etc... for you and all you have to do is make a library api call similar to TLS with the destination, encoding and message size limit details as a parameter and each send() operation requiring a recipient so the library can handle the auth/encryption? Can you not do that with libolm? Why can't you use IRC on top of such a library then similar to how you would with TLS?
- lsh123 4y agoI am not arguing that library can be built. I am just saying there are no simple e2ee messaging protocols ;)