Integrating w3os discord guide into frameworks #321
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
…utor details - Enhanced the Discord management documentation with a new summary section outlining key security measures. - Introduced a comprehensive account security checklist for individuals and team members. - Updated contributor information to include Auditware, reflecting their role and contributions. - Streamlined content for clarity and improved organization of security measures and guidelines.
|
@DicksonWu654 is attempting to deploy a commit to the Security Alliance Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
NFTDreww
reviewed
Dec 17, 2025
- Updated all checklist items to use proper User Settings paths - Added instructions for removing phone number and saving backup codes - Changed Privacy & Safety to Content & Social paths - Updated DM filtering to use "Filter all" option Co-authored-by: NFTDreww
- Removed Content Filter section (no longer in Discord) - Removed "CAPTCHA all accounts" option - Removed Timeout section (moved to different location) - Removed Permissions section (now part of community setup flow) - Removed Membership Screening section (separate flow for age-restricted servers) Co-authored-by: NFTDreww
- Changed path from "Server Settings > AutoMod" to "Server Settings > Safety Setup > AutoMod" - Removed deprecated "Explicit image filter" line - Added recommendation to create private channel for AutoMod logs Co-authored-by: NFTDreww
- Changed from "Server Settings > Overview" to "Server Settings > Engagement > Default Notification Settings" - Updated terminology from "Mentions Only" to "Only @mentions" Co-authored-by: NFTDreww
- Clarified that minimal bots actually need Admin permissions - Encouraged users to review actual bot permission needs instead of defaulting to Admin - Updated integration command permissions path to correct location - Removed non-existent "Allow new integrations" setting Co-authored-by: NFTDreww
- Removed outdated invite permissions setting from Invites section - Updated Privacy Settings to use current "Direct Messages" toggle wording Co-authored-by: NFTDreww
- Removed Manage Channels and Manage Roles from Moderators (too privileged) - Added appropriate Moderator permissions: View Audit Log, View Server Insights, Kick/Ban/Timeout, messaging, and moderation - Simplified Members permissions to basic viewing and messaging only - Removed dangerous permissions like Ban/Kick/Timeout and Manage Messages from Members Co-authored-by: NFTDreww
- Removed less secure "react to message" suggestion - Updated Wick bot recommendation to emphasize in-channel captcha verification Co-authored-by: NFTDreww
- Removed MEE6 link from Logging Setup section - Removed MEE6 link from Additional Recommendations section - MEE6 has had multiple security incidents and is not recommended Co-authored-by: NFTDreww
- Updated Anti-Impersonation Bots section to recommend Hashbot instead of Wick Bot - Added link to hashbot.com Co-authored-by: NFTDreww
- Removed Security subsection with QR scan options that Discord no longer has - Discord has removed this setting from Privacy & Safety Co-authored-by: NFTDreww
- Added back "CAPTCHA all accounts before they are able to join during a suspected raid" option - This setting was incorrectly removed; it should be updated, not deleted Co-authored-by: NFTDreww
- Restructured Integration section to properly group items under the "Manage Bot/App > Roles & Members / Channels" path - This path applies to permission removal, uninstalling, verification, and command restriction - not just the last item Co-authored-by: NFTDreww
- Updated the command permissions restriction note to include the specific path: Manage > Roles & Members / Channels / Command Overrides - This addition enhances clarity for server administrators on where to manage integration permissions effectively.
- Added explanation of what Cold Admin is and why it's important - Added Cold Device definition and requirements - Added detailed step-by-step setup instructions: - Creating dedicated email account with 2FA - Creating Discord account with proper settings - Joining server and transferring ownership safely - Added usage guidelines and monthly maintenance reminder - Added critical warning about ownership transfer verification Co-authored-by: NFTDreww
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Frameworks PR Checklist
Integrating w3os discord guide into frameworks
This is from #305. @NFTDreww suggested we merge discord first into frameworks, then work on the other ones. This has alreayd been approved by NFT Drew
vocs.config.tsadding thedev: trueparameter