[Self-Hosted] State of Media Expiry Setting Does Not Retroactively Affect Pre-Existing Media

(#672) Bug Closed: Fixed self-hosting

Summary

The Media Expiry setting only affects media at the time it is uploaded. If an instance admin changes this setting, previously uploaded media is not affected and only newly uploaded media uses the updated expiry setting. I would expect changes to this setting to also apply retroactively, such that existing media would also observe the updated expiry setting for such an event when an instance’s data storage capacity conditions change. For example, if an instance owner is running out of space, they would probably want pre-existing media to have an expiry date applied to make room; inversely if an instance owner upgraded their storage capacity, they may no longer see the need to have expiry applied for pre-existing media.

Steps to reproduce

If media expiry is already enabled:
  1. Upload an attachment in a text chat/channel.
  2. Go to Configuration > Instance Config > Media & retention and uncheck "Enable attachment expiry" in the admin panel.
  3. Fully restart docker compose stack.
  4. Go back to the attachment that was uploaded in step 1; it will still have an expiry date applied.
If media expiry is already disabled:
  1. Upload an attachment in a text chat/channel
  2. Go to Configuration > Instance Config > Media & retention and check "Enable attachment expiry" in the admin panel.
  3. Fully restart docker compose stack.
  4. Go back to the attachment that was uploaded in step 1; it will have no expiry date applied.

Environment

Version: Latest Self-Hosted as of the time of documenting this bug. Server OS: Debian 13.5 Client Browser: Fluxer PWA in Flatpak Brave Browser Device: Computer
  1. Falco changed the status from Awaiting confirmation to Fixed
  1. The pull request fluxer#1182 mentions this post Closed
  2. The pull request fluxer#1182 was closed without merging Closed

3 comments

Sign in with Fluxer to comment and vote.
Comment by Rex
RexSystem 1 vote
Status changed from Needs triage to Awaiting confirmation
Fixed in the self-hosted api 2026.1011.113345: changing attachment expiry now also applies to files uploaded earlier. This applies to self-hosted instances only.
Deleted comment
Removed by moderator Rex: Removed a general status note that was posted on many GitHub threads. It no longer applies here.
Comment by Falco
Falco OP1 vote Fixed for me
This is confirmed to be fixed on Fluxer API 2026.1011.125745 Enabling media expiry applies an expiration date for all media based upon the date of upload. Disabling media expiry removes expiration dates for all uploaded media on the server.