On break since 7/30/2025.
CentralAuth | English Wikipedia | Tamil Wikivoyage | Commons | Meta
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
checkuser
hideuser
globalblock
userrights
(even if partial)
![]() | 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) |
![]() |
4,000+ |
Bio
Languages: en-N, ta-2, cs-1, sk-1
Wikis most active:
- English Wikipedia (ENWP)
- Meta (META)
- Commons (CMNS)
- Tamil Wikivoyage (TAWY, Incubator)
Hi! I'm Faster than Thunder, and I have been editing Wikimedia since I started 6th grade. Most of my edits are on English Wikipedia and Tamil Wikivoyage. Sometimes, you can see me rapidly warning vandals on Meta or Commons. I have written a few articles on English Wikipedia, such as Multivariate logistic regression. Tamil is my native language, so it's not surprising that I contribute extensively to Tamil Wikivoyage. I have also expanded many articles there, hoping that it eventually becomes its own wiki. Because of my dedication there, I most likely would end up as an administrator on Tamil Wikivoyage once it becomes its own wiki. I do request account blocks on English Wikipedia and Meta, and I even request account locks on Meta when needed, and they are usually acted on. I dislike when they take obviously long to get acted on, though.
Outside of Wikimedia, I am a sci-fi writer and play chess online. I also have autism.
I have never edited under another account, and I do not use an alternate account.
I've been targeted by drive-by vandals on Meta 5 times.
What I've learned from my mistakes throughout Wikimedia
- Do not make adminship your primary goal, and only apply when plugging values into the appropriate formula below says you are ready.
- Do not try to enforce your own standards for process and suggest them instead in appropriate places.
- If you edit Wikibooks or Wikivoyage, only edit based on your first-hand experience.
- Except in the case of obvious harassment, assume that administrators are right.
- If you are blocked on a wiki, avoid interacting with relevant users on other wikis.
Long articles
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!
Dominated pages
- Many User talk pages on Meta
- Multiple articles and templates on Tamil Wikivoyage
- w:en:Multivariate logistic regression
- w:en:Katherina Kubenk
- m:Template:Uw-machine
- w:en:Gymnospora
- w:en:Arnold Margolin (television producer)
- w:en:Cailhau
- w:en:Călinești, Argeș
- w:en:Kathy Goldman
- w:en:Ralph von Frese
- w:en:Satellite gravity
Tips for adminship (content projects only)
- 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.
Formula for Adminship readiness
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) * (1 - 0.1 * informal sanctions (i.e. bans, partial blocks) in the past 6 months - 0.25 * sitewide blocks on any wiki in the past year)
Coordination projects and stewardship: (1/40 * years on Wikimedia + (edits (global) + local edits + edits to administrative pages (local) + user talk page edits / 4) / 60000) * (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)) * (1 - 0.1 * informal sanctions (i.e. bans, partial blocks) in the past 6 months - 0.25 * sitewide blocks on any wiki in the past year)
English Wikipedia: 31.4% ⬤ editing in mainspace only
Commons: 6.1% (-40 months) ⬤ working in administrative areas only
Meta: 21.2% ⬤ working in administrative areas only
Advice for RfA commentators
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 500 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.
Oppose I appreciate how you have a clean track record here on Wikipedia, but you have an active ban on Wikivoyage. Once you resolve the problems related to the ban, I will be happy to support you.
My way of sanction times
Just to clarify, I am not an administrator anywhere.
- 24 hours
- 48 hours
- 72 hours
- 5 days
- 7 days
- 14 days
- 21 days
- 30 days
- 46 days
- 61 days
- 76 days
- 91 days
- 17 weeks
- 26 weeks
- 39 weeks
- 52 weeks
- 78 weeks
- 24 months
- 36 months
- 60 months
- ∞