dietrichm / admirer Goto Github PK

Currently syncing works on the last x amount of loved tracks on the source service. However for a lot of use cases it would be easier to sync tracks since the previous sync.

As both Last.fm and Spotify keep a datetime a track was added, we could run a sync for tracks up to the last synced track, given we save said datetime in a persistent state.

Set synchronization options in a config file, avoiding passing source/target service names, limits and datetimes as command line options for every sync.

ListenBrainz has a notion of loved and hated tracks used for recommendations.

Various errors (depending on the service) are being returned when using list or sync before logging in.

Build binaries for Linux and others.

Check what needs to happen for Windows. Configuration directory path will need fixing:

https://github.com/dietrichm/admirer/blob/main/infrastructure/config/loader.go#L21

Every OAuth2 authentication flow redirects to the non existing https://admirer.test.

Let's complete the flow by spinning up a HTTP server on a random port and let the browser redirect back there, so Admirer picks up the OAuth2 token automatically.

Thinking of building a separate web-based front-end, Admirer should or could expose its functionality currently available through CLI commands over a small HTTP API.

The sync command is the most important feature of this tool.

Given a limited number of recently loved tracks on one service, query and mark as loved the same tracks on another service.

Synchronization should work in any direction.

Currently, the API client and secret have to be set in environment variables. This is not the most user friendly approach.

Better would be to query for the ID and secret during the service login flow, and read/write both values from/to the existing secrets file.

Store service secrets in the operating system's keychain.