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
The endpoint we're using from Azuracast API tells us the following:
When the current song will finish.
The next song.
Why not wait until the current song finishes then update the UI with the next song. Then wait a little bit before spamming that endpoint.
Maybe there's some data we can use to make each client attack the endpoint at different times. Could we use "random-range-0-1 * length-of-song" to decide when to attack next?
The text was updated successfully, but these errors were encountered:
The endpoint we're using from Azuracast API tells us the following:
Why not wait until the current song finishes then update the UI with the next song. Then wait a little bit before spamming that endpoint.
Maybe there's some data we can use to make each client attack the endpoint at different times. Could we use "random-range-0-1 * length-of-song" to decide when to attack next?
The text was updated successfully, but these errors were encountered: