Conduct case review: ivirius.software #8
Labels
areas::processes::conduct
Code of conduct
tasks::analysis::clarification
Gathering partial or missing information
tasks::review::compliance
Alignment with standards or regulations
Background
From https://discord.com/channels/725513575971684472/929868175762395146/1328414399844716637
A brief assessment of our infraction system
Posted on Discord in
#rules-and-info
:🛡️ Infraction policy
Server Companion#4732 is used to enforce our infraction policy, open source here:
https://github.com/WindowsAppCommunity/uwpcommunity-backend/blob/dev/src/bot/commands/infraction.ts#L267
We don't ban, except to combat bots and geniune malice, which usually manifest under specific conditions:
Ban context
Gauging from public chat messages, getting banned was seemingly the goal.
However, this member has a short established presense in the community, so the only ban-worthy thing they could have done was circumventing the infraction system, which they did.
We used the infraction system as normal. A warning was issued, then strikes were issued, and the member circumvented the infractions by leaving and rejoining, which led to a ban.
Screenshot of chat messages leading up to ban
Problem
As per the improvements in #7, this member's ban needs to be re-evaluated.
Solution: Conduct Case review
ivirius.software
637970525108436993
Can this member be unbanned?
Yes. This member has been banned for much longer than the duration of their original mute/strike. If we had the tooling to auto-track the ban side of our infraction system, it would have long expired by now.
The text was updated successfully, but these errors were encountered: