Jose Celano

ACK 0252f308183e8ea53988907e7553eda8952ebdc7

Finally, I decided to merge this PR at this point with: - Migration to Figment done. - A new feature. If you are OK with the default values, you can...

> @josecelano I think that the double-underscore is the natural choice :) Hi @da2ce7, I've extended the question from only "which separator to use" (it seems `__` is fine) to...

Relates to: https://github.com/torrust/torrust-tracker/pull/622#issue-2085940333 Hi @da2ce7 I wasn't sure if that is a good practice. I have the feeling we should move the client to another package and also primitives shared...

Hi, we can close it. @da2ce7 feel free to re-open it. I think this is related to https://github.com/torrust/torrust-tracker/issues/689. Maybe the solution is to extract an independent package.

Hi @ERR1R at the moment the tracker does not support uploading pre-existing keys. You must use the [tracker API](https://docs.rs/torrust-tracker/3.0.0-alpha.11/torrust_tracker/servers/apis/v1/context/auth_key/index.html) to create new keys for the torrust tracker. Besides, the [Torrust...

> well, if we change passkey for users then all seeding torrents for all users are invalid and have to be redownloaded! :-). > > i don't want to do...

Relates to: https://github.com/torrust/torrust-tracker/issues/773

This is already a new feature tracker [here](https://github.com/torrust/torrust-tracker/issues/773).

Hi @ERR1R, I've added a new endpoint [here](https://github.com/torrust/torrust-tracker/issues/974) to upload pre-generated keys.