Index bans

[qimiko]

index bans. i didn't really test this besides making sure it compiled :p

a ban blocks developers from

• creating mod versions
• uploading mods
• adding devs to a mod
• being added as a dev to a mod

it does not do anything else (like unlisting/deleting all existing mods).

ban status is not visible to anyone besides index admins, unless they attempt to add that developer as a developer to a mod, which would be a very silly idea. ban reason is made public when a banned user tries to perform a blocked action. everything else is only visible to index admins

[RayDeeUx]

"SiX sEvEn" yes we all get it please just find a new joke to beat to death

[Fleeym]

I think it would be useful if bans had a revoked_at timestamp, that way we have a history of bans for a user. Also could be used for temporary bans that get revoked automatically.

[qimiko]

can add, although does that mean that bans shouldn't be using dev id as the primary key? (so that one dev can have multiple bans). and then i can have /bans return a list of bans instead of one ban and probably also redo the delete endpoint to support that

[Fleeym]

Yeah, that's gonna need a bit of refactoring. Delete endpoint should just set revoked_at = now, basically never delete a ban row.

[Fleeym]

Another thing - if I manage to merge submission threads bans should also lock the developer from commenting on threads.