Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

We should support revealing whether the user is currently typing on mobile/web/etc (SPEC-128) #29

Open
matrixbot opened this issue Mar 15, 2015 · 4 comments
Labels
A-Client-Server Issues affecting the CS API feature Suggestion for a significant extension which needs considerable consideration

Comments

@matrixbot
Copy link
Member

It'd be fun and useful to optionally show whether a user is currently interacting with matrix via a phone, browser or whatever. a bit like fb does. it'd make people more sympathetic to typos and response time etc

(Imported from https://matrix.org/jira/browse/SPEC-128)

(Reported by @ara4n)

@matrixbot
Copy link
Member Author

Jira watchers: @ara4n

@matrixbot matrixbot changed the title We should support revealing whether the user is currently typing on mobile/web/etc We should support revealing whether the user is currently typing on mobile/web/etc (SPEC-128) Oct 31, 2016
@matrixbot matrixbot added the feature Suggestion for a significant extension which needs considerable consideration label Nov 7, 2016
@gergelypolonkai
Copy link
Contributor

To remain compatible with old clients, I'd suggest a new key in m.typing. I can't come up with a good name, so let's call it user_ids_ex. The new content then would be:

{
  "user_ids": ["u1", "u2"],
  "user_ids_ex": {
    "u1": ["m.web", "im.riot.web"],
    "u2": ["m.mobile", "im.riot.android"]
  }
}

The idea here is the first value is a standard one, while the second is a custom one, so clients aware of the latter type can even show an icon of that client. Or maybe just stick to one value.

In a future (final v1?) version user_ids_ex could even completely replace the old one.

@gergelypolonkai
Copy link
Contributor

Oh, and users should also choose not to disclose their client type, which may be denoted as m.undisclosed.

@turt2live turt2live added the A-Client-Server Issues affecting the CS API label Feb 6, 2019
turt2live referenced this issue in matrix-org/matrix-react-sdk Jun 27, 2019
Fixes element-hq/element-web#9986

There's a few reasons for pushing this out to its own place:
* In future, we might want to move WhoIsTyping here.
* We have multiple composers now, and although they don't send typing notifications, they could (see https://github.com/vector-im/riot-web/issues/10188)
* In future we may have status for where/what the user is typing (https://github.com/matrix-org/matrix-doc/issues/437)
* The composer is complicated enough - it doesn't need to dedupe typing states too.

Note: This makes use of the principles introduced in element-hq/element-web#8923 and element-hq/element-web#9090
@turt2live
Copy link
Member

and what the user is "typing", eg: uploading files (https://github.com/vector-im/riot-web/issues/7068) or recording a video/audio clip.

@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Client-Server Issues affecting the CS API feature Suggestion for a significant extension which needs considerable consideration
Projects
None yet
Development

No branches or pull requests

3 participants