rainbownapkin/canopy
1
0
Fork 0
Code Issues 2 Pull requests Actions Packages Projects Releases Wiki Activity

Channel-only User Bans #14

New issue
Closed
opened 2024-11-15 18:05:59 -05:00 by rainbownapkin · 6 comments
rainbownapkin commented 2024-11-15 18:05:59 -05:00 (Migrated from gitlab.com)
Copy link

Create per-channel username-ban system, no space for alt names needed since they'll still be in the users DB, and whatever future alt-management system we make.

Bans should be entirely manageable from the channelSettings frontend.

!chanBan command will be created as part of: #50

Create per-channel username-ban system, no space for alt names needed since they'll still be in the users DB, and whatever future alt-management system we make. Bans should be entirely manageable from the channelSettings frontend. !chanBan command will be created as part of: #50
rainbownapkin commented 2024-11-15 18:05:59 -05:00 (Migrated from gitlab.com)
Copy link

added #6 as parent issue

added #6 as parent issue
rainbownapkin commented 2024-11-27 07:30:20 -05:00 (Migrated from gitlab.com)
Copy link

changed the description

changed the description
rainbownapkin commented 2024-11-27 07:30:49 -05:00 (Migrated from gitlab.com)
Copy link

changed the description

changed the description
rainbownapkin commented 2024-11-27 07:34:27 -05:00 (Migrated from gitlab.com)
Copy link

changed title from Channel-only Bans to Channel-only {+User +}Bans

changed title from **Channel-only Bans** to **Channel-only {+User +}Bans**
rainbownapkin commented 2024-11-30 06:42:55 -05:00 (Migrated from gitlab.com)
Copy link

Finished up with basic database management and related ajax calls for channel bans: ef79e9941c

Now we just need to finish up with the front end for it in the channelSettings page, and add logic to block banned users from joining respective channels.

Finished up with basic database management and related ajax calls for channel bans: ef79e9941cdfd64b46591f6100d294b18ccaa6ba Now we just need to finish up with the front end for it in the channelSettings page, and add logic to block banned users from joining respective channels.
rainbownapkin commented 2024-12-01 17:19:22 -05:00 (Migrated from gitlab.com)
Copy link

Finished up with channel-based user bans: 96953979a2

Finished up with channel-based user bans: 96953979a221defda99ecdcc4e40c432f056e95f
rainbownapkin (Migrated from gitlab.com) closed this issue 2024-12-01 17:19:22 -05:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
dev
0.4-indev-hotfix-3
0.4-indev-hotfix-2
0.4-indev-hotfix-1
0.4-indev
0.3-indev-hotfix-1
0.3-indev
verbose-queue
0.2-indev
0.1-indev
No results found.
Labels
Clear labels   
Bug

   
Cleanup/Refactor

   
Core Feature

   
Documentation

   
Feature

   
Performance Improvement

   
Security Improvement

   
UX/Accessibility

   
Unreproducable Bug
No labels
Bug
Cleanup/Refactor
Core Feature
Documentation
Feature
Performance Improvement
Security Improvement
UX/Accessibility
Unreproducable Bug
Milestone
Clear milestone
No items
No milestone
Canopy v0.1-Indev
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: rainbownapkin/canopy#14
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?