Error messages should be sent as a list of all errors. Eg.

{
    'route': 'auth.authenticate',
    'receipt': <variable Receipt ID>, // Receipt ID, if one was supplied on request
    'error': true,
    'data': {
        'error_code': <int Error code>,
        'error_messages': {
            {'error_field': <str fieldname, optional>, 'error_message': <str Error message, mandatory>},
            { ... },
         }
    }
}

error_message should contain the error message. If error_field is set, this error will be field specific. If not, it is a generic operation error.

Operations should be namespaced. Eg. auth.get_profile and auth.update_profile to auth.profile.get and auth.profile.update.

We should have two endpoints for each data update/create function. Eg, auth.register.validate and auth.register.apply. First one only validates input and outputs errors if necessary, the second one does validation and data saving to database if success. This allows on-the-fly data validation when user is inputting data to forms.

The forum front-end could use a way to fetch a single board by id and get both board information and users/threads (like what the 'forum.get_threads' route already does).

Without something like this, the forum needs to fetch all boards and then store them somewhere for single-board thread listing views. This doesn't fit into the application's structure very well when the board is used as a top-level React Router view component.

Socket server can get stuck and go to a state where it cannot be stopped if MQ server does not respond. Needs to get fixed.

Eg. Cerberus @ http://docs.python-cerberus.org/en/stable/usage.html