jdev - 2022-02-10

There was a discussion in another room earlier about bookmarks support so I asked around and made a summary of current support for the various specs people are using. Here it is, if anyone else is interested: https://mellium.im/issue/258

TL;DR please go update your servers to support the PEP Native Bookmarks conversion, it's very low right now and having every client implement 3 specs and all in slightly different ways is going to make the upgrade path difficult.

Sam, are you aware of this documentation btw? https://docs.modernxmpp.org/client/groupchat/#bookmarks

I was not, thank you!

Prosody 0.12 (Soon™) will ship with it included and most likely enabled by default. How fare the other servers?

Ejabberd has no support, as far as I can tell

(those are the only two I looked into since I assume the vast majority of services use one of those two and the other servers will likely follow suit)

Sam, note that the upgrade thingy isn’t about converting from old to new, it is about exposing all three protocols to access a single data store.

Also Tigase presumably supports it since their clients only use PEP Native

So when you modify one using one client, it gets broadcasted to all other resources.

Sure

Still an important distinction I think, which “conversion” doesn’t convey.

I'd be very curious to see what happens to the compliance checker if prosody 0.12 is released; I suspect it would be a pretty big bump.

FWIW mod_bookmarks in Prosody does both XEP-0402 conversion and XEP-0411 conversions, in the same module.

Sam, nah, all of the Debian users will only use it five years later when the current distribution becomes oldoldstable.

Fair point.

Link Mauve, outch

Don't remind me about the oldoldoldstable users

That sort of thing might be addressable though; eg. we could ask Debian to include the module by default and ask large services to upgrade

Debian doesn’t touch existing releases, except for very important security issues. ✏

modulo backports ✏

Which approximately nobody uses.

backports is what I was thinking

Appropriately nobody uses XMPP to begin with, so surely a lot of those use backports too! 😀

But yah, I have no idea how widespread debian is or how widespread backports is in there. May or may not be an issue.

Link Mauve, also, [citation needed]

Is anyone aware of any clients other than converse.js that *only* support Bookmarks v1.1 and not PEP Native or Private XML?

Movim used to do that, so its older versions.

I assume web stuff gets updated fast, so unless that's wide spread that's probably fine

I'm torn. I don't want to implement yet another thing just for one client, but I feel like web stuff is important to retain compatibility with

Tell that to Electron apps installed into /opt

Sam, my recommendation on modernxmpp was based on client support btw.

Sam, Converse is often combined with Prosody, which will soon have mod_bookmarks enabled.

*nods* I came to a similar conclusion. Although for other reasons I want to implement privatexml based stuff even less because I have basic pep/pubsub and it's somewhat re-usable, but don't have any private XML and it would require a lot more boilerplate work

So I stand by my recommendation in modernxmpp. :)

Maybe in a few decades we can fully deprecate Private XML. ✏

There was the idea of just translating it server-side to XEP-0223

Yay for a fourth storage method!

is pep native the bookmarks 2 stuff or is that yet something else?

Yes, it is that one.

It got renamed when it got made Stable IIRC.

still no dark mode for modern xmpp :(

nephele, what do you mean ?

moparisthebest, when the browser requests a dark theme, modernxmpp still serves light CSS.

patches welcome?

IIRC I already experimented once.

Or maybe it was for prosody.im?

badxmpp