Email verification? #2

New issue

Closed

opened 2024-11-24 20:40:18 +00:00 by nex · 2 comments

nex commented

2024-11-24 20:40:18 +00:00

(Migrated from git.gay)

Email verification for LBU would be nice, but there needs to be a plan to migrate the old bot to this one

nex commented

2024-11-27 19:33:17 +00:00

(Migrated from git.gay)

The way this is going to work is as follows:

User joins the server
User presses "Verify my email" button in the verify channel
User enters their email, it is validated and checked to be a student.leedsbeckett.ac.uk email
3.1. staff emails are a special case and told to contact the committee directory
User is sent a random 12-character code (6 bytes)
User inputs this code, or presses the "input code" button if they closed the modal
User is given verified role and email is set to verified in the database.

This differs from the current method which uses an explicit deny role in order to deny access. This new system won't use that, and relies on @everyone not having access by default.

The way this is going to work is as follows: 1. User joins the server 2. User presses "Verify my email" button in the verify channel 3. User enters their email, it is validated and checked to be a student.leedsbeckett.ac.uk email 3.1. staff emails are a special case and told to contact the committee directory 4. User is sent a random 12-character code (6 bytes) 5. User inputs this code, or presses the "input code" button if they closed the modal 6. User is given verified role and email is set to verified in the database. This differs from the current method which uses an explicit deny role in order to deny access. This new system won't use that, and relies on @everyone not having access by default.

nex commented

2024-12-02 13:16:27 +00:00

(Migrated from git.gay)

Now in v2