Modern XMPP project discussion - 2023-04-07

hi. i'm looking into implementing bookmarks and found https://docs.modernxmpp.org/client/groupchat/#bookmarks

playing around with some clients it seems that basically none of them really prefer PEP

at least not dino and gajim for example. dino will actually fetch the PEP bookmarks but not update them later

Clients that do support XEP-0402 generally only enable it if the `urn:xmpp:bookmarks:1#compat` feature is advertised, or the different clients would end up with different sets of bookmarks.

wouldn't they end up with different bookmarks either way, since the client not implementing the new ones would update the old way?

No, that feature means that both methods access the same bookmarks.

E.g. in Prosody it means that a module is handling legacy private XML and translating XEP-0402 data for you.

ok, so without the server supporting the compat feature via a module like that, nobody can implement 0402 really

in a new client that is

since everyone else just ignores 0402 and you will definitely end up with different bookmarks between clients

correct?

For specialized deployments you could get away with it, but generic clients for the current ecosystem will likely need to fall back to private xml a while longer if they want to work with most servers.

(Read: We're waiting for https://github.com/processone/ejabberd/issues/3591 )

Do any servers but Prosody support 402 yet?

There's a button to the right on the XEP-0402 line at https://xmpp.org/extensions/ you can click to see who's got it implemented

cool, thanks

Server-side, it made it *so* much easier to interface with bookmarks after switching.

raucao, 👍️ any issues, poke other server devs and operators so they implement and deploy XEP-0402 :)

i mean, it's implemented when there's PEP

yeah but then you have an absolute mess unless all your other clients also do XEP-0402

aaaand that's hard to be sure of since users might try different clients from time to time

i totally see that. i also see how a server dev might hate having to implement extra compat code :)

that's why there's that compat feature for server-side unifying bookmark storage, all those problems go away

until the day we're ready to finally be rid of the old

The nice thing with implementing it as a translation layer that stores the bookmarks in PEP natively, once all clients are ready, we can simply deprecate and delete the compat module.

We did the same thing with vcard-temp vs vcard4

so, i was actually asking because i want a server-side hook for when someone registers an account with us to be auto-joined into a specific room. the reasonable choice is 0048 in that case

until everyone's agreed to prefer 0402 that is

> The nice thing with implementing it as a translation layer that stores the bookmarks in PEP natively, once all clients are ready, we can simply deprecate and delete the compat module. true. it will be a nice day one day :) ↺

the trick is to bait people with ✅️ :)

https://xmpp.org/extensions/xep-0459.html#changes-2021 does say you should do 0402, so if you don't, no green checkmark for you

weird as it is, https://compliance.conversations.im/ has the ultimate power to decide what gets implemented and deployed

everyone knows *blue* checkmarks are the most attractive

could even make 0402 cost $8 per month

very elite feature

<this message is only available to Prosody Pro users>

i see it's "information" on the test suite

i only need my 100% lol

yeah, that's why it's not implemented and deployed everywhere yet

only prosody, because we care about things other than green checkmarks :)