On Fri, 2017-08-25 at 14:00 +0100, Matthew Hodgson wrote:
From memory, the sort of modern features which Matrix has which the API doesn't handle include: * Infinite scrollback serverside history * Synced history across multiple devices * Server side search * Server side notification settings * Read receipts * Read-up-to markers * Multiway voip * Promoting 1:1s to group chats and vice versa * Native end-to-end encryption (verifying keys, devices, sharing keys, etc) * Encrypted file transfers * Redacted msgs And upcoming shortly: * Reactions / upvotes / downvotes * Editable msgs * Pinned messages * Threading
Matrix isn't the only protocol that supports many of those. I'm no fan of Telepathy, certainly — the complete lack of error reporting was what caused me to ditch it and stick with Pidgin for corporate Lync users. When users are completely unaware that they aren't reachable on IM, or why, that's a total UX fail. But I still think we're better off with a *generic* framework, even if we have to drag it into the 21st century, than tying ourselves into a single protocol. Of course if you want to go and make a lovely shiny UI for your single protocol, nobody should dissuade you from that. But to talk about it as a "replacement for Telepathy" doesn't make sense to me.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature