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.
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.
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.
Dan
on
I fully agree with mt and Benjamin as I have the same use cases with OMEMO and Movim.
Zash
on
Changes
tags Status-Started
Gyulavitez
on
I'm endorsing and waiting for it very much. Thank you, for doing this.
jh
on
Can one already test the new module? Are the OMEMO-KEYS also stored or leave active if the server restarts?
Stephen Paul Weber
on
This affects PubSub nodes as well, not just PEP. Would a solution for one apply for both, likely?
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.
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.
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'/>
ChangesType-DefectType-Enhancement Milestone-0.10 Status-AcceptedNot going to block the release, pushing to next.
ChangesI'd like to vote for an inclusion in the 0.10 release as it would greatly benefit the omemo and conversations avatar handling experience.
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.
I fully agree with mt and Benjamin as I have the same use cases with OMEMO and Movim.
I'm endorsing and waiting for it very much. Thank you, for doing this.
Can one already test the new module? Are the OMEMO-KEYS also stored or leave active if the server restarts?
This affects PubSub nodes as well, not just PEP. Would a solution for one apply for both, likely?
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.
https://github.com/omemo/gajim-omemo/issues/152
The work was actually for our generic pubsub code and won't apply to mod_pep. However mod_pep_plus, which might replace mod_pep at some point
PEP with permanent storage is now in mod_pep_plus and should be working. Thanks to Link Mauve!
Changes[mod_pep] Permanent data storage[PEP] Permanent data storageMattJZashGreat, thanks for the work! Is this feature usable with 0.10?
It is not supported with 0.10.