What feature do you want?
A configuration option to ignore XMA attachments (especially Instagram/Facebook reels or stories) so no media is stored in matrix room, just keeping the link to reach it .
Why is it needed?
Currently, disable_xma_backfill and disable_xma_always only prevent the bridge from making additional Instagram API calls to fetch the full-quality version of shared XMA posts. They do not prevent the minimal preview/inline XMA part from being included. This means that in all cases, some kind of media (like a preview, thumbnail, or Instagram link) is still bridged to Matrix rooms and server usage space grows.
Proposed solution
- New config option (e.g.,
suppress_xma: true), or extending the existing disable_xma flags to support completely ignoring XMA.
- When set, any message part containing an XMA attachment (or matching certain types: reels/stories/profile shares) isn't bridged at all, only providing the link to the original reel/story/etc.
Alternatives
- The current flags (
disable_xma_backfill, disable_xma_always) provide only partial suppression.
What feature do you want?
A configuration option to ignore XMA attachments (especially Instagram/Facebook reels or stories) so no media is stored in matrix room, just keeping the link to reach it .
Why is it needed?
Currently,
disable_xma_backfillanddisable_xma_alwaysonly prevent the bridge from making additional Instagram API calls to fetch the full-quality version of shared XMA posts. They do not prevent the minimal preview/inline XMA part from being included. This means that in all cases, some kind of media (like a preview, thumbnail, or Instagram link) is still bridged to Matrix rooms and server usage space grows.Proposed solution
suppress_xma: true), or extending the existing disable_xma flags to support completely ignoring XMA.Alternatives
disable_xma_backfill,disable_xma_always) provide only partial suppression.