Skip to content
New issue

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

Stop Spamming Azuracast's API to see if the song changed. #1

Open
45ninjas opened this issue Jun 17, 2023 · 0 comments
Open

Stop Spamming Azuracast's API to see if the song changed. #1

45ninjas opened this issue Jun 17, 2023 · 0 comments

Comments

@45ninjas
Copy link
Contributor

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant