jdev - 2021-02-20

Hi i need email password data

so about pep, say someone publishes something over pep, for example avatar or nickname

and i cache that info so i can show it before i connect to the server

if the contact deleted his node, im stuck forever wth the data

there is nothing that informs me that the node was deleted, if i was offline at the time of deletion

question is, should i care?

Some of the PEP XEPs talk about publishing a mostly empty payload to remove stuff.

basically every pep xep says if you want the data to be deleted, you need to publish empty info, not delete the node

.

I've thought about implementing https://xmpp.org/extensions/xep-0312.html to help with that.

The minimum subset of PubSub features needed for PEP doesn't include node deletion (or creation for that matter)

Or

i think i just dont care, and offer some kind of cache reset button

https://xmpp.org/extensions/xep-0163.html#defaults

It does

lovetox: Could roll a dice and have some expiry time.

i thought about that

i think i add the timestamp, can be useful and i can do some expiry magic

What if, when connecting and going online and fetching all the cached items, you mark those as expired. If a new PEP notification comes in, that replaces the previously cached thing. Then next time, ignore those marked as expired.

but i dont fetch all the items, i only fetch what i currently need and display

also sound inefficient

bascially if i have a table with 1000 rows, you say i should update all 1000 with "expired"

Could do it by having a generation number, that increases every time restart / reconnect or something

i dont see the benefit over just storing the last received timestamp

So first time you start, generation=1, anything you receive is saved with generation=1. You reboot. generation=2. anyting in the database with generation>=1 is used as cache, purge generation<0. etc.

hm, there is so much pep data

And when does anyone except me delete nodes anyway?

Is that a common thing?

i dont think so whats more common is that someone uses a client that supports UserTune

then switches client which does not support it

from now on the tune is stuck forever

thats why i want you to implement pubsub expiry feature :)

:)

there are some pep xep where the data is simply not useful > 24 hours

We need an internal cron of some sort to keep track of all the time based expiry things we have now. MAM, HTTP upload, now this.

lovetox: The above is sorta like generational garbage collection, and based on that things should become stale once you go offline. So if you go offline then anything you have stored is stale, until you go online and it gets (maybe) refreshed.