Jose Celano

Relates to: https://github.com/torrust/torrust-index-gui/issues/660

> Suggestion: Improve the error message when the frontend can't connect to the backend in general for all requests. @mario-nt @da2ce7 @grmbyrn I think that's not a trivial task and...

I'm closing this because I don't see a good solution that improves what we have right now.

This should not have been closed. I've implemented only this https://github.com/torrust/torrust-index-gui/issues/469

> This should not have been closed. I've implemented only this #469 In the end, I was confused. It was this issue that one implemented in https://github.com/torrust/torrust-index-gui/issues/468

> @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). Yes, I think that was something (maybe) we lost when we migrated to Nuxt.

I'm organising user management issues on [this epic](https://github.com/torrust/torrust-index-gui/issues/657).

@fistwho can you provide a couple of situations where this can be helpful? For example: - To avoid SPAM if bot accounts are being created. - To limit the number...

Relates to: https://github.com/torrust/torrust-index-archive/issues/104

> @josecelano I'm recreating all the issues, etc, in planning to delete the `torrust-index` repo. So, are you planning to create user features in this repo, and then open new...