You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For Talk an OCS endpoint would be preferred. This way also mobile clients can show the information.
If the user status is uniquely identifyable (hardcoded message_id like the in_call), we can use that as an indicator to see if we should contact the OOO endpoint to load more info. The user status is returned on the conversation list, but I guess we wouldn't want to load even more data for all users every 30 seconds.
How to use GitHub
Is your feature request related to a problem? Please describe.
Users can enter OOO info via #40616. Apps want access to this data and react when a users goes to or returns from OOO.
Describe the solution you'd like
Add an OCP API that exposes the OOO information. Add events for the start and end of OOO.
Describe alternatives you've considered
N/a
Additional context
N/a
The text was updated successfully, but these errors were encountered: