Link MauveIf the user has no bookmarks2, but has both PEP and Private XML bookmarks and I want to unify them, what should I do?
Link MauveDoes it make sense to merge them?
KevServer or client?
Link MauveFor background: I’m working on Prosody’s mod_bookmarks2 which will expose XEP-0402 §5.3’s urn:xmpp:bookmarks:0#compat disco#info feature.
Link MauveThat is, will expose a Private XML interface to the bookmarks2.
Ge0rGKev: didn't you plan to require stricter interoperability inside of Bookmarks2?
KevBM2 isn't mine. That one's Dave's :)
Ge0rGI'm sorry very much
Link MauveWithout this module, a user could have three different bookmark stores: their Private XML bookmarks store, their PEP bookmarks store, and their PEP bookmarks2 store.
Link MauveMy current goal is to expose the first and the third ones as an unique store, and to forbid publishing to the second one.
Link MauveWhich, without XEP-0411 being exposed, shouldn’t be an issue for any client.
KevLink Mauve: I think it would be reasonable to merge everything server side. If you get in before there's existing data, it's obviously (to me) reasonable to merge. If there's extant data when you install the merging module, I guess you could argue there are issues with merging, but I think I still would.
Ge0rGaren't there clients that only support PEP bookmarks1?
Link MauveGe0rG, they should be accustomed to losing their data.
Ge0rGI'd say "upgrade all stores to bookmarks2", but then loading + unloading an experimental module will corrupt everything
Link MauveGe0rG, you can contribute the opposite transformation to mod_bookmarks.
Ge0rGLink Mauve: I'm not a server developer. Horrible things happen when I try.