Hi,
TLDR: It is common practice for CSI (Client State Indication)
implementations to withhold (and deduplicate) PEP notifications and/or
headline messages. Due to the rise of XEPs such as Message Displayed
Synchronization (MDS) those implementations need to be changed to
immediately let through PEP notifications from nodes that are on the
account itself.
I noticed the MDS problem in theory a while ago but didn’t care too
much because due to a lack of implementations I’m not using MDS on a
daily basis. (MDS needs to be able to dismiss notifications even if
the client is in background)
However today I ran into a related problem with Bookmarks 2 and User Nickname.
I was writing code that actually performs a rename in a MUC if the
desired nick changes (either pulled from the bookmark or if that one
is unset from XEP-0172) instead of only using these sources on initial
join. I think it is somewhat obvious that the rename should be done
fairly instantly on all clients once a client has made the change
(either to the bookmark or to 0172). Otherwise other users would see
the user as being joined multiple times with different nicks until all
clients have come to the foreground.
I guess letting through all PEP notifications from the account
(instead of allow listing certain nodes) is good enough. That’s
beneficial for Nick, Bookmarks, OMEMO. The only one for which we
technically don’t need it is Avatar. But how often do you change that
one (meaning how many false positives would you generate?!)
cheers
Daniel
Version 1.0.0 of XEP-0490 (Message Displayed Synchronization) has been
released.
Abstract:
This specification allows multiple clients of the same user to
synchronize the displayed state of their chats.
Changelog:
Accept as Stable as per Council Vote from 2024-11-05. (XEP Editor
(dg))
URL: https://xmpp.org/extensions/xep-0490.html
Note: The information in the XEP list at https://xmpp.org/extensions/
is updated by a separate automated process and may be stale at the
time this email is sent. The XEP documents linked herein are up-to-
date.
Good morning Council Members,
the next XMPP Council Meeting will take place on, Tuesday, November 5
2024 at 16:00 UTC in xmpp:council@muc.xmpp.org?join
The Agenda is as follows:
1) Roll call
2) Agenda Bashing
3) Editors update
- none
4) Items for voting
a) Move 'XEP-0490: Message Displayed Synchronization' to stable
https://xmpp.org/extensions/xep-0490.html
5) Pending votes
Travis on 3 PubSub proto xeps from last week.
See the spreadsheet of Doom:
https://docs.google.com/spreadsheets/d/1H310M8z6Kdo6XyNf2DwafzrSLuwhaLNvzfa…
6) Date of Next
7) AOB
8) Close