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

Support Hitster #2258

Open
1 of 2 tasks
DwainZwerg opened this issue Jan 18, 2025 · 0 comments
Open
1 of 2 tasks

Support Hitster #2258

DwainZwerg opened this issue Jan 18, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@DwainZwerg
Copy link

DwainZwerg commented Jan 18, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Pain

Hitster is a music quiz in which you have to predict the year of release, the title and the artist of a particular song. There are certain cards with the correct solution printed on the back and a QR code on the front. This QR code is normally scanned by the Hitster app and then played using the Spotify app in the Hitster app (without displaying the year, title, cover, or artist; there is only a play/pause button and a button to stop playing the song). Due to the Spotify Shuffle function, it is now the case that you can only play the game properly with a Spotify Premium (because instead of the desired song, some other song is played); in addition, the use has never been privacy-friendly because you needed a Spotify account.

Suggested solution

The QR codes are all coded in the following scheme: http://www.hitstergame.com/de/00268 So a five-digit ID behind http://www.hitstergame.com/de/. I would create a mapping that assigns each Hitster ID to its matching Spotify song (as a URL or whatever you need (or YouTube Music)). For the client, I envision the following solutions:

  1. spotube registers on Android http://www.hitstergame.com/de/ as a supported link. A user uses the Android QR code scanner to get the URL, which is then opened in Spotube. Spotube plays the correct song from the invidious instance selected in the Spotube settings in another newly written player (which only has the play/pause button and a “cancel” button) according to the mapping. Advantages: No QR code reader needs to be integrated into Spotube and Spotube does not need camera permission. Disadvantage: You have to write a new player into the already functioning app. You have to rely on the supported link feature of Android to work properly.
  2. A new Hitster mode will be integrated into Spotube: A QR code scanner is integrated so that the link is already captured by Spotube itself. The new player then plays the song corresponding to the mapping. Advantage: You don't have to rely on Android's supported link feature working as intended. Disadvantages: Spotube requires camera permission and a QR code reader and a new player must be integrated into Spotube.
  3. You write a small app “Hitster FOSS”, which has integrated the mapping, the QR code reader and the rudimentary player and retrieves the correct title from Spotube via an API (this is how the interaction between Hitster and Spotify works).
  4. You write a small app “Hitster FOSS”, which contains the mapping, the QR code reader, this rudimentary player and the retrieval algorithm of the Spotify songs from invidious.

Useful resources

The linked links

Additional information

I would really appreciate it if you would take on this feature request.

Self grab

  • I'm ready to work on this issue!
@DwainZwerg DwainZwerg added the enhancement New feature or request label Jan 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

1 participant