Skip to main content

Is there a good #Pleroma MRF policy for expiring old remote activities that are older than a given interval?
#pleroma
in reply to Sean Tilley

:twiz:
:twiz:
• •
I havent used it a lot but this sounds like a job for the ObjectAge Policy.
in reply to :twiz:

Sean Tilley
Sean Tilley
• •

Yeah, maybe. I was initially looking into Activity Expiration, but the wording is a little vague

Adds automatic expiration to all local activities


I only want to target activities that have a remote origin, not stuff that I’ve posted personally.

ObjectAge seems to target incoming posts?

in reply to Sean Tilley

Gidi Kroon
Gidi Kroon
•
@Sean Tilley I don't know the names from the top of my head, but there's a config setting and a mix task that you can put into crontab. It expires remote posts, but only the objects, not the activities. I use it. Last I heard (a while ago) they were thinking of removing this feature though.
@Sean Tilley
in reply to Gidi Kroon

Gidi Kroon
Gidi Kroon
•

@Sean Tilley In case it is still relevant:

It is the admin setting Remote post retention days under instance:

screenshot of the admin frontend showing the "Remote post retention days" setting, set to 31

then the prune_objects mix task as the pleroma user:

cd ~/pleroma/ && MIX_ENV=prod mix pleroma.database prune_objects

It seems I've scheduled this long ago and forgot about it by having the following in /etc/cron.d/pleroma:

SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

12 3 * * * pleroma { cd ~/pleroma && MIX_ENV=prod mix pleroma.database prune_objects && echo "Objects pruned" ; } 2>&1 | logger -t pleroma-cron
@Sean Tilley
⇧