13 Mar
2026
13 Mar
'26
9:16 a.m.
On Fri, Mar 13, 2026, at 13:49, Maxime Buquet wrote:
On 2026/03/13, snit via Standards wrote:
Thats what the range is for, to remove the implementation detail or do something with it.
Its an implementation detail that Gajim mentions a user "Nickname, " and another
client "@Nickname:".
Now Gajim will send you a range start/end and tell you which characters are a plaintext
representation of the mention.
You can then choose to remove the text and replace it with something else, or format it in
some color, or do nothing with it.
Usually you would replace the text with some clickable GUI elements which show the
nickname (which you take from your database, not from the text) in some format you decide
is fitting for your client.
But i read your draft again, and i think the confusion might really come from the place
that in your draft you used the range to mark text to which other people should be
notified?
Again, no characters are treated as special here.
Everything that applies to '@' applies to anything else, as well. IF you decide to
send extra characters with your mentions, you include them in the range. It doesn't
matter what those characters are. The receiver shouldn't need to care either;
that's kind of the entire point.
I guess that's where we disagree. As a receiving implementation, why
would you have to display an "implementation detail" from another
client? You can't actually remove that implementation detail if you feel
it should not be displayed in your client, as you do not understand it. the receiving entity MAY use this as a hint that the
specified range of the content is being addressed to the specified occupant.
Thats from your draft. Thats not what i would need as a feature from this spec. For me
start/end should mark the range of the nickname, so i can replace it with GUI and do not
need to use regex and care about false positives.
Regards