Elevated roles: Unprivileged

I define "key position of trust" as a user group that itself grants at least one formally restrictive right:

• abusefilter-modify
• block
• centralauth-lock
• hideuser
• globalblock
• userrights (even if partial)

This user is currently experiencing significant real world stress that may affect their ability to work on Wikimedia. This user may choose to work in quieter areas and avoid complicated tasks or areas prone to conflict. This user may also respond to talk page messages or e-mails more slowly than usual, and your patience is greatly appreciated. Thank you.

This user tries to do the right thing. If he makes a mistake, please let him know.

This user has extended confirmed rights on the English Wikipedia. (verify·CA)

This user is a reviewer on the English Wikibooks. (verify)

This user has been on Wikimedia Projects for 3 years, 9 months and 26 days.

3,000+

This user has made over 3,000 contributions to Wikimedia projects. (total)

Languages: en-N, ta-2, cs-1, sk-1

Wikis most active:

• English Wikipedia (ENWP)
• Meta (META)
• Tamil Wikivoyage (TAWY, Incubator)

I have never edited under another account, and I do not use an alternate account.

For each invalid character, follow the first applicable rule in the associated section below:

• Leave them capitalized: aiAssist becomes AiAssist.

• If all invalid non-brackets can be replaced with spaces to produce a satisfactory title, then this should be done.
• Otherwise, replace them with the appropriate name of the character: C# becomes C sharp.
• Use only ( and ) as brackets, even to replace < and >.

• Separate characters with spaces: ~~~ becomes ~ ~ ~
• Keep these groups of characters together whenever possible:
  • groups of alphanumeric and non-alphanumeric characters: %26%26%27 becomes % 26 % 26 % 27 with &&' → % 26 % 26 % 27 (What it resolves to)
  • same type of non-alphanumeric characters: ..//.. becomes .. // ..

• Leave underscores and spaces truncated to a single space: By also the first and third rules for forbidden characters, <|°_°|> becomes ( ° ° )

• If colons and/or vertical bars can be removed to produce a satisfactory title, then this should be done: :User:0000 becomes User 0000
• series: part becomes Series – part: CR: The Finale becomes CR – The Finale
• variable: value becomes variable. value, similar to list items: C: Plan Siege becomes C. Plan Siege
• value: variable becomes value, variable: SS: Devastating Duo becomes SS, Devastating Duo
• colon relationships like x:y become x/y

• Truncate the title to the first comma or period, replacing it with ....
• Stop after one noun and one verb, leaving any other words in between: For example, stop at First plan multiple ideas...
• Truncate to the first 8 syllables: TwentyOneThousandEightHundredSeventyOneAndSixtyOneThousandFiveHundredSixtyOneArePartAbsoluteFactorsOfBehemoth3000000... becomes TwentyOneThousandEightHundred...
• In the case of long numbers:
  • Put them in mixed number form: 0.0000056305989268... becomes 1/177601
  • If the number is too long or the numerator and/or denominator of the fraction form is too long to remember (your discretion), locate it under scientific notation, preferably rounded to 16 digits from the nonzero digit: (256!) becomes 8.5781777534284265e506
  • In both above cases, other forms of the article title, such as longer forms, should redirect to the refactored title: 1/543185295592672549499302394643640275918374120256093130759988042950370991361 → 1.8409923981997604e-75

On ENWP:

• When I moved the article Multivariate logistic regression into mainspace, it was already longer than Katherina Kubenk!
• When I moved the article Satellite gravity into mainspace, it was already longer than Trams in Navapolatsk!

• Alternate between:
  • editing articles until you dominate them until they make up 45% of your edit count among namespaces (main), User talk, and Project.
  • helping in admin-related areas until a non-mainspace namespace becomes your namespace with most edits.

Content projects: (1/40 * years on the site + (3 on Wikipedias, 10 on other wikis) * (edits + edits to administrative pages + user talk page edits / 4) / 40000) * (1 + .1 for each actively used advanced right on any wiki + .25 for each other wiki one is already an administrator of)

Coordination projects and stewardship: (1/40 * years on Wikimedia + 2 * (edits (global) + local edits + edits to administrative pages (local) + user talk page edits / 4) / 120000) * (1 + .1 for each actively used advanced right on any wiki + .5 for each other wiki one is already an administrator of + .25 * (number of languages active in - 1))

English Wikipedia: 29.1% ⬤ editing in mainspace only

Tamil Wikivoyage: 5.7% ⬤ editing in mainspace only (-2 years)

Meta-Wiki: ?

The best way to oppose an RfA of a candidate who is on the right track and will be ready after some more time is to give them constructive feedback on their contributions and to explain why you oppose the RfA anyway, for example:

•  Oppose I appreciate how you have created and expanded many articles on the English Wikipedia and fight vandalism from time to time, but I am opposing because you have made 6,000 edits so far. I will be happy to accept once you have made more than 8,000 edits.
•  Oppose I appreciate your extensive contributions on English Wikipedia and that you are an active administrator on Tamil Wikivoyage, but you have only made 5,000 edits here on Meta.
•  Oppose I like how you are an administrator on both English Wikipedia and Tamil Wikivoyage, but you aren't active enough on Meta. Once you become more active, I will be more than happy to support you.

Just to clarify, I am not an administrator anywhere.

1. 24 hours
2. 48 hours
3. 72 hours
4. 5 days
5. 7 days
6. 14 days
7. 21 days
8. 30 days
9. 46 days
10. 61 days
11. 76 days
12. 91 days
13. 17 weeks
14. 26 weeks
15. 39 weeks
16. 52 weeks
17. 78 weeks
18. 24 months
19. 36 months
20. 60 months
21. ∞