| Summary: | Add support for MTProto (Telegram) | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Yajo <yajo.sk8> |
| Component: | general | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED MOVED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | dev, pochu27 |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Yajo
2014-02-17 15:38:05 UTC
Connection manager implementations welcome. Note that Java is an awkward language to be writing connection managers in: by far the best-supported is C (or C++) with GLib, via telepathy-glib. I think telepathy-qt might have some experimental support for writing Qt connection managers too. See also <https://lists.debian.org/debian-devel/2014/02/msg00081.html>, <http://unhandledexpression.com/2013/12/17/telegram-stand-back-we-know-maths/> for some concerns about Telegram's security, which doesn't seem to be any better than XMPP with TLS (it does have the potential to be end-to-end secure, but so does XMPP via OTR or XTLS if someone wants to help us implement that). KDE are planning on writing a CM on TpQt for GSOC 2014. I'll update this when we have work in progress, which will hopefully be around June with a release nearer September. (In reply to comment #2) > KDE are planning on writing a CM on TpQt for GSOC 2014. > > I'll update this when we have work in progress, which will hopefully be > around June with a release nearer September. Will this be for Telepathy 0 or Telepathy 1? We're hoping to have Telepathy 1 become API-stable within the next few weeks. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-spec/issues/173. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.