chore: remove /confirm and references to Unconfirmed role
#26
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To help facilitate in migrating unconfirmed pre-onboarding users to use the new onboarding feature once they join.
Provides information to the kicked user as to why they were kicked and how to rejoin. The kicked user is not gauranteed to get the DM; they have the option to reject all DMs from specific servers.
Uses existing Confirm view to simpify code flow.
9 tasks
Keeps consistency in formatting with other notices that Pi-Bot sends to the user.
Nydauron
force-pushed
the
chore/remove-confirmation
branch
from
82d1847 to
de4aabd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Removes
/confirmand adds a cleanup command/cleanup unconfirmedto kick unconfirmed users (i.e. users without the Member role). This is to remove the obsolete manual confirmation system the server has had since its inception in 2020.Why kick Unconfirmed members?
While users can go to "Channels & Roles," they will still have the Unconfirmed role if they do not leave the server. An easy way would be to delete the Unconfirmed role (fixed via baed1b2)
They can take the initiative to do it themselves. Otherwise, kicking them and having them rejoin forces them into the onboarding pipeline, and if they don't end up rejoining, oh well, they were dead weight anyway to the member count.
How to communicate this to users?
Make #welcome read-only and clear all messages. Replace the top message with an
@everyoneannouncement that includes instructions to either go to "Channels & Roles" or rejoin the server to complete the onboarding survey.This announcement should be sent to #welcome to
@everyoneon 2025-09-01. We can set a hard deadline of 2025-09-15 before we kick and remove channel access on 2025-09-16 PDT.Checks
blackover the code to ensure formatting.Important Info
pipdependencies.Issues Closed
My pull request closes the following issues:
N/A
Thank You
Thank you for your contribution to Scioly.org! This pull request will be reviewed
in a promptly manner. If not done, please feel free to contact @cbrxyz.