search

QuiltMC / quiltmc.org

The source for quiltmc.org
https://quiltmc.org
Other
58 stars 48 forks source link

Update nickname rules #105

Closed Akarys42 closed 1 year ago

Akarys42 commented 1 year ago

Implements suggestion 1052159108557570088 ("Add a rule in the nicknames section of the rules against intentionally confusing or misleading nicknames, to avoid accessibility issues and impersonations.") and simplify the wording of that section.

netlify[bot] commented 1 year ago

Deploy Preview for ecstatic-booth-88897a ready!

Name Link
Latest commit 4e8f096b711e5c4195e2859c7b516d7fcbdd0f7c
Latest deploy log https://app.netlify.com/sites/ecstatic-booth-88897a/deploys/63da14b90dd09b00096b9664
Deploy Preview https://deploy-preview-105--ecstatic-booth-88897a.netlify.app
Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

cloudflare-workers-and-pages[bot] commented 1 year ago

Deploying with  Cloudflare Pages  Cloudflare Pages

Latest commit: 4e8f096
Status: ✅  Deploy successful!
Preview URL: https://1661f88d.quiltmc-org.pages.dev
Branch Preview URL: https://update-nickname-rules.quiltmc-org.pages.dev

View logs

Akarys42 commented 1 year ago

Rendered view

obj-obj commented 1 year ago

no Zalgo

nooooooooooooooo

Southpaw1496 commented 1 year ago

I have a few thoughts about the wording. I'm not sure how much of this is "French grammar is different than English" and how much is "Southpaw enforcing his writing style on everyone else" but I thought I'd put them out there anyway.

  1. Maybe I'm just not hip or down with the language kids, but I'd never use ex: to abbreviate "for example", I'd use eg. instead.
  2. I'm not sure if you're using "example" correctly in the first place. I personally think it would be easier to read if you got rid of the example part and just put them straight.

Here are some examples. I chopped and changed them a little, feel free to take selectively.

  1. Nicknames must be easy to read, especially by a screen-reader. This means no Zalgo or other difficult-to-read styling, or Unicode control characters.
    1. Nicknames cannot be intentionally confusing or misleading. Impersonation is stricly forbidden, as well as using similar looking nicknames to be intentionally confusing.
    2. Nicknames must have some readable characters. This means no "empty" nicknames.
  2. Are empty nicknames the only thing Rule 3 is trying to prevent? If so, couldn't we just say "no empty nicknames", and if not, perhaps we should give another example?
  3. I'm not sure if the last paragraph needs to change at all, I've always thought our right to change nicknames that break rules was implicit. If you think it does, you should remove "also".
  4. The first paragraph could be much shorter. "All nicknames must adhere to the rules above, in addition to the following rules:"

I think it looks good overall, though.

Akarys42 commented 1 year ago

The examples are because they are only one way the rule would apply. For example, not having a hard to read nickname means you can't have zalgo, but also anything else hard to read that isn't zalgo. Does that make sense?

Appreciate the feedback, I'll have a look at it shortly.

Southpaw1496 commented 1 year ago

I'm going to botch saying this, but while I understand what you're saying about the examples, I don't think my versions imply that only the specific examples we give are banned. But, if you did want to explicitly say "example", you shouldn't describe a good nickname "easy to read", before giving examples of bad ones. So, instead, you might say:

  1. Nicknames can't contain characters which might be difficult to read, especially for screen readers (eg. Zalgo, ornate Unicode letters, or Unicode control characters.)
  2. Nicknames can't be intentionally confusing or misleading (eg. nicknames that impersonate someone else, or are intentionally confusingly similar to someone else's.
  3. No nicknames without readable characters (e.g "invisible" names).
ghost commented 1 year ago

Unicode defines zero width joiners as control characters so rule 1 would forbid certain system tags, can we make an exception for these...

Uhhh looks like discord might not even allow zwj in names which is odd

gdude2002 commented 1 year ago

Out of curiosity, how are those useful in system tags?

Akarys42 commented 1 year ago

Discord will strip ZWS from names anyway (including webhooks), there is no need to complexity the rules for that

Akarys42 commented 1 year ago

Also, should we define what "hard-to-read" means? I don't think so, that'd open to rule lawyering quite easily. That should be left to the moderator's appreciation imo.

Maybe we should just put no hoisting in the rules to make the rule set more consistent If we do that, there will be a set expectation that we'll be taking down any hoister, which honestly seems like a waste of time to me. If anything, I'd rather completely stop caring about hoisters, but some people like to reset their nicks.

pluiedev commented 1 year ago

If anything I'd rather completely stop caring about hoisters, but some people like to reset their nicks.

Yeah honestly I agree, it's not like hoisters actually cause real problems for us anyway...

woodiertexas commented 1 year ago

Afaik hoisting just makes the memberlist look ugly.

pluiedev commented 1 year ago

Afaik hoisting just makes the memberlist look ugly.

Ugly? Possibly. Distracting? Probably not? We already have lots of staff members and bots hoisted on there that normal hoisters don't really show up that much. A moderation problem either way? Nope

woodiertexas commented 1 year ago

Only way it would be a moderation problem is if people combine hoisting with status advertisements,