support for custom status

[matrixbot]

Created by @ matthew:matrix.org.

away/ooo/asleep etc

[gwicke]

See also: https://matrix.org/jira/browse/SPEC-15

[ara4n]

dup #285

[Half-Shot]

assigns himself

[Half-Shot]

Currently need to get this looked into first.

EDIT: Fixed :)

[turt2live]

/me repurposes this as status messages

[turt2live]

Fixed by the proof of concept at matrix-org/matrix-react-sdk#2347

By executive decision, away messages and presence messages are tracked at https://github.com/vector-im/riot-web/issues/478

[wioxjk]

Would love to this this implemented,

[haupas]

+15 for this feature :-)

[Opisek]

How is this still not a thing in the largest Matrix client after 8 years, when plenty of small clients have this. It's a simple feature that any other communicator has, and the matrix experience without it feels incomplete.

I tried to find any information in all the other related GitHub issues, as well as the now deprecated roahline, but to no avail. Can we have any timeline for custom status messages?

[t3chguy]

@Opisek Element Web used to support an Element-specific custom status feature but it did not work well (using DM room state) as there is no good way to support them in Matrix until Matrix inherently supports such a feature.

[Opisek]

@t3chguy As far as I can tell, this is already part of the Matrix specification under the field status_msg in user's presence. Is this the same feature as we are requesting here or am I missing something?

• https://spec.matrix.org/v1.10/client-server-api/#events-7
• Add missing status_msg to m.presence schema and example matrix-org/matrix-spec-proposals#1744

On the other hand, the react sdk implements status messages, but I'm not sure if it uses the same part of specification as I mentioned above.

matrix-org/matrix-react-sdk#2347

[t3chguy]

status_msg

IIRC this has some major issues around being clobbered by different devices

On the other hand, the react sdk implements status messages, but I'm not sure if it uses the same part of specification as I mentioned above.

That was the custom implementation I spoke about earlier, which was really faulty.

Either way this is tracked in element-hq/element-meta#425