Hi,
On Tue, 2026-03-17 at 12:31 +0000, Stephen Paul Weber wrote:
(a) Markup to
the body, that has the purpose to indicate that a
part of
the body is referring to a user or a group of users
(b) Some indication that the message should have some sort of
priority
to a user or a group of users
In the direct mention case, I don't think we really wrnt to allow one
without the other.
Who is "we"? I certainly want to do it and do so regularly in Slack.
Mentioning people that are not in the room is kind of normal in
physical conversations, why shouldn't it work in digital rooms? And
just like in a physical room if you mention a person that is not in the
room, they won't get notified - except if someone explicitly forwards
the message to them.
Of course you don't need to support that in your client if you don't
like it. It remains a useful feature for others though.
I am also against noping though. It is not up to the
sender if I want
to be notified.
How would the recipient client know if a person is mentioned because
they're being referred to or if the mention happened to indicate to the
recipient that this is relevant for them. Not every message that
mentions a person is also relevant to them. For example when X writes
to Y "The council consists of 5 individuals: [A,B,C,D] and
[singpolyma]" (with the latter being a mention), that's not necessarily
meant to be notifying you, that's really just mentioning you.
Of course you don't need to comply with that in your client either if
you don't like it. It remains a useful feature for others though.
And if we use occupant id the idea of cross-room
mentions becomes not
possible. I'm not sure what the use case for those is but if we wand
that I suppose we should use URI.
The ProtoXEP also allows for mentioning people by JID. I'm very much
open to also mention people by URI (allowing for mentioning of non-XMPP
people, via e.g. tel:, mailto: and acct: URI). In all cases, the idea
of a mention is that recipients can identify the person being
mentioned. If you mention someone by occupant-id, that should only
happen within the scope of the room, as otherwise the occupant-id might
be unresolvable (if the message recipient isn't in the room that
assigned the occupant-id).
Marvin