You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 2, 2020. It is now read-only.
As it is it might be possible to mask a bad file as an .mp3, so we should be doing some sort of validation on the /play endpoint to verify what we're going to broadcast to the socket is valid.
How to actually validate that it is a valid MP3 or not is up in the air. And if we can get around it (headers? I'm not sure), we'd also want to avoid the time, and bandwidth, consuming part of it by not downloading the MP3 to the server running soundspaces.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As it is it might be possible to mask a bad file as an .mp3, so we should be doing some sort of validation on the /play endpoint to verify what we're going to broadcast to the socket is valid.
How to actually validate that it is a valid MP3 or not is up in the air. And if we can get around it (headers? I'm not sure), we'd also want to avoid the time, and bandwidth, consuming part of it by not downloading the MP3 to the server running soundspaces.
The text was updated successfully, but these errors were encountered: