Ban a user through an endpoint.

[fernandez14]

Create a new endpoint that:

• Checks permissions to ban a user
• Performs the ban

[RodrigoCR]

How was ban done before? Can I get some context? Maybe I can work on this task.

[fernandez14]

How was ban done before? Can I get some context? Maybe I can work on this task.
@RodrigoCR ban was done by hand creating the field banned, banned_at in the user document hahahaha.

Well, now we still leverage those fields but we now use an endpoint and also we now have extended functionality through banning reasons. The banning reasons now tell the system how long a user will be banned based on custom logic from the config.hcl file, like this:

banReason spam {
    effects = <<JS
        var factor = banN || 1;
        exports = {
            duration: 60 * factor,
            ip: true,
        }
    JS
}

banReason spoofing {
    effects = <<JS
        var factor = banN || 1;
        exports = {
            duration: 60 * 24 * 7 * factor,
            ip: true,
        }
    JS
}