We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It would be a massive efficiency to deploy MSC3860 to this storage provider to allow storage to be served directly from S3 servers.
I would see it sending a s3 get_presigned_url() of a media file to the client to keep S3 server closed from public.
The text was updated successfully, but these errors were encountered:
I agree that this would be a useful feature to support. 👍
Sorry, something went wrong.
No disagreements from the Synapse team. We're not going to prioritise it, but would gladly review a PR.
No branches or pull requests
It would be a massive efficiency to deploy MSC3860 to this storage provider to allow storage to be served directly from S3 servers.
I would see it sending a s3 get_presigned_url() of a media file to the client to keep S3 server closed from public.
The text was updated successfully, but these errors were encountered: