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

Custom Status #22

Open
nadonomy opened this issue Nov 5, 2020 · 6 comments
Open

Custom Status #22

nadonomy opened this issue Nov 5, 2020 · 6 comments
Labels
all All platforms: Web, Desktop, iOS & Android.

Comments

@nadonomy
Copy link
Contributor

nadonomy commented Nov 5, 2020

Summary
Users expect to be able to set custom statuses (Away, Do not Disturb, On Holiday, Visiting the France office, etc...) in productivity contexts, and they're a nice to have in most others.

Intended Outcome
Support custom statuses. Consider setting autoresponders for people contacting you when away to receive an automated reply.

@nadonomy nadonomy added the all All platforms: Web, Desktop, iOS & Android. label Nov 5, 2020
@Sorunome
Copy link

You can already PUT a status_msg, though? https://matrix.org/docs/spec/client_server/latest#put-matrix-client-r0-presence-userid-status element just doesn't display them anywhere.

@ddmesh
Copy link

ddmesh commented Nov 8, 2022

Long time since last update on this issue. It is really important to allow people to hide their online status. currently all messengers do support hiding the online status.
I have seen that there is an api call "set_presence" which allows this. but this such a configuration should be available in client.
As users may install different clients, a server side (home server) configuration for the whole account which controls the
online status, would be great.

In LABs flags there is no flag that allows to being "offline", only the read receipt can be muted.
Ar there any plans to set this issue to a higher priority?

Thanks a lot

@JesusLV
Copy link

JesusLV commented Mar 4, 2024

Is there any update about this ticket?. Will be helpful to have this feature in our Team

@benedikt-wegmann
Copy link

Many requests for this feature.

Additionally, critical voices make this into a privacy feature as well if there were an "invisible" option. Currently - in theory - the forced online/idle status when using a company instance would allow the "tracking" of a user's/employee's activity/inactivity by any other user on the service.

@RightInTwo
Copy link

RightInTwo commented Oct 24, 2024

It's weird to me how such a basic feature that even has an appropriate endpoint is not available on a client modern chat with such bold claims - just like a "send later" feature. If users come from competitors and miss many of the modern features they got used to and integrated in their workflows, they might be disappointed in what can be offered.

EDIT for clarification: I might be was mistaken about the API's capabilities, because it's not the only thing that can change a Status.
https://spec.matrix.org/latest/client-server-api/#get_matrixclientv3presenceuseridstatus and https://spec.matrix.org/latest/client-server-api/#put_matrixclientv3presenceuseridstatus

EDIT2: Thanks @defnull for the explanation - it's a matrix limitation. And why should it be easy? :) I changed my comment accordingly.

@defnull
Copy link

defnull commented Oct 24, 2024

If I read the spec correctly, then clients can set the online status explicitly, and also avoid to be automatically marked as 'online' when polling the /sync endpoint. But 10.8.2.1 says "Any activity that bumps the last active time on any of the user’s clients will cause the server to automatically set their presence to online." which means that there is currently no way to implement a reliable 'Incognito' or 'Invisible' mode on client side. Any "pro-active event" (e.g. sending a message) from any device will set the status to 'online' and trigger m.presence events.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
all All platforms: Web, Desktop, iOS & Android.
Projects
None yet
Development

No branches or pull requests

7 participants