User talk:Legoktm/May 2019

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

ArbCom 2019 special circular

Icon of a white exclamation mark within a black triangle
Administrators must secure their accounts

The Arbitration Committee may require a new RfA if your account is compromised.

View additional information

This message was sent to all administrators following a recent motion. Thank you for your attention. For the Arbitration Committee, Cameron11598 02:47, 4 May 2019 (UTC)

Administrator account security (Correction to Arbcom 2019 special circular)

ArbCom would like to apologise and correct our previous mass message in light of the response from the community.

Since November 2018, six administrator accounts have been compromised and temporarily desysopped. In an effort to help improve account security, our intention was to remind administrators of existing policies on account security — that they are required to "have strong passwords and follow appropriate personal security practices." We have updated our procedures to ensure that we enforce these policies more strictly in the future. The policies themselves have not changed. In particular, two-factor authentication remains an optional means of adding extra security to your account. The choice not to enable 2FA will not be considered when deciding to restore sysop privileges to administrator accounts that were compromised.

We are sorry for the wording of our previous message, which did not accurately convey this, and deeply regret the tone in which it was delivered.

For the Arbitration Committee, -Cameron11598 21:03, 4 May 2019 (UTC)

Administrators' newsletter – May 2019

News and updates for administrators from the past month (April 2019).

Guideline and policy news

Technical news

  • XTools Admin Stats, a tool to list admins by administrative actions, has been revamped to support more types of log entries such as AbuseFilter changes. Two additional tools have been integrated into it as well: Steward Stats and Patroller Stats.

Arbitration

  • In response to the continuing compromise of administrator accounts, the Arbitration Committee passed a motion amending the procedures for return of permissions (diff). In such cases, the committee will review all available information to determine whether the administrator followed "appropriate personal security practices" before restoring permissions; administrators found failing to have adequately done so will not be resysopped automatically. All current administrators have been notified of this change.
  • Following a formal ratification process, the arbitration policy has been amended (diff). Specifically, the two-thirds majority required to remove or suspend an arbitrator now excludes (1) the arbitrator facing suspension or removal, and (2) any inactive arbitrator who does not respond within 30 days to attempts to solicit their feedback on the resolution through all known methods of communication.

Miscellaneous


Sent by MediaWiki message delivery (talk) 00:37, 5 May 2019 (UTC)

16:27, 6 May 2019 (UTC)

Bot misread

TFA-to-be was moved and moved back, the bot just protected the wrong article Tropical Depression Nineteen-E, instead of Tropical Depression Nineteen-E (2018). I have no idea if intervention is needed or if the bot will "learn". --Gerda Arendt (talk) 17:10, 8 May 2019 (UTC)

00:48, 14 May 2019 (UTC)

13:03, 20 May 2019 (UTC)

15:33, 27 May 2019 (UTC)

A possible bot

Hi Legoktm, I've been looking at trying to implement a similar function to legobot over at WikiJournals. We have a tracking table for articles in progress that has to be updated manually. I keep thinking that there must be a bot-based solution but I don't have skills in that area. Is it the sort of thing you'd be able to help in building something lightweight (or could you suggest someone with those sorts of skills?). Any help or ideas appreciated! T.Shafee(Evo&Evo)talk 04:51, 30 May 2019 (UTC)

The Signpost: 31 May 2019