{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}

Speaking of vacuuming, the upcoming version of Mastodon will provide admins with the option to define a content retention policy that will evict all remote posts past a defined date. A harsh, but most effective way to keep the database (and by extension, media cache) to a constant size, as far as activity by local users allows.

8
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
oshy

@Gargron Hell yeah this is a great feature to add!!!!!!

0
2y
정아름 ⠜⠿⠕

@Gargron If I set retention policy for remote posts, What could happen to users' fav/boost/bookmark?
undo and gone? or just delete from local DB without undoing fav/boost/bookmark?

0
2y
Baloo Uriza

@Gargron Would be extra-cool if this could be done just to accounts that have no followers locally.

0
2y

@Gargron Preferences -> ☑ Automatically delete old posts

0
2y
:debian: 𝚜𝚎𝚕𝚎𝚊 :trisquel:

@Gargron

Finally! :D

0
2y
𝓻𝓻𝓪

@Gargron omg it is finally happening

0
2y
Muntasm Ul Haque

@Gargron what does it mean for the end users? Would their old posts get deleted after a specific time?

1
2y
Teknikal_Domain

@Gargron this makes me wonder two things:

  1. If some activity past that date is referenced again (say, boosted), or is specifically requested by a user (say, by URL), would it be fetched and stored again? Or does that mean an instance with that enabled will not work with anything beyond that date
  2. As long as we're talking about sizes, is there any way to deal with cached account headers? That seems to be the biggest folder here by far, nothing I know in tootctl touches it.
0
2y
Replies