Skip to content

Commit

Permalink
Merge pull request #81 from snoonetIRC/nickname-dropping-guidelines
Browse files Browse the repository at this point in the history
Update rules for dropping inactive nicknames
  • Loading branch information
A-UNDERSCORE-D authored May 27, 2019
2 parents d3c47cf + d14019e commit 68da531
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion content/rules/user.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ weight: 1
+ Users may request ownership of their chosen nickname on Snoonet, but this is offered as a privilege and not a right. To request a specific nickname, please contact us in #help. Requests will be considered and discussed at the sole discretion of Snoonet staff. We may refuse to drop nicknames that violate Snoonet rules, are historically significant, are reserved for network purposes, or for any other reason. Nicknames must be inactive for at least 3 months before requested to be dropped.
+ Your nickname may not contain any racial slurs or bigotry. Names in violation of this are subject to being dropped and/or prohibited, with repeat offenders being banned.
+ Temporary/disposable email addresses are prohibited. Snoonet reserves the right to delete your registration if you register with a false/throwaway email address.
+ By default, nicknames have an insane expiration date. Single accounts with 1 name and 6+ months of inactivity may be dropped if someone requests the name. Nicknames grouped to any single account may be ungrouped after 3+ months of inactivity and upon request of another user.
+ By default, nicknames have an insane expiration date. Upon request, single accounts with only 1 name and at least 1 year of inactivity may be dropped. Nicknames grouped (/NS GROUP) to any single account may be ungrouped/dropped after at least 6 months of inactivity. Requests for nicknames to be dropped will be subject to staff discretion.

## Hostmasks

Expand Down

0 comments on commit 68da531

Please sign in to comment.