RFC: add typing timing constants to capabilities
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Is your feature request related to a problem? Please describe.
After https://github.com/nextcloud/spreed/issues/9624 we have fixed timings in typing.
But 10 seconds of throttling with 15s waiting seems a bit long. We may want to change this constant in the future.
The problem is, that desktop and mobile clients have multi-versioning. For proper working, all clients of one server should have the same timing.
Describe the solution you'd like
Add those constants to Talk server's capabilities.
Describe alternatives you've considered
Any other thoughts or ideas?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing issue #9624 and the discussion in pull request #9689 to understand the existing typing timings and why clients need a shared value. Then locate Talk server capabilities and determine how those timing constants should be exposed; done means the requested values are available to clients consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100