Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conduct case review: ivirius.software #8

Closed
Arlodotexe opened this issue Jan 15, 2025 · 1 comment
Closed

Conduct case review: ivirius.software #8

Arlodotexe opened this issue Jan 15, 2025 · 1 comment
Assignees
Labels
areas::processes::conduct Code of conduct tasks::analysis::clarification Gathering partial or missing information tasks::review::compliance Alignment with standards or regulations

Comments

@Arlodotexe
Copy link
Member

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

  • Breaking the rules may result in an infraction.
  • When a strike or warning expires, all infractions are removed.
  • Infractions stack. If you had a Warning, you now have Strike 1, and so on.
  • Bypassing the infraction system or violating a rule shortly after joining will result in a ban.
  • Certain offenses can be pardoned or made more severe, at an Admin's discretion.

  • Warning - Lasts 2 weeks
  • Strike 1: 7 day mute, 21 day strike
  • Strike 2: 21 day mute, 63 day strike
  • Strike 3: 63 day mute, 189 day strike
  • Strike 4: 189 day mute, 567 day strike

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:

  1. A member breaks the rules immediately upon joining.
  2. A member purposely circumnavigates the infraction system.

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

Discord Name Discord Id
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.

@Arlodotexe Arlodotexe added areas::processes::conduct Code of conduct tasks::review::compliance Alignment with standards or regulations tasks::analysis::clarification Gathering partial or missing information labels Jan 15, 2025
@Arlodotexe Arlodotexe self-assigned this Jan 15, 2025
@Lamparter
Copy link
Member

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
areas::processes::conduct Code of conduct tasks::analysis::clarification Gathering partial or missing information tasks::review::compliance Alignment with standards or regulations
Projects
Status: Done
Development

No branches or pull requests

2 participants