MSC3911: Linked media #131
Draft
Conversation
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
…etrieval of media restrictions
… a media restriction
…tach restricted m.room.avatar media
…g media when restricted (#96)
…having to be a media worker. This created an http replication endpoint on the media worker, and it will now need a replication listener declared in its configuration file. Make sure to add the worker to the `instance_map`, and it is going to be best practice going forward to use a new list `media_repo_instances` to name each worker that can have that replication listener.
This particular function is not particularly usable when early in a room and applying a filter for events that do not exist yet
…espect to media restriction
…over-able reason (#129)
…dling of missing state (#126)
…rs with respect to media restriction (#128)
…system when doing a copy
…system when doing a copy (#137)
Related: famedly/product-management#3448 Be more selective about what avatar url's are allowed to be set to the profile of a given user. Particularly around remote media, but any media that is suddenly "missing" could have this error. Enhance the pre-flight validation to ensure that the media exists, with selective conditions during the transition away from unrestricted media to either ignore the error or forbid the operation. Gracefully handle updating membership events during a profile avatar change propagation. Most of the potential errors that can be raised here should now be blocked by the pre-flight validation when setting the profile. Additionally, outgoing remote invites and room creator join membership events conditionally drop the avatar url if the media does not exist and legacy unrestricted media is disabled
…rs needing additional configuration
…ing github actions Somehow, PyO3 version 0.24.1 is being used which only has support for Python <= 3.13 even though the version pinned in Cargo.toml is 0.25.1. It is unknown where exactly this version of PyO3 is coming from, but caching oddities are suspected Revert this after Synapse is overall bumped to Python 3.14 in v1.142.0
Lot of things going on here: 1. Enable the new `media_repo_instances` list for media workers 2. Add the new test package directory in Complement 3. Turn on `msc3911_enabled` 4. Make sure to route to workers when that mode is enabled There is an additional temporary commit to be removed before merging. It exists to override the branch name of Complement to pull for testing. Once this is merged it should automatically allow the Synapse branch of `msc3911` to target `msc3911` branch on the Complement repo. Other branches/PRs should pull from the `main` branch, unless there exists a branch of exactly the same name on both repos. E.g. if my PR has the branch name `jason/cool-fixes` it will search for that exact same branch name on Complement before falling back to `main`
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.
Implements matrix-org/matrix-spec-proposals#3911 with some minor changes: