If you wish to contact bureaucrats to alert them of a privacy issue or an emergency please use
or email wikien-bureaucratslists.wikimedia.org.
|Click here to add a new section|
|The Bureaucrats' noticeboard is a place where tasks related to the Bureaucrat permission can be discussed and coordinated. Any user is welcome to leave a message or join the discussion here. Please record any actions which require review below in a new section.
This is not a forum for grievances. It is a specific noticeboard addressing Bureaucrat-related issues. If you want to know more about an action by a particular bureaucrat, you should raise the matter with them on their talkpage in the first instance. Please stay on topic, remain civil, and remember to assume good faith. Take extraneous comments or threads to relevant talk pages.
Requests to hide usernames which are grossly insulting or contain personal information should be sent to the stewards OTRS queue via meta:Special:EmailUser/Wikimedia Stewards (or stewardswikimedia.org), or contact a steward privately via IRC (#wikimedia-stewards) but do not post it here.
To request your administrator status to be removed, initiate a new section below.
Resysop request (MikeLynch)
Hi there, I'd requested a de-sysop about a year and a half ago, and now that I'll be editing more frequently, I'd like to ask for me to be resysopped.
- This seems fine to me. We'll need to wait 24 hrs for other crats to review per WP:RESYSOP. Delighted to have you back. --Dweller (talk) Become old fashioned! 09:10, 25 July 2016 (UTC)
- Done. Welcome back. 28bytes (talk) 13:58, 25 July 2016 (UTC)
MadmanBot and "Notification of imminent suspension of administrative permissions due to inactivity"
Does anyone here take responsibility for User:MadmanBot and its erroneous messages regarding removing admin permissions?
The latest email:
Further to a previous email, your administrator permissions will be removed if you do not return to activity before 1 Aug 2016. Please see http://en.wikipedia.org/wiki/Wikipedia:Administrators#Procedural_removal_for_inactive_administrators for further details.
If you wish to have these permissions reinstated should this occur, please post to the Bureaucrats' noticeboard and the userright will be restored per the re-sysopping process (i.e., as long as the attending bureaucrats are reasonably satisfied that your account has not been compromised, that your inactivity did not have the effect of evading scrutiny of any actions which might have led to sanctions, and that you have not been inactive for a three year period of time). If you remain inactive for a three year period of time, including the present year you have been inactive, you will need to request reinstatement at RFA. This removal of access is procedural only, and not intended to reflect negatively upon you in any way.
We wish you the best in future endeavors, and thank you for your past administrative efforts.
This message has been sent by MadmanBot on behalf of the English Wikipedia bureaucrats. Please report any errors at http://en.wikipedia.org/wiki/User_talk:MadmanBot.
The "please report any errors" link redirects to User talk:Madman. Madman has made three edits since the fall of 2015 and no edits in the last month, so it seems unlikely that there is a lot of support going on there.
I received the first suspension notification on July 1st, when my last edit had been on July 5th of the previous year; close to but not actually inactive for a year. I had attempted repeatedly to recover my account through the email password recovery in the interim and failed, and so I'd been editing as an IP. The email recovery still doesn't work as far as I know, but yesterday I was somehow able to recover it through the username method. Anyway, made a couple edits yesterday to verify everything was working and assumed I would be in the clear.
Not so, it seems, since I received the above email today.
So, in short, what is up with that? I've been an admin for 12 years. I haven't used admin powers much recently, I admit, but then I've also never ever had a complaint against me for using them. Not an unreasonable balance. Thanks for your help. —Ben Brockert (42) 07:32, 25 July 2016 (UTC)
- Hi. Several points there:
It's not good that a bot operator is absent and not able to respond to issues raised. We need to address that.The speed of Madman's response easily deals with this --Dweller (talk) Become old fashioned! 13:00, 25 July 2016 (UTC)
- It seems totally appropriate for a warning of impending inactivity to be sent out before you reach the trigger point. That's the reason for the warning.
- If you're now active again, you won't be desysopped, but thanks for raising point one.
- Re your last paragraph, it's not personal. The community decided some time ago to desysop inactive admins. Read WP:RESYSOP - it's purely administrative and can be overturned.
- --Dweller (talk) Become old fashioned! 09:13, 25 July 2016 (UTC)
- @Dweller: Shame the source code isn't available for that bot task - it may be worth, should Madman return any time soon, asking if we could have the source popped up on a public GitHub repo (with a number of developers granted access), so in the future issues like this can be rectified -- samtar talk or stalk 09:19, 25 July 2016 (UTC)
- I have dropped Madman a line by email and asked him to join this conversation. --Dweller (talk) Become old fashioned! 09:53, 25 July 2016 (UTC)
- I am looking into this. I may not be editing much recently, but I do see my talk page, so let's not refer to me as an "absent" bot operator, if you please. v/r, — madman 12:47, 25 July 2016 (UTC)
- The e-mail was not in error. If you did not return to editing by August 1st, then as of August 1st you would have been a year inactive (with last edit July 5th). I know the date math isn't exactly intuitive (I've been over it enough times), but it's correct. v/r, — madman 12:58, 25 July 2016 (UTC)
- One issue I do see is that the inactive list is e-mailed at 00:00 UTC and then updated at 01:00 UTC; if someone returned to editing within the last twenty-four hours (as you did), that may not be reflected immediately. I'll switch those two crontab entries and consider this issue resolved. v/r, — madman 13:05, 25 July 2016 (UTC)