#485 [mod_pep] Permanent data storage

Reporter Ge0rG
Owner MattJ
Created
Updated
Stars ★★★★★ (10)  
Tags
  • Milestone-0.11
  • Type-Enhancement
  • Status-Started
  • Priority-Medium
  1. Ge0rG on

    Some applications rely on permanent storage of PEP data, i.e. XEP-0223 for bookmarks. Prosody only stores PEP data in memory, and it is lost whenever the server is restarted. Keeping bookmarks (and maybe other client-generated state) across restarts would be desirable.

  2. MattJ on

    Yes, we're working on this. Meanwhile though, clients shouldn't be using it as permanent storage unless the server advertises: <feature var='http://jabber.org/protocol/pubsub#persistent-items'/>

    Changes
    • owner MattJ
    • title [mod_pep] Permanent data storage
    • tags Type-Defect Type-Enhancement Milestone-0.10 Status-Accepted
  3. MattJ on

    Not going to block the release, pushing to next.

    Changes
    • tags Milestone-0.11
  4. mt on

    I'd like to vote for an inclusion in the 0.10 release as it would greatly benefit the omemo and conversations avatar handling experience.

  5. Benjamin Renard on

    The inclusion of this feature in the 0.10 release would be awesome. The feature gap is a real problem for integration with new software like Movim.

  6. Dan on

    I fully agree with mt and Benjamin as I have the same use cases with OMEMO and Movim.

  7. Zash on

    Changes
    • tags Status-Started
  8. Gyulavitez on

    I'm endorsing and waiting for it very much. Thank you, for doing this.

  9. jh on

    Can one already test the new module? Are the OMEMO-KEYS also stored or leave active if the server restarts?

  10. Stephen Paul Weber on

    This affects PubSub nodes as well, not just PEP. Would a solution for one apply for both, likely?

  11. jh on

    So far I know the pep function is no module firmly separate in the server integrated. So a permanent memory is also something basic. However, I XMPP standards also know a lot me not at the lying ends.

  12. jh on

    https://github.com/omemo/gajim-omemo/issues/152

New comment