Discord Verification
Overview
Discord verification is implemented to ensure all of the following:
All members of the team are students at the University of Waterloo
This is a condition of joining WARG
See Bootcamper Onboarding for more details
Spammers, advertisers, and automated Discord accounts are unable to cause disruption
Access to the Discord server’s public channels is automatically granted upon verification.
Please read this document before asking any questions. If you still have questions after, feel free to ask the subteam leads or directors.
Automatic Verification
The Verified role is granted through a Discord bot, currently Sir Goose.
To be automatically verified, type: /verify
or $verify
and follow the instructions.
Sir Goose does not have access to your UW password
Sir Goose privacy policy: https://github.com/sunny-zuo/sir-goose-bot/blob/master/src/interactions/button/verificationLearnMore.ts
The Discord bot may be changed in the future as Sir Goose is currently maintained by a UW student.
Manual Verification
The Verified Manual role may be granted for any of the following reasons:
Verification is not possible for a technical reason
UW student/alumni is not comfortable giving information to the Discord bot
External advisor
Person affiliated with the competition in which WARG is participating
Other reason approved by a director
To be manually verified:
Ping one of the subteam leads or directors with a request to be manually verified
State whether you would like to verify in-person (step 2) or online (step 3)
If there is no response after a day, ping a different subteam lead or director
In-person:
Arrange for a time to meet with a subteam lead or director at the WARG bay
Show your WatCard and Discord username
The subteam lead or director adds your Discord username to the manual verification tracking table and assigns the Verified Manual role
Online:
The subteam lead or director confirms they are expecting your email within the next few days
Send an email to uwarg@uwaterloo.ca from your UW email address with:
Subject:
Discord Manual Verification
Body:
I would like [Discord username] to be manually verified by [lead name]
The subteam lead or director adds your Discord username to the manual verification tracking table and assigns the Verified Manual role
Manual Verification Tracking Table
No real names are stored here.
For subteam leads and directors:
Mechanism: One of the following:
In-person
Online (include link to specific email)
Approver: Name of the subteam lead or director who approved
Date: Last updated
Reason and Current Status: Reason can be the same as current status
Discord Username | Mechanism | Approver | Date | Reason and Current Status |
---|---|---|---|---|
warg-equipment#1242 | In-person | Daniel Puratich | 2023-05-29 | WARG equipment |
kevths#2134 | In-person | Daniel Puratich | 2023-05-29 | Alumni and Advisor (Past EE Lead) |
Shrinjay#4691 | In-person | Daniel Puratich | 2023-05-29 | Alumni and Advisor (Past Director) |
Chief_Engineer#7597 | In-person | Daniel Puratich | 2023-05-29 | Alumni and Advisor |
HulaParade#5631 | In-person | Daniel Puratich | 2023-05-29 | Faculty Advisor |
sillyspacecadet#1979 | In-person | Daniel Puratich | 2023-05-29 | Alumni and Advisor |
Frank123#4084 | In-person | Daniel Puratich (Sahil Kale) | 2023-05-29 | Previously allowed advisor |
Rainer_Walter#6029 | In-person | Daniel Puratich | 2023-05-29 | Operations Advisor (Past Operations lead) |
WanTron#2540 | In-person | Daniel Puratich | 2023-05-29 | EE Advisor (Industry professional who has helped the team with hardware and advise in the past!) |
brielle.c#6454 | In-person | Daniel Puratich | 2023-05-29 | Mech Advisor (Past Mech Member) |
carno#7926 | In-person | Daniel Puratich | 2023-05-29 | Mech Advisor (Past Mech Member) |
mattviss1#6240 | In-person | Daniel Puratich | 2023-05-29 | Mech Advisor (Past Mech Member) |
Chris Hajduk#1195 | In-person | Daniel Puratich (Sahil Kale) | 2023-05-29 | Previously allowed Alumni |
serge#0090 | In-person | Daniel Puratich (Sahil Kale) | 2023-05-29 | Previously allowed Alumni |
ianjfrosst#9844 | In-person | Daniel Puratich (Sahil Kale) | 2023-05-29 | Previously allowed Alumni |
cindy#8322 | In-person | Daniel Puratich | 2023-05-29 | Mech Alumni (Past Mech Member) |
chris.shum#4406 | In-person | Daniel Puratich (Sahil Kale) | 2023-05-29 | Previously allowed Advisor |
Amin Oji#2991 | In-person | Daniel Puratich (Sahil Kale) | 2023-05-29 | Previously allowed Advisor |
Xierumeng#7022 Â | In-person | Daniel Puratich | 2023-05-29 | Autonomy Advisor and Alumni |
segfault_11#2547 | In-person | Daniel Puratich | 2023-05-29 | Past firmware (EFS) lead |
antenna#3335 | Daniel Puratich | 2023-05-29 | UW student | |
UltraRay17 | In-person | Alison Thompson | 2023-08-15 | UW student (Master’s) |
ac5231 | Anthony Luo | 2024-01-18 | UW Student | |
simone27227 | Online | Daniel Puratich | 2024-09-15 | UW Student |
 |  |  |  |  |
 |  |  |  |  |
 |  |  |  |  |
 |  |  |  |  |
Add more rows if required | Â | Â | Â | Â |
Revocation
Verification may be revoked by a subteam lead or director if the user is hacked or other similar cases. Revocation is recorded in the leads channel.
If your verification has been revoked, please contact a subteam lead or director to restore verification.
Â