Cameron Garnham
Cameron Garnham
@josecelano This Pull Request is Ready for Review, however it needs some polish before merging. :)
needs impossible rebase, closed by #923
When a programmer looks at an API and sees `std::string`, he/she expects uft8 (or other text) encoded data. When a programmer looks at an API and sees `std::vector`, he/she expects...
@josecelano I think that we should have a set of "community" info dictionary schemas; some sort of whitelist format. In general if we find the format unofficial format somehow useful...
@josecelano noted that the [index backend already supports banning users](https://docs.rs/torrust-index-backend/latest/torrust_index_backend/web/api/v1/contexts/user/index.html#ban-a-user).
@WarmBeer suggested that we can have some option to enable an activation queue for new users; so that administrators can check user accounts before activating them.
@josecelano I'm recreating all the issues, etc, in planning to delete the `torrust-index` repo.
Yes. User Story Issues are Here. We can link relevant (back-end) issues from here.
Then we could call it: ```toml [registration.email] required = true verified = true ``` If this section is missing, emails addresses are not collected.
Option 3: Do not register the user until the email has been validated. 1. Ask the user to enter email. 2. Send email to user: a. Send registration link, if...