8 Nov
2025
8 Nov
'25
5:47 p.m.
Hi Thilo,
I haven’t looked into this from a protocol perspective yet, but from a
server developer’s point of view: even if we implemented this tomorrow and
released it in a few months (which is pretty fast in server time), keep in
mind that many server admins update… let’s say… at their own pace.
That means new features often reach only a subset of users at first. This
is not as dramatic as it may sound, as it happens for all new server
features. Usually, it is fine: early adopters naturally gravitate toward
servers that keep up to date anyway. But if your solution requires broad
deployment to really be useful (which might be implied by the fact that
you're explicitly asking for server developer perspectives) it might be
worth considering alternative approaches.
Kind regards,
Guus
On Sat, Nov 8, 2025 at 5:00 PM Thilo Molitor <thilo(a)eightysoft.de> wrote:
Hi all!
With XEP-0469: Bookmark Pinning and XEP-0492: Chat notification settings
we now
have two XEPs that allow syncing pinning and notification settings across
clients on the same account using the <extensions/> element of XEP-0402:
PEP
Native Bookmarks.
Unfortunately, this now means that normal 1:1 chats (that are synchronized
as
roster items) lag behind.
I'm volunteering to write a XEP adding an <extensions/> element alongside
the
<group/> element to allow arbitrary extensions for roster items. This
would
bring 1:1 roster items on-par with bookmarks2 and immediately allow
XEP-0492
and XEP-0469 to be applied to roster items as well.
But before I start I want to ask especially the server developers on this
list: would you consider implementing this?
If the answer is no or "some day far far in the future", it might be worth
to
try to invent some other mechanism that could be deployed faster.
In my opinion, however, extending the roster items is by far the most
elegant
and simplest solution.
What do you think?
-tmolitor
_______________________________________________
Standards mailing list -- standards(a)xmpp.org
To unsubscribe send an email to standards-leave(a)xmpp.org