Repository navigation
[Inline parity 6/6] Bound media transfers and preserve fidelity - #6
Closed
salmonumbrella wants to merge 17 commits into
Closed
salmonumbrella wants to merge 17 commits into
salmonumbrella wants to merge 17 commits into
Conversation
salmonumbrella
force-pushed
the
feat/inline-parity-media
branch
from
November 8, 2026 16:24
6742fa2 to
d4f6564
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why
The framework file helper could spool an entire response before the bridge checked its size. Audio/video metadata and upload echoes also need honest fallbacks rather than unsupported native claims.
Usage
Existing media paths apply the limits automatically. Outgoing audio uses a file fallback; native video needs valid dimension/duration metadata. Unknown Matrix backends without a proven bounded transport fail explicitly. Dedicated sticker/GIF semantics are not advertised.
Stacks on #5 (and its preceding dependencies).
Refs #1.