I will be starting the upgrade to Mastodon v3.2.0 for all instances hosted on Masto.host
There will be a downtime of about 30 seconds during the upgrade.
You can read the release notes here: https://github.com/tootsuite/mastodon/releases/tag/v3.2.0
PS: ♥️ the new audio player
All instances hosted on Masto.host are now running Mastodon v3.2.0
Any issues please let me know.
@mastohost Hey there! I'm getting CORS errors when trying to play MP3s within the webclient.
This person was talking about the issue:
And here's an example that's not working on the ✨Plush✨ City webclient:
@mawr That's so strange, it is working for me.
What browser/OS are you using?
Can you send me the console log?
I think it might be due to the fact we're using our own AWS S3 instance-- do I need to add headers there?
OS X 10.14.6, FireFox 78.0.2.
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://s3-us-west-2.amazonaws.com/plushcity/cache/media_attachments/files/104/592/230/316/898/303/original/acac639ac654a3e6.mp3. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
Uncaught (in promise) DOMException: The media resource indicated by the src attribute or assigned media provider object was not suitable.
@mastohost I had just found that in the S3 documentation and have added CORS headers but they don't seem to be working. Still troubleshooting
@mastohost I had missed that GET was not included in the default permissions for example1.com in the S3 example documentation. I'd assumed it was after seeing PUT, POST, and DELETE. Because I'd defined plush.city specifically, it was overriding the secondary rule that allowed all domains to GET.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!