Archives
August 2018 – present January 2018 – July 2018 July 2017 – December 2017 October 2016 – June 2017 August 2015 – September 2016 August 2014 – July 2015 August 2013 – July 2014 November 2012 – July 2013 April 2012 – October 2012 November 2011 – March 2012 April 2011 – October 2011 December 2010 – March 2011 September 2010 – November 2010 April 2010 – August 2010 November 2009 – March 2010

Thanks for uploading File:EnerNOC Logo.png. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).

Note that any non-free images not used in any articles will be deleted after seven days, as described in section F5 of the criteria for speedy deletion. Thank you. --B-bot (talk) 17:28, 1 April 2019 (UTC)[reply]

Hi please hide my Ip address: [REDACTED - Oshwah] from this page: https://en.wikipedia.org/wiki/Khaled_Juffali without removing content added if possible — Preceding unsigned comment added by Quantom122 (talk • contribs) 14:33, 3 April 2019 (UTC)[reply]

Thanks for cleaning up at ANI. Can I also trouble you to hide Special:Permalink/891316983 (content and edit summary)? Thanks, --DannyS712 (talk) 04:35, 7 April 2019 (UTC)[reply]

Sure thing, thanks for pointing it out! GorillaWarfare (talk) 04:38, 7 April 2019 (UTC)[reply]

No problem. Thanks for hiding it. Also, on the same topic (before I forget, since I won't be able to refresh my memory) is it a COI to give an IP a {{Uw-npa4im}} warning if I was the target? Thanks, --DannyS712 (talk) 04:39, 7 April 2019 (UTC)[reply]

Nope, being the target of personal attacks doesn't make you involved in any way. GorillaWarfare (talk) 04:40, 7 April 2019 (UTC)[reply]

Good to know. Thanks again, --DannyS712 (talk) 04:45, 7 April 2019 (UTC)[reply]

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

Administrator changes Reaper Eternal • ThaddeusB Bogdangiusca • Christopher Parham • Necrothesp • Schneelocke • Siroxo • Sarah Mentifisto → Lofty abyss Interface administrator changes Mr. Stradivarius

Bureaucrat changes DeltaQuad Kingturtle

Technical news

• In Special:Preferences under "Appearance" → "Advanced options", there is now an option to show a confirmation prompt when clicking on a rollback link.
• The Wikimedia Foundation's Community health initiative plans to design and build a new user reporting system to make it easier for people experiencing harassment and other forms of abuse to provide accurate information to the appropriate channel for action to be taken. Please see meta:Community health initiative/User reporting system consultation 2019 to provide your input on this idea.

Arbitration

• The Arbitration Committee clarified that the General 1RR prohibition for Palestine-Israel articles may only be enforced on pages with the {{ARBPIA 1RR editnotice}} edit notice.

Miscellaneous

• Two more administrator accounts were compromised. Evidence has shown that these attacks, like previous incidents, were due to reusing a password that was used on another website that suffered a data breach. If you have ever used your current password on any other website, you should change it immediately. All admins are strongly encouraged to enable two-factor authentication, please consider doing so. Please always practice appropriate account security by ensuring your password is secure and unique to Wikimedia.
• As a reminder, according to WP:NOQUORUM, administrators looking to close or relist an AfD should evaluate a nomination that has received few or no comments as if it were a proposed deletion (PROD) prior to determining whether it should be relisted.

For Max(imus) and you. qedk (t 桜 c) 17:05, 12 April 2019 (UTC)[reply]

Why thank you! Not sure how Max(imus) would feel about strawberries, but I sure like them :) GorillaWarfare (talk) 17:19, 12 April 2019 (UTC)[reply]

How do I supply a source for adding family information? I am a relative and have first hand knowledge of this family. Leona Goodell (talk) 02:35, 13 April 2019 (UTC)[reply]

as to why the voting of arbitrators (i.e. the support/oppose/abstain/recuse tally) in private appeals aren't disclosed? ∯WBG^converse 06:52, 15 April 2019 (UTC)[reply]

I'm actually not sure -- I think we may have disclosed tallies in the past on a per-case basis, but it's not common practice. GorillaWarfare (talk) 17:36, 15 April 2019 (UTC)[reply]

In that case, I don't see any reason as to why the common practice can't be changed. You might remember the drama-fest w.r.t to the premises of the first question over here. ∯WBG^converse 05:49, 16 April 2019 (UTC)[reply]

The better place to discuss this would probably be at WT:ARBCOM where all the arbs can see it. GorillaWarfare (talk) 16:22, 16 April 2019 (UTC)[reply]

May 2019, Volume 5, Issue 5, Numbers 107, 108, 118, 119, 120, 121 Hello and welcome to the May events of Women in Red! Please join us for these virtual events: New topics: "May" women / Mayors / Environentalists Geofocus: CEE countries Continuing initiatives: Suffrage / #1day1woman Other ways you can participate: Help us plan our future events: Ideas Cafe Join the conversations on our talkpage Follow us on Twitter: @wikiwomeninred Subscription options: Opt-in/Opt-out

--Megalibrarygirl (talk) 16:17, 27 April 2019 (UTC) via MassMessaging[reply]

Hello, GorillaWarfare. Please check your email; you've got mail!
It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the {{You've got mail}} or {{ygm}} template.Funcrunch (talk) 22:36, 28 April 2019 (UTC)[reply]

Administrators must secure their accounts The Arbitration Committee may require a new RfA if your account is compromised. Use strong, unique passwords for your Wikipedia account and associated email Change your password now if your Wikipedia account password or email password is reused on another website, exposed, or weak Enable two-factor authentication now for improved security

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:45, 4 May 2019 (UTC) Template:Z152[reply]

Thanks for uploading File:Enso Group logo.jpg. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).

Note that any non-free images not used in any articles will be deleted after seven days, as described in section F5 of the criteria for speedy deletion. Thank you. --B-bot (talk) 17:27, 4 May 2019 (UTC)[reply]

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) Template:Z83[reply]

Hi GW. What a horrible CF. [And all this comes without hugely digging through heaps of AC pages, as I simply neither have the time nor patience. Something has gone horribly wrong here. These days I keep out of enWP politics and just potter along with administrative bitsies. 1) Why is ArbCom even discussing this? It is not within the scope of AC, as I know it. 2) How did the first email come about? Let alone be sent? 3) How did the subsequent email come about and semi-justify the first? Should have been a complete retraction, nothing more.

Looks like you/we need to fix the AC house. Both in getting it back to the AC's scope, and managing what the personnel attached to AC are doing. As a long term admin, that is pretty disappointing. We are a consensus, not and AC has a scope within which to work. And I am not going to do individual blame, I am looking to solutions. [And it doesn't need a personal explanation, it is me expressing a PoV without getting entrenched in enWP politics, as those days are in the past.] — billinghurst sDrewth 03:37, 5 May 2019 (UTC)[reply]

Hmm, and I just saw special:permalink/891851004#Return_of_permissions_for_compromised_administrator_accounts. How is this part of AC? I hope that the bureaucrats throw this out as overreach. — billinghurst sDrewth 03:42, 5 May 2019 (UTC)[reply]

(edit conflict) @Billinghurst: There's a fair bit of discussion over at WT:ACN if you've not seen it. To answer your questions: 1) The ArbCom does handle desysoppings in the case of admin compromise (and in other situations), as it has for years. Typically we've just restored admin permissions once people have regained access to their admin account, but there have been concerns recently about administrators inadequately securing their accounts after account compromise. 2) There have been six compromised admin accounts in recent history, and more if you go back into slightly less recent history, that have come about from poor account security. The first email was drafted by an arbitrator and then submitted for discussion among the rest of the committee. 3) Same process for the second email. I disagree with you that the note should have been retracted entirely; the tone was poor and the bullet point about 2FA didn't adequately convey that it remains optional, but the substance of the message is important. GorillaWarfare (talk) 03:47, 5 May 2019 (UTC)[reply]

To reply to your addition that we edit conflicted on, the bureaucrats can't really "throw it out" per se—there is no ratification process by the bureaucrats or anything like that. I suppose they could refuse to resysop administrators when we asked them to, but that would be an odd change given they've been doing so as long as I can remember. Adding the option to not resysop a compromised admin more or less automatically is putting more of the decision in the community's hands than before, not less. GorillaWarfare (talk) 03:49, 5 May 2019 (UTC)[reply]

This should be community consensus, not the AC consensus and edict. The AC should be putting recommendations to the community for their consensus to how we the community operate, not by AC edict. This is rule creep and authority creep, and the AC should be well aware of this shift in power and pushing hard against it.

Any bureaucrat worth a pinch of shit would be asking any returning admin who lost control of their account to demonstrate how they have better secured their account, and showing compliance. This is not something that is arbitration. — billinghurst sDrewth 04:04, 5 May 2019 (UTC)[reply]

The removal of rights that AC adopted was "temporary" that you have taken it further, is unreasonable. Please check the 2009 adaptation. — billinghurst sDrewth 04:07, 5 May 2019 (UTC)[reply]

@Billinghurst: I don't particularly appreciate your implication that I've been unaware of a procedure I've been responsible for following for several years. Have you seen Joe Roe's 15:43, 4 May 2019 comment at WT:ACN? It sums up my opinions on this quite well. I'd recommend moving this conversation to that page, anyway—I am one member of a larger Committee, and you seem to be addressing the Committee as a whole in these comments. GorillaWarfare (talk) 04:14, 5 May 2019 (UTC)[reply]

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

Administrator changes HickoryOughtShirt?4 • RexxS Necrothesp Bratsche • Kyle Barbour • Kzollman • Madman Interface administrator changes Pharos

Bureaucrat changes Primefac CheckUser changes Reaper Eternal

Guideline and policy news

• A request for comment concluded that creating pages in the portal namespace should be restricted to autoconfirmed users.
• Following a request for comment, the subject-specific notability guideline for pornographic actors and models (WP:PORNBIO) was removed; in its place, editors should consult WP:ENT and WP:GNG.

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

• A request for comment is currently open to amend the community sanctions procedure to exclude non XfD or CSD deletions.
• A proposal to remove pre-2009 indefinite IP blocks is currently open for discussion.

I came here expecting to thank a burly, alpha male with hair on his chest and a large medallion for being a good role model in the fetid swamp of the Article on Gab, and instead I'm thanking this other person. Now I have to rewire my brain to accommodate this new information. I appreciate your balance and fairness.Tym Whittier (talk) 04:50, 9 May 2019 (UTC)[reply]

I get that a lot... Thanks for being willing to take a step back and cool off. GorillaWarfare (talk) 04:54, 9 May 2019 (UTC)[reply]

wtf you're a girl? and you're administrator, checkuser, oversighter, and arbitrator and they dont even let me be a fking template editor. this is so unfair, this is sexisist. --Eng. M.Bandara-Talk 00:33, 13 May 2019 (UTC)[reply]