Skip to content

3.2.0.0

Choose a tag to compare

View all tags
@DerekYang2 DerekYang2 released this 09 Nov 03:49
· 104 commits to master since this release
3.2.0.0
2a89bb2
This commit was signed with the committer’s verified signature.
DerekYang2 Derek Yang
GPG key ID: B778651AE27D128F
Verified
Learn about vigilant mode.

Changes mostly Qobuz related (app id/secret, email setting encryption), with the addition of a loading splash screen.

Change List

  • Allow user to enter a fixed Qobuz App Id and Secret. Leaving blank will just assume the current player App Id and Secret.
  • Fix encryption for storing email/password for Qobuz using Windows DPAPI.
  • Added splash screen. Takes a few seconds to authenticate into the streaming services. Before, qobuz could still be loading up in the background even when the search page appeared. Now, everything is guaranteed to be authenticated when search appears.
  • Save button in Settings now shows error when Qobuz app secret and app ID are invalid.

Download FluentDL_3.2.0.0.zip below.
Download FluentDL_3.2.0.0_arm64.zip for ARM-based systems (untested).

See installation wiki for installation details and videos.

See README authentication section for authentication details.

Additional Notes

Qobuz App Id and Secret

Every id and token (your user account) is tied to an app id and secret (qobuz web player values).

However, the web player changes app id/secret every once in a while. This changes the id/token for all users. Before this release, you would need to go back into the browser to get your new id/token values.

To get around this, you can now save an app id/secret alongside your id/token. Now, even if the app id/secret changes, your old id/token remains working with the old app id/secret that you saved.

TLDR: If you don't want to manually get id/token values every once in a while, press Capture Current App ID/Secret on the same day you get your id/token from the browser. If you have id/token values from elsewhere, you will need to know their corresponding app id/secret. Finally, remember to hit save.

Qobuz Password Field

The encrypt/decrypt is now unique for each windows user. If an attacker found the saved settings text and that was all they had, they would be unable to decrypt it without your windows password. There are a few other ways around DPAPI, and its security is discussed here. If you wish to 100% guarantee the safety of the email/password (i.e. important account), id/token option is always available or clear that setting after usage.

Assets 4
Loading