Hi @dlaumen , thanks for getting in touch.

We always try to work with the vendors so I don't see any problem with merging this.

You have [email protected] in your identifier string.

Do you want the current version of rclone? This is in fs.Version eg v1.74.0-beta.9474.f8e1d74b9 or v1.73.0 which should be semver compliant (perhaps without the leading v)?

Thank you for the followup @ncw !

I didn't know how to dynamically get a version number, and for us it's currently mostly important to be able to distinguish official versus 3rd party clients.

I did just double-checked against our parser for this version, but unfortunately that won't work. It's apparently slightly stricter than what semver allows in regards to the pre-release identifiers, we only allow integers. We do support a +build

The regex for the whole version string:

/^(external-drive)+(-[a-z_]+)+@[0-9]+\.[0-9]+\.[0-9]+(\.[0-9]+)?-((stable|beta|RC|alpha)(([.-]?\d+)*)?)?([.-]?dev)?(\+.*)?$/i

So this could work: [email protected]+f8e1d74b9 or simply [email protected] or [email protected]. For us it doesn't matter that much how detailed you send a version number.

Am I also correct in assuming this app_version is configurable/overridable by the user?
We currently have some workarounds/exceptions in place on the API for rclone to avoid breaking changes on uploads, but if a user sets a custom app_version and we can no longer detect the request comes from rclone then the upload will fail. We will keep this exception in place for rclone until after the Proton Drive SDK is deemed stable and 3rd parties had a chance to implement it. So it might maybe be better if the user cannot override this and break uploads without knowing/understanding why?