| Summary: | Think about Calls with the Text type | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Jonny Lamb <jonny.lamb> |
| Component: | tp-spec | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED MOVED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | normal | ||
| Priority: | lowest | CC: | david.laban, olivier.crete |
| Version: | git master | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | Call-later | ||
| i915 platform: | i915 features: | ||
SIP/SDP can also carry the type "application", but I've never seen that in practice, so I guess it's safe to ignore it. A bit more about T.140: It's live text, so characters are send one by one (or in small packets) and you can send stuff like backspace, so it does not fit the normal IM way of thinking. RFC 4103 specifies a way to carry the text over RTP. It's like the "Chat" feature in the old ICQ for those who remember the golden days. That said, maybe we're better implementing that in the CM, but maybe not. Also, this T.140 text normally comes with timestamps, so it could be subtitles (but I haven't seen anyone use it like that). This is all low priority since we don't have an express requirement for it. I reckon it could work as another content (adding another type to the Media_Stream_Type enum, and relying on existing clients not to crash if they don't support it (or using client capabilities). We can let the UI decide how to display it later. Is this considered as a blocker for Call1? No, that's why the whiteboard says "Call-later" This is the same high-level feature as XMPP's XEP-0301, which incorporates "real-time text" into ordinary XMPP IMs - it sends several intermediate versions of each IM as a XEP-0301-specific message (mostly with a diff-like encoding), then the "final" version as an ordinary IM. I'm not sure whether this would be a better fit as a type of Call, or as an extension to Text. -- 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/84. |
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.
This one time, at band camp, Olivier Crête lolled: > There could be calls with the "Text" type (for live text.. ie ITU-T > T.140 and RFC 4103). This stuff is optional in the LTE media > requirements, that said, I'm not certain at all how we will want to > handle this in Telepathy if we want to do it.