To leave a message for me, press the "new section" tab at the top of the page. Remember to sign your message with ~~~~. I will respond to all civil messages.
I attempt to keep conversations in one location, as I find it easier to follow them that way when they are archived. If you open a new conversation here, I will respond to you here. Please watchlist this page or check back for my reply. If I have already left a message at your talk page, unless I've requested follow-up here or it is a standard template message, I am watching it. If you leave your reply here, I may respond at your talk page if it seems better for context. If you aren't sure if I'm watching your page, feel free to approach me here.
Vous pouvez également communiquer en français
Ihr könnt hier auch auf deutsch kommunizieren.
Admins, if you see that I've made a mistake, please fix it.
I will not consider it wheel-warring if you reverse my admin actions as long as you leave me a civil note telling me what you've done and why and as long as you're open to discussion with me should I disagree.
Changes to user permissions made from Meta are now included in the local user permissions log (T6055).
The autoconfirmed user group will soon be modified such that the four-day account age requirement begins when an account makes its first edit (T418484).
Arbitration
The arbitration case SchroCat has been opened. Evidence submissions in this case closed on 15 April.
Per a recent motion, appeals of blocks from the conflict-of-interest VRT queue are, by default, appealed on-wiki through the normal unblock process. However, they may be heard by the Committee if COIVRTers disagree on the interpretation of the evidence or believe ArbCom would be better suited to hear the appeal. Administrators are also advised that loosening or lifting such blocks without the consent of someone with access to the queue or ArbCom can be grounds for desysopping.
Per a recent motion, restrictions issued directly by the Committee may now be enforced with blocks which work exactly like contentious topic blocks.
Mandatory 2FA for bureaucrats: Bureaucrats without two-factor authentication (2FA) enabled have already lost access to their advanced rights on 26 May. Those who do not enable 2FA may be automatically removed from the groups in mid-June 2026, and from that point onward, new members must have 2FA enabled before they can be added. (T423119, T423120)
