Folks have looked at building a telepathy connection manager for Matrix in the past (starting with https://github.com/gergelypolonkai/matrix-glib-sdk and working outwards), but rapidly hit major impedance mismatches with telepathy's API which sadly dates back to a simpler age of IRCv2 and 1st generation IM apps like ICQ or MSN. 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 So, the choices are either to build a new version of telepathy with that sort of featureset, or build something new which exposes Matrix's API via Dbus or similar. One could then use local or remote bridges to other protocols (or follow the "connection mgr" pattern to implement them locally, but given that would barely be using Matrix at all it's not really our focus). M
|