Page extended-protected
From Wikipedia, the free encyclopedia
(Redirected from Wikipedia:RfR)

    Requests for permissions

    This page enables administrators to handle requests for permissions on the English Wikipedia. Administrators are able to modify account creator, autopatrolled, confirmed, file mover, extended confirmed, mass message sender, new page reviewer, page mover, pending changes reviewer, rollback, and template editor rights, and AutoWikiBrowser access.

    Editors wishing to request a permission flag here should do so following the procedure below. Editors requesting permissions are advised to periodically revisit the requests page, as notifications will not always be given after a decision is made. Editors should not expect their request to be answered right away and should remember to be patient when filing a request. To find out what permissions your account has, go to Special:Preferences, where your permissions are listed in the user profile tab under "Member of groups".

    Requests for permissions are archived regularly; please see Wikipedia:Requests for permissions/Archive for an index of past requests.

    Bot report: No errors! Report generated at 14:30, 2 August 2024 (UTC)

    Permissions

    Handled here

    • Account creator ( add request · view requests): The account creator flag is granted to users who are active in the request an account process. The flag removes the limit on the maximum number of new accounts that can be created in a 24 hour period. It also allows users to make accounts with names similar to other accounts. The account creator flag is only given to users who participate in the ACC process and may be removed without notice should a user's participation in the account creation process cease.
    • Autopatrolled ( add request · view requests): The autopatrolled flag is granted to users who are active in the creation of new articles. This tool is granted so their creations are auto patrolled in Special:NewPages. Unlike other requests, any user may nominate an editor for Autopatrolled, even without that user's consent. A user who wishes to have this flag generally should have created at least 25 articles and must be trusted, experienced, and must have demonstrated they are familiar with Wikipedia's policies and guidelines, especially WP:BLP and Wikipedia:Notability.
    • AutoWikiBrowser ( add request · view requests): AutoWikiBrowser is a semi-automated MediaWiki editor for Microsoft Windows, designed to make tedious repetitive tasks quicker and easier. It is essentially a browser that automatically opens up a new page when the last is saved. When set to do so, it suggests some changes (typically formatting) that are generally meant to be incidental to the main change. Please read the rules of use and registration requirements on the main page before requesting permission. This is not a true user right, but access needs to be granted by administrators just like other permissions. If approved, your name will be added to the CheckPage. Users with under 250 non-automated mainspace edits or 500 total mainspace edits are rarely approved. You will need to give a reason for wanting AWB access.
    • Confirmed ( add request · view requests): The confirmed flag may be granted to new users who have not yet hit the threshold for autoconfirmed status. These are users who have not had both 10 edits and 4 days experience. People with this flag can upload files and edit semi-protected pages before hitting the autoconfirmed flag. Users requesting this flag must indicate clearly why they should be exempted from the customary confirmation period.
    • Event coordinator ( add request · view requests): The event coordinator user right allows editors to create multiple new accounts, and to temporarily confirm accounts so that they can create new articles.
    • Extended confirmed ( add request · view requests): The extended confirmed flag is normally automatically added to accounts after 500 edits and 30 days, but may be added to legitimate alternate accounts of users that already have this access. The flag allows users to edit pages under extended confirmed protection.
    • File mover ( add request · view requests): The file mover user right is intended to allow users experienced in working with files to rename them, subject to policy, with the ease that autoconfirmed users already enjoy when renaming Wikipedia articles.
    • Mass message sender ( add request · view requests): Mass message sender enables users to send messages to multiple users at once. This flag is given to users who have made requests for delivery in the past, clearly showing an understanding of the guidance for use.
    • New page reviewer ( add request · view requests): The new page reviewer user right allows users to mark pages as patrolled and use the page curation toolbar. At administrators' discretion, the right may be accorded on a time limited basis or indefinite.
    • Page mover ( add request · view requests): The page mover user right allows users experienced in working with article names to move them, subject to policy, without leaving behind a redirect. They may also move all subpages when moving the parent page(s). General guidelines include making 3,000 edits and 6 months of editing history. At administrators' discretion, the right may be accorded on a time limited basis or indefinite.
    • Pending changes reviewer ( add request · view requests): The reviewer flag is granted to users who are experienced enough with Wikipedia editing and its policies for contributing to the process of reviewing articles placed under pending changes.
    • Rollback ( add request · view requests): Rollback enables users to remove vandalism much more quickly and efficiently than by undoing it. Users who do not demonstrate an understanding of what constitutes capable vandalism fighting, either because they have no or little history of doing so, or show a poor ability to discern between good and bad faith edits will not be granted this right. Also, it is unlikely that editors with under 200 mainspace edits will have their request granted. For a more detailed explanation of rollback and information about when it is appropriate to use the tool, see Wikipedia:Rollback. For information about the technical details of the feature, see here.
    • Template editor ( add request · view requests): The template editor flag allows users to edit protected templates and Lua modules. General guidelines for granting include making at least 1,000 edits overall (with at least 150 to templates or modules), being a registered user for over a year, and having a record of successfully proposing significant edits to several protected templates. Users should demonstrate proficiency with template syntax and an understanding of the need for caution when editing heavily-used templates.

    Handled elsewhere

    Several permissions are requested and handled elsewhere:

    Removal of permissions

    If you wish to have any of your permission flags (except administrator) removed, you should contact an administrator. If you want your administrator flag removed, you should contact a bureaucrat.

    This is not the place to request review of another user's rights. If you believe someone's actions merit removal of a permission flag, you should raise your concern at the incidents noticeboard.

    The bureaucrat, checkuser, and oversight flags are removed at meta:Steward requests/Permissions. Stewards will typically not carry out such requests unless they are made on behalf of the Arbitration Committee, by a user who is requesting their own access be removed, or in cases of an emergency.

    Process

    Requestors

    To make a request for a permission, click "add request" next to the appropriate header and fill in the reason for wanting permission.

    Any editor may comment on requests for permission.

    Administrators

    Administrators are permitted to grant account creator, autopatrolled, confirmed, event coordinator, file mover, mass message sender, new page reviewer, page mover, pending changes reviewer, rollback and template editor flags to any user who meets the criteria explained above and can be trusted not to abuse the tool(s). Administrators may either grant these permissions permanently or temporarily. For convenience, a bot will automatically comment with relevant data if the user does not meet configurable qualifications. Even if the bot does not comment, administrators should review the user's contributions and logs to ensure the tools will be used appropriately and check for any indication of potential misuse.

    Once an administrator has granted a permission or decided to deny a request, they should add {{ done}} or {{ not done}} respectively under the request with their comments. If a user already has the requested permission, or is autoconfirmed and requesting confirmed, {{ already done}} should be used. N hours after the last comment was made (as specified by the config), the request will be archived automatically: approved requests will be placed here; declined requests will go here. See User:MusikBot/PermClerk#Archiving for more information on archiving functionality.

    Other editors

    Requests for permissions is primarily intended for editors requesting a permission for their own account. Other editors are welcome to comment if they have specific information that is relevant to that request that a patrolling administrator is unlikely to discover for themselves. Otherwise, since only administrators can effectively respond to these requests, general comments or 'clerking' by other users are rarely helpful. Non-administrators cannot "decline" to grant a request, because they're not in a position to accept it.

    A limited exception to this is Wikipedia:Requests for permissions/Autopatrolled, where third party nominations are encouraged. Other editors should still avoid offering general remarks on requests and leave the final decision to an administrator.

    Current requests

    Account creator


    Autopatrolled

    Has created roughly 30 articles by my count; only one stub, my spotchecks found nothing concerning. Diverging Diamond (is Queen of Hearts's alt; talk) 19:10, 1 August 2024 (UTC) reply

    Is there any indication that the user wants autopatrolled? I don't want to throw rights at someone who would prefer that their creations be reviewed by NPP/AfC. — Red-tailed hawk  (nest) 10:42, 2 August 2024 (UTC) reply
    @ Red-tailed hawk: Unlike other PERMs, third party nominations for autopatrolled are welcome (preferred even), because it's primarily a tool used by NPP to manage its workload rather than a tool used by the holder to edit. If someone really doesn't want it for some reason, they can of course ask for it to be removed. –  Joe ( talk) 11:59, 2 August 2024 (UTC) reply
    @ Red-tailed hawk I would be open to having it. Hypothetically I like the idea of someone else checking my articles or critiquing them, but no one who has patrolled my articles has ever really made a significant change or tagged anything, so it hasn't really helped there lol, so if it reduces the NPP workload and gets the page indexed faster I don't see why not. PARAKANYAA ( talk) 13:04, 2 August 2024 (UTC) reply
    In that case, I have no objection to granting the right. — Red-tailed sock  (Red-tailed hawk's nest) 13:08, 2 August 2024 (UTC) reply

    For a third time, I'm applying for autopatrolled rights; my first request was denied in April 2023, and my second request was denied in June 2024. The reason for the first decline was that my previous articles were tagged for "notability." After that decline, I worked on bringing articles over from the Russian Wikipedia and had relatively few problems when other editors were reviewing them (I don't bring over everything from those respective pages, so I added a tag for expanding from Russian to let others know that information is still there). The reason for the second decline was that I moved one of my BLP articles back into the mainspace without changing the sourcing, and it was eventually deleted (that was a mistake on my part). Now, roughly two months later, I have had little to no problems with the other articles I have brought over. I respectfully request that I be granted the autopatrolled permission this time around, as I believe it will help lighten the NPP workload to some extent. Thanks in advance for your consideration. Losipov ( talk) 20:10, 2 August 2024 (UTC) reply

     Automated comment This user has had 1 request for autopatrolled declined in the past 90 days ( [1]). MusikBot talk 20:20, 2 August 2024 (UTC) reply

    AutoWikiBrowser


    Requesting so I can help streamline small edits like typos, general maintenance, and so on. NyanThousand ( talk) 12:56, 23 July 2024 (UTC) reply

    I will use AWB to tag galaxy-related (and other astronomical objects) with the appropriate talk page banners (WP:ASTRONOMICAL OBJECTS), and will use it to tag "Weather of _____" with the corresponding task force talk page banner tags. I can also use it for typos on long tornado articles, which tend to have misspellings in them. Sir MemeGod ._. ( talk - contribs - created articles) 05:10, 1 August 2024 (UTC) reply

    Hoping it will make nitpicky edit somewhat less tedious. Isaac Rabinovitch ( talk) 18:05, 2 August 2024 (UTC) reply



    Confirmed


    Event coordinator


    Extended confirmed

    Reason for requesting extended confirmed rights Sorin Balanel (Victoriabank) ( talk) 14:15, 1 August 2024 (UTC) reply

     Not done; no reason given. This will be granted automatically when you meet the requirements listed above. stwalkerster ( talk) 16:42, 1 August 2024 (UTC) reply

    I probably will not be extended confirmed because I have made few edits. etaoin shrdlu( cmfwyp| vbgkqj) 14:28, 1 August 2024 (UTC) reply

     Not done. This will be granted automatically when you meet the requirements listed above. stwalkerster ( talk) 16:42, 1 August 2024 (UTC) reply
    But it has been more than 30 days! etaoin shrdlu( cmfwyp| vbgkqj) 21:37, 1 August 2024 (UTC) reply
    You need to meet both the 30 day requirement and the 500 edits requirement. At the moment, you've only made 73 edits. stwalkerster ( talk) 23:01, 1 August 2024 (UTC) reply
    I thought it was 30 edits within 500 days! etaoin shrdlu( cmfwyp| vbgkqj) 13:52, 2 August 2024 (UTC) reply

    My legitimate alt-account. – The Sharpest Lives ( 💬✏️ℹ️) ( ping me!) 15:51, 1 August 2024 (UTC) reply

     Done stwalkerster ( talk) 16:43, 1 August 2024 (UTC) reply

    I ask permission to translate from English to Italian and viceversa without waiting for the 30 days and 500 edits limits... I would like to add more information about my family and my ancestors (Barattucci, in Wikipedia I found only Antonio: https://it.wikipedia.org/wiki/Antonio_Barattucci) but I don't think I will reach 500 edits during this process.. and I'd like to translate the pages into English too. Also, I'd like to translate into Italian the page of the Adragna family ( /info/en/?search=Adragna_family), one of its member is my friend Marta Adragna and she asked me to create the Italian version. Thanks in advance, Fabio Barattucci. DucaTux ( talk) 22:42, 2 August 2024 (UTC) reply


    File mover


    Mass message sender



    New page reviewer

    I want to reduce the massive backlog. I have been looking at the new pages patrol feed sporadically for the past two months and the backlog keeps increasing. I want to play a part in reviewing the articles. HRShami ( talk) 11:19, 21 June 2024 (UTC) reply

    Hello there, I am interested tn helping out in new page reviewing as there are very large articles backlog and love to do so. Xegma (talk) 07:10, 11 July 2024 (UTC) reply

    Question, though I am not an administrator, I see that you have published accepted AFC submissions, even if they lack citations or are in need of some fixing. And some have orange banners on them. Why is this? —  48 JCL 01:01, 17 July 2024 (UTC) reply
    @ 48JCL: As they should. The standard at acceptance at AfC is that the article would probably survive an AfD. Nothing more. Declining a draft for surmountable problems like a lack of citations or pretty much anything covered by a cleanup banner is inappropriate. –  Joe ( talk) 08:18, 19 July 2024 (UTC) reply
    I spot checked the 4 most recent accepts and they had lots of citations at time of acceptance. Feel free to link to the specific draft accepts you are concerned with. A complete lack of citations is a valid draftification reason and valid AFC decline reason, but I am not seeing that here. A major lack of citations such as entire paragraphs missing a citation (and also not supported by any WP:GENREFs) could be a valid decline reason ( WP:V is policy after all). But it may also be reasonable to accept a draft that is mostly cited and just missing a couple citations, such as Draft:Norah Fulcher. – Novem Linguae ( talk) 13:33, 19 July 2024 (UTC) reply

    I would like to request new page reviewer rights to help review newly-created articles and lower the backlog. I have accepted lots of drafts at AFC and participated in many AfDs with deep discussions to exhibit my knowledge of notability, as I was advised previously. Thanks! Waqar 💬 19:55, 14 July 2024 (UTC) reply

     Automated comment This user has had 1 request for new page reviewer declined in the past 90 days ( [2]). MusikBot talk 20:00, 14 July 2024 (UTC) reply
    I see you found the IP at AfC who submits soundtrack articles (41 accepts of soundtracks it looks like). I'm glad to see you've started to accept drafts at AfC, instead of just declining (a ratio of 1 accepted to 348 declined at the time of the last application). I do still have concerns about your experience at AFD, given that, of your last 40 votes, all but 2 of them were pile on votes where the result had basically already been decided based on the number of votes for the conclusion you chose. You accepted one piece of criticism from me, your lack of accepts at AfC, but you do still appear to be pile on voting. Honestly, I'm not sold, but I'll leave it up to someone else whether they want to grant you a trial or not. Hey man im josh ( talk) 18:56, 24 July 2024 (UTC) reply
    Thank you for your feedback. I understand your points, I've made lots of contributions recently, and I hope I will be granted a trial to demonstrate my willingness to contribute positively. Best, Waqar 💬 07:49, 25 July 2024 (UTC) reply
    I'd like to say that I've been working so hard for the past couple of months. I've made so many contributions to AFCs, I've reviewed over 1,160 articles (accepts: 138, declines: 670, and the rest either rejected or speedily deleted) so far. I'm also actively patrolling the new page feed, adding maintenance tags, and tagging articles for speedy deletion like A3, A7, and G11. I've drafted more than 200 articles that either lacked reliable sources or needed additional sources. In the AFD discussions, I voted on more than 150 pages. Without considering the no consensus results, 98.6% of my AfD's were matches, and even though the votes were assumed to be piles on voting, most of my recent votes were very detailed and specific and weren't pointing towards anyone, but I will accept their valuable advice and try my best to make improvements at AFDs as well. Having said that, I believe that all those contributions exhibit my hard work and dedication. I hope I get a chance to at least prove myself by patrolling new pages, and I would be more than happy to help with the backlog. Thanks for your time and consideration. Waqar 💬 18:10, 27 July 2024 (UTC) reply

    I was given a trial for a few months and would like to renew my permissions. I have made good use of my permissions by fixing new pages and applying CSD whenever necessary. Florificapis ( talk) 22:45, 31 July 2024 (UTC) reply

     Automated comment This user was granted temporary new page reviewer rights by Joe Roe (expires 00:00, 6 August 2024 (UTC)). MusikBot talk 22:50, 31 July 2024 (UTC) reply

    I'd like to help out with the backlog at NPP. My previous experience includes many nominations of drafts under G1, G2, and G3, and a couple instances of article ratings and XfD participation. Rusty  🐈 03:48, 3 August 2024 (UTC) reply


    Page mover


    I have been editing for over 7 years and I plan on using this permission in order to help with discussions on WP:RM and deal with cross-redirects for articles that should have more disambiguated titles. KingSkyLord ( talk | contribs) 12:46, 2 July 2024 (UTC) reply

    Reason for requesting page mover rights: I want to have my page mover rights extended, as I contribute to RM/TR. Was given 3mo trial and it will end on August 20. Toadette Edit! 08:30, 29 July 2024 (UTC) reply

     Automated comment This user was granted temporary page mover rights by Robertsky (expires 00:00, 20 August 2024 (UTC)). MusikBot talk 08:40, 29 July 2024 (UTC) reply

    I was granted pagemover rights nearly a month back, but due to mistakes on my part, the rights have been now revoked. So, I am requesting the rights again on Primefac's advice, explaining why I made the mistakes and how I shall avoid those mistakes going forward.

    • On 30 July, I moved British Indian Army to Indian Army (1895–1947) after which Celia Homeford informed me that the move had been unilateral, following which I immediately proceeded to check the talk page of the article for previous RMs, which I did find and had resulted in the move of Indian Army (1895–1947) to British Indian Army. I hadn't checked the talk page before swapping the page and thus had not been aware of this RM when I had swapped — a mistake on my part. I had checked the WP:COMMONNAME of the article and sought to make the article title WP:Consistent with other historical army related articles like German Army (1935–1945) for instance. I should've checked the talk page and it's archives for any previous RMs and discussions before making the swap. That is what I usually do before making a move or a swap, but this step had slipped my mind in this case. In future, I shall make sure to always check the talk page and the archives for RMs and discussions regarding the article title without fail before making a move or a swap.

    I've learnt from my mistakes and hope not to repeat them. I also aim to minimise any chance of any other mistakes on my part. PadFoot ( talk) 17:56, 30 July 2024 (UTC) reply

     Automated comment This user has had this permission revoked in the past 180 days ( [3]). MusikBot talk 18:00, 30 July 2024 (UTC) reply


    Pending changes reviewer

    I've been doing RCP for a little while now, and recently started NPP. I believe I could assist in patrolling recent changes to expand on my anti-vandalism work. Thanks, Lord serious pig 06:20, 26 July 2024 (UTC) reply

     Done Elli ( talk | contribs) 18:21, 31 July 2024 (UTC) reply

    I've been doing patrolling for a little while now, and recently started seriously devoting time. I believe I will submit myself in patrolling recent changes in contributing to anti-vandalism work. Thanks Fsrvb ( talk) 19:43, 1 August 2024 (UTC) reply

     Automated comment This user has had an account for 5 days and has 28 edits in the mainspace. MusikBot talk 00:00, 3 August 2024 (UTC) reply

    I have been monitoring recent changes on pages for a while now AlexBobCharles ( talk) 08:36, 2 August 2024 (UTC) reply



    Rollback

    I've been patrolling recent changes for a while now, using Twinkle to warn members. I have over 200 mainspace edits, and I'm extended confirmed with over 700 edits total. I've also been doing NPP for a little too. I'd like to use rollback for more advanced tools such as Huggle and AntiVandal. Thanks, Lord serious pig 06:14, 26 July 2024 (UTC) reply

    I see that you are failing to consistently warn editors when you revert their edits. Why? It's important to leave a notification for every revert you make. Are you aware that we have tools such as Twinkle or Ultraviolet that make this extremely easy? - Fastily 10:34, 28 July 2024 (UTC) reply
    I don’t believe I'm not, @ Fastily:, I warn people using twinkle, here is my warn logs: https://en.wikipedia.org/?title=Special%3AContributions&target=Lordseriouspig&namespace=3&tagfilter=twinkle&start=&end=&limit=50. Lord serious pig 20:31, 28 July 2024 (UTC) reply
    I reviewed your contributions from last month and found these within seconds: 1, 2, 3. I'll repeat what I said above: it's important to leave a notification for every revert you make. Are you aware that we have tools such as Twinkle or Ultraviolet that make this extremely easy? - Fastily 08:03, 1 August 2024 (UTC) reply
    I’m unsure why I forgot to add a warning for those, @ Fastily, considering Twinkle automatically opens the talk page, but I usually warn members, and tools like Anti-vandal or Huggle would probable negate me forgetting warns. Thanks, Lord serious pig 10:00, 1 August 2024 (UTC) reply
    No worries, thanks for your honesty. Please ensure that you are always leaving warnings. I can't stress enough the importance of not biting the newcomers; if you find yourself reverting good faith edits, then it's especially important to notify the editor. If you don't want to leave a template warning, that's completely fine, but you do need to leave a talk page message explaining why you reverted the edit. Moving forward, could you please make a promise to leave warnings/notifications for every revert? - Fastily 23:02, 1 August 2024 (UTC) reply
    No problem, @ Fastily I’ll definitely try to leave warnings for every revert I make. Thanks, Lord serious pig 02:57, 2 August 2024 (UTC) reply

    I've been recent changes patrolling on and off with Twinkle, and more recently Ultraviolet, for years now, and would like to try Huggle's more advanced tools. I have over 1.4k mainspace edits, no history of edit warring, and consistently and appropriately notify editors whose changes I revert. P1(she/her, talk/ contribs) 04:18, 1 August 2024 (UTC) reply

     Not done I noticed you make a handful of edits, and then drop off for months at a time. While I appreciate your enthusiasm, I'd like to see you spend at least a month consistently patrolling RecentChanges ( Twinkle & Ultraviolet can help with that) before reapplying. Also, please ensure that you are always warning editors when you revert their edits. Thanks, Fastily 08:03, 1 August 2024 (UTC) reply

    I've been viewing recent changes for a while with Twinkle, and would like to keep using the Android app to prevent vandalism, which requires rollback permissions.

    I am aware, after reading others' requests, that warning users after edits must be done every single time. While there are moments in which I have forgot to do this in the past, I will ensure to make it a consistency going forward. LR.127 ( talk) 00:54, 3 August 2024 (UTC) reply


    Template editor

    I am a frequent editor and creator of templates and modules, and I have encountered several instances where having the template editor permission would be helpful. Many of my requested edits on protected templates have been performing minor visual fixes or fixing small bugs with the template's logic. For these uncontroversial edits, having to submit a request and involve another editor feels unnecessary, considering the nature of the requested edits. In other cases with more significant changes, going through the edit request process works fine for the most part, but I like to be able to avoid the process because of the backlog the edit queue can have at times and the added potential confusion added by having to request technical changes. Because of this, I'd much rather be able to have a standard discussion on template talk pages, if necessary, followed by implementing the agreed upon changes myself rather than having to request someone else to implement the changes. In the near future, I plan on exploring adding support for the new dark mode to more templates and being able to implement these changes on protected templates myself would be of great help. In the future, I would also like to use my technical knowledge of wikitext and Lua to help with processing the template edit request queue.

    Another issue that the template editor permission would resolve is that several templates I've created or rewrote are now template editor protected: Template:For-multi, Template:Country name, Template:Yearly archive list/display, Template:Visible anchor/styles.css, Template:Divbox/styles.css, and Module:Outdent. As a result, I am unable to edit them, which makes several of them difficult to maintain. Per the guidelines, three templates sandboxes I've worked on include Module:Jcon/sandbox, Template:Visible anchor/sandbox/styles.css, and Template:Infobox road/sandbox and at some requested template edits are [4] [5] [6] [7] [8] [9] [10].

    Also, I acknowledge that I performed what ended up being (unintentionally) disruptive templates several years ago. Since then, I have learned a lot about collaborating with others on Wikipedia and being mindful of the impact template edits can have on articles across the wiki. Since then, I have been much more careful with the edits I perform, as these past experiences have shown me the dangers of not doing so. With the template edit permission, I intend to take from these past mistakes, and I will follow the best practices to ensure the template edits I perform are well-tested, agreed upon, and non-disruptive. I find that now I am very cautious with my template edits, and I always create thorough test cases (e.g. Template:Jcon/testcases) before performing changes. BrandonXLF ( talk) 19:08, 28 July 2024 (UTC) reply

    After looking at your contributions I'm inclined to grant, but would like to know if Primefac, EdJohnston, or Galobtter (admins who were involved with the placing and then lifting of your sanctions) have thoughts. Elli ( talk | contribs) 01:39, 30 July 2024 (UTC) reply
    Brandon has definitely matured as an editor since their first go-round with this permission. I've been burned in the past but let's say I'm cautiously optimistic. Primefac ( talk) 12:11, 30 July 2024 (UTC) reply
     Done for a three-month trial period. Feel free to request again in October and assuming there weren't any issues in the meantime, I'll be happy to grant the permission indefinitely. Elli ( talk | contribs) 18:11, 31 July 2024 (UTC) reply