[Feature Request]: Use new clientData API to persist data

[the0neWhoKnocks]

Description

Currently a separate server is required to persist theme data across browsers/devices. Once it's been released, this should be handled via the new clientData API. I'm just creating this issue to surface the new functionality and remove the extra server as a dependency.

Describe the solution you'd like

Once it's released, start using the new clientData API to persist data.

This PR shows how they're using the new functionality.

Describe alternatives you've considered

No response

Complementary informations

• Is this feature already implemented in the default WebUI?

[Larsluph]

That's awesome, thanks for the notice!
However this may be more complex to handle as we still support backward compatibility with older versions of qBittorrent, so we'll still need some kind of fallback.

[the0neWhoKnocks]

@Larsluph Hm, I'd probably create a config.js util. Build out the util with your current get/set logic for UI data. Then add a switch to verify window?.parent?.qBittorrent?.ClientData exists. If it does, use the new API, profit.

Bummer you wouldn't be able to drop the extra server support... unless you're willing to draw a line and say you'll no longer support the server after release of version X.