Post by noahjupe12 on Mar 14, 2023 10:42:04 GMT -8
So, basically what I want to implement- yet can't find a plugin- or a way to do so- is a way to manage both users and posts.
Deactivation is when we place an IP ban on that specific account, so they can't log in and multiaccount. The reason being simple- to avoid overwhelming people with trying to contact people who aren't on that specific account anymore- but rather on another- that would be the purpose of deactivating an account. Plus, it doesn't delete any of their posts that they have made onsite.
Soft Deletion is when a user requests to be removed- usually because they don't plan on returning. But soft deletion has a few benefits. (1) It doesn't remove posts that the user has posted entirely. (2) Staff can soft delete posts and still view them- but regular members can't. (3) It can be used for terms of records, and is basically safe- preventing you from losing said item/post/user from the database. Additionally, Soft Deletion when used with POSTS, not users, can still show soft deleted posts in a thread to staff, not regular members.
Hard Deletion is when two things come into play. (1) A user's guardian requests that the account be removed. and (2) if a user is permanently banned- they will not be allowed to come onsite. A Hard Deletion comes with an IP ban, and complete deletion of their account. There will be no evidence of said post or user ever being onsite- and this is dangerous for even moderators to use- or even members- because when administrators are forced to take things into their own hands- we face the risk of a user permanently deleting said post- or a moderator deleting an account.
What I wish to propose is an idea- preferably as a Plugin- to grant staff the ability to do three methods with both Users and Posts- Deactivation, Soft Deletion, and Hard Deletion.
Additionally, I'd also like to propose the way for Moderators to deal with approving users onsite/validation. However, for terms of user safety, I would like for a way for them to NOT see the literal IP address, but rather a color change over a user who signs up for an account- to know if a certain user is multiaccounting.
Deactivation is when we place an IP ban on that specific account, so they can't log in and multiaccount. The reason being simple- to avoid overwhelming people with trying to contact people who aren't on that specific account anymore- but rather on another- that would be the purpose of deactivating an account. Plus, it doesn't delete any of their posts that they have made onsite.
Soft Deletion is when a user requests to be removed- usually because they don't plan on returning. But soft deletion has a few benefits. (1) It doesn't remove posts that the user has posted entirely. (2) Staff can soft delete posts and still view them- but regular members can't. (3) It can be used for terms of records, and is basically safe- preventing you from losing said item/post/user from the database. Additionally, Soft Deletion when used with POSTS, not users, can still show soft deleted posts in a thread to staff, not regular members.
Hard Deletion is when two things come into play. (1) A user's guardian requests that the account be removed. and (2) if a user is permanently banned- they will not be allowed to come onsite. A Hard Deletion comes with an IP ban, and complete deletion of their account. There will be no evidence of said post or user ever being onsite- and this is dangerous for even moderators to use- or even members- because when administrators are forced to take things into their own hands- we face the risk of a user permanently deleting said post- or a moderator deleting an account.
What I wish to propose is an idea- preferably as a Plugin- to grant staff the ability to do three methods with both Users and Posts- Deactivation, Soft Deletion, and Hard Deletion.
Additionally, I'd also like to propose the way for Moderators to deal with approving users onsite/validation. However, for terms of user safety, I would like for a way for them to NOT see the literal IP address, but rather a color change over a user who signs up for an account- to know if a certain user is multiaccounting.
