jdev - 2019-11-13

  1. Link Mauve

    If the user has no bookmarks2, but has both PEP and Private XML bookmarks and I want to unify them, what should I do?

  2. Link Mauve

    Does it make sense to merge them?

  3. Kev

    Server or client?

  4. Ge0rG


  5. Link Mauve

    For 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.

  6. Link Mauve

    That is, will expose a Private XML interface to the bookmarks2.

  7. Ge0rG

    Kev: didn't you plan to require stricter interoperability inside of Bookmarks2?

  8. Kev

    BM2 isn't mine. That one's Dave's :)

  9. Ge0rG


  10. Ge0rG

    I'm sorry very much

  11. Link Mauve

    Without this module, a user could have three different bookmark stores: their Private XML bookmarks store, their PEP bookmarks store, and their PEP bookmarks2 store.

  12. Link Mauve

    My current goal is to expose the first and the third ones as an unique store, and to forbid publishing to the second one.

  13. Link Mauve

    Which, without XEP-0411 being exposed, shouldn’t be an issue for any client.

  14. Kev

    Link 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.

  15. Ge0rG

    aren't there clients that only support PEP bookmarks1?

  16. Link Mauve

    Ge0rG, they should be accustomed to losing their data.

  17. Ge0rG

    I'd say "upgrade all stores to bookmarks2", but then loading + unloading an experimental module will corrupt everything

  18. Link Mauve

    Ge0rG, you can contribute the opposite transformation to mod_bookmarks.

  19. Ge0rG

    Link Mauve: I'm not a server developer. Horrible things happen when I try.