Jump to content

User talk:Fluffernutter/Archive 38

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Archive 35Archive 36Archive 37Archive 38Archive 39Archive 40Archive 45

18:16, 23 April 2018 (UTC)

The Signpost: 26 April 2018

16:18, 30 April 2018 (UTC)

Administrators' newsletter – May 2018

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

Administrator changes

added None
removed ChochopkCoffeeGryffindorJimpKnowledge SeekerLankiveilPeridonRjd0060

Guideline and policy news

  • The ability to create articles directly in mainspace is now indefinitely restricted to autoconfirmed users.
  • A proposal is being discussed which would create a new "event coordinator" right that would allow users to temporarily add the "confirmed" flag to new user accounts and to create many new user accounts without being hindered by a rate limit.

Technical news

  • AbuseFilter has received numerous improvements, including an OOUI overhaul, syntax highlighting, ability to search existing filters, and a few new functions. In particular, the search feature can be used to ensure there aren't existing filters for what you need, and the new equals_to_any function can be used when checking multiple namespaces. One major upcoming change is the ability to see which filters are the slowest. This information is currently only available to those with access to Logstash.
  • When blocking anonymous users, a cookie will be applied that reloads the block if the user changes their IP. This means in most cases, you may no longer need to do /64 range blocks on residential IPv6 addresses in order to effectively block the end user. It will also help combat abuse from IP hoppers in general. This currently only occurs when hard-blocking accounts.
  • The block notice shown on mobile will soon be more informative and point users to a help page on how to request an unblock, just as it currently does on desktop.
  • There will soon be a calendar widget at Special:Block, making it easier to set expiries for a specific date and time.

Arbitration

Obituaries

  • Lankiveil (Craig Franklin) passed away in mid-April. Lankiveil joined Wikipedia on 12 August 2004 and became an administrator on 31 August 2008. During his time with the Wikimedia community, Lankiveil served as an oversighter for the English Wikipedia and as president of Wikimedia Australia.

16:28, 7 May 2018 (UTC)

Help us design granular blocks!

Hello :-) The Anti-Harassment Tools team at the Wikimedia Foundation will start building these granular blocking tools in a few weeks and we've asked WMF designer Alex Hollender to help us make some wireframes so the tools are intuitive to MediaWiki users.

We have a first draft of how we think this tool should work. You can read the full proposed implementation here but here are the significant parts:

  • Granular blocks (page, category, namespace, and file uploading) will be built on top of Special:Block. These blocks will function as if they were regular blocks and allow for the same options, but only take effect on specific pages.
  • We will add a new checkbox for "Block this user from the whole site" which will be checked by default. When it is unchecked the admin will be able to specify which pages, categories, and/or namespaces the user should be blocked from editing.
  • Granular blocks can be combined and/or overlap. (For example, a user could be simultaneously blocked from editing the articles Rain, Thunder, Lightning, and all pages inside the Category:Weather.)
  • Only one block is set at a time, to adjust what the user is blocked from the administrator would have to modify the existing block.
  • Block logs should display information about the granular block
  • When a blocked user attempts to edit an applicable page, they should see a block warning message which include information on their block (reason, expiration, what they are blocked from, etc.)
  • If a category is provided, the blocked user cannot edit either the category page itself and all pages within the category.
  • If the File: namespace is blocked, the user should not be allowed to upload files.

We like this direction because it builds on top of the existing block system, both a technical and usability wise. Before we get too far along with designs and development we'd like to hear from you about our prosposal:

  1. What do you think of the proposed implementation?
  2. We believe this should be an expansion of Special:Block, but it has been suggested that this be a new special page. What are your thoughts?
  3. Should uploading files be combined with a File namespace block, or as a separate option? (For example, if combined, when a user is blocked from the File namespace, they would neither be able to edit any existing pages in the File namespace nor upload new files.)
  4. Should there be a maximum number of things to be blocked from? Or should we leave it up to admin discretion?

We appreciate your feedback on this project's talk page or by email. For the Anti-Harassment Tools team, SPoore (WMF) (talk) , Trust and Safety Specialist, Community health initiative (talk) 20:54, 9 May 2018 (UTC)

Roses are red,
Good message links are blue,
My proofreading stinks,
So here's a good link for you SPoore (WMF), Trust & Safety, Community health initiative (talk) 16:32, 10 May 2018 (UTC)

.

22:23, 14 May 2018 (UTC)

17:34, 21 May 2018 (UTC)

The Signpost: 24 May 2018

The Signpost: 24 May 2018

12:40, 29 May 2018 (UTC)

Administrators' newsletter – June 2018

News and updates for administrators from the past month (May 2018).

Administrator changes

added None
removed Al Ameer sonAliveFreeHappyCenariumLupoMichaelBillington

Guideline and policy news

Technical news

  • IP-based cookie blocks should be deployed to English Wikipedia in June. This will cause the block of a logged-out user to be reloaded if they change IPs. This means in most cases, you may no longer need to do /64 range blocks on residential IPv6 addresses in order to effectively block the end user. It will also help combat abuse from IP hoppers in general. For the time being, it only affects users of the desktop interface.
  • The Wikimedia Foundation's Anti-Harassment Tools team will build granular types of blocks in 2018 (e.g. a block from uploading or editing specific pages, categories, or namespaces, as opposed to a full-site block). Feedback on the concept may be left at the talk page.
  • There is now a checkbox on Special:ListUsers to let you see only users in temporary user groups.
  • It is now easier for blocked mobile users to see why they were blocked.

Arbitration

  • A recent technical issue with the Arbitration Committee's spam filter inadvertently caused all messages sent to the committee through Wikipedia (i.e. Special:EmailUser/Arbitration Committee) to be discarded. If you attempted to send an email to the Arbitration Committee via Wikipedia between May 16 and May 31, your message was not received and you are encouraged to resend it. Messages sent outside of these dates or directly to the Arbitration Committee email address were not affected by this issue.

Miscellaneous


21:54, 4 June 2018 (UTC)

June 2018 GOCE newsletter

Guild of Copy Editors June 2018 News

Welcome to the June 2018 GOCE newsletter, in which you will find Guild updates since the February edition. Progress continues to be made on the copyediting backlog, which has been reduced to 7 months and reached a new all-time low. Requests continue to be handled efficiently this year, with 272 completed by the end of May (an average completion time of 10.5 days). Fewer than 10% of these waited longer than 20 days, and the longest wait time was 29 days.

Wikipedia in general, and the Guild in particular, experienced a deep loss with the death on 20 March of Corinne. Corinne (a GOCE coordinator since 1 July 2016) was a tireless aide on the requests page, and her peerless copyediting is a part of innumerable GAs and FAs. Her good cheer, courtesy and tact are very much missed.

March drive: The goal was to remove June, July and August 2017 from our backlog and all February 2018 Requests (a total of 219 articles). This drive was an outstanding success, and by the end of the month all but eight of these articles were cleared. Of the 33 editors who signed up, 19 recorded 277 copy edits (425,758 words).

April blitz: This one-week copy-editing blitz ran from 15 through 21 April, focusing on Requests and the last eight articles tagged in August 2017. At the end of the week there were only 17 pending requests, with none older than 17 days. Of the nine editors who signed up, eight editors completed 22 copy edits (62,412 words).

May drive: We set out to remove September, October and November 2017 from our backlog and all April 2018 Requests (a total of 298 articles). There was great success this month with the backlog more than halved from 1,449 articles at the beginning of the month to a record low of 716 articles. Officially, of the 20 who signed up, 15 editors recorded 151 copy edits (248,813 words).

Coordinator elections: It's election time again. Nominations for Guild coordinators (who will serve a six-month term for the second half of 2018) have begun, and will close at 23:59 UTC on 15 June. All Wikipedia editors in good standing are eligible, and self-nominations are encouraged. Voting will take place between 00:01 UTC on 16 June and 23:59 UTC on 30 June.

June blitz: Stay tuned for this one-week copy-editing blitz, which will take place in mid-June.

Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators: Corinne, Jonesey95, Miniapolis, Reidgreg and Tdslk.

To discontinue receiving GOCE newsletters, please remove your name from our mailing list.

MediaWiki message delivery (talk) 13:26, 5 June 2018 (UTC)

21:55, 11 June 2018 (UTC)

21:47, 18 June 2018 (UTC)

23:10, 25 June 2018 (UTC)

The Signpost: 29 June 2018

00:46, 3 July 2018 (UTC)

Administrators' newsletter – July 2018

News and updates for administrators from the past month (June 2018).

Administrator changes

added PbsouthwoodTheSandDoctor
readded Gogo Dodo
removed AndrevanDougEVulaKaisaLTony FoxWilyD

Bureaucrat changes

removed AndrevanEVula

Guideline and policy news

  • An RfC about the deletion of drafts closed with a consensus to change the wording of WP:NMFD. Specifically, a draft that has been repeatedly resubmitted and declined at AfC without any substantial improvement may be deleted at MfD if consensus determines that it is unlikely to ever meet the requirements for mainspace and it otherwise meets one of the reasons for deletion outlined in the deletion policy.
  • A request for comment closed with a consensus that the {{promising draft}} template cannot be used to indefinitely prevent a WP:G13 speedy deletion nomination.

Technical news

  • Starting on July 9, the WMF Security team, Trust & Safety, and the broader technical community will be seeking input on an upcoming change that will restrict editing of site-wide JavaScript and CSS to a new technical administrators user group. Bureaucrats and stewards will be able to grant this right per a community-defined process. The intention is to reduce the number of accounts who can edit frontend code to those who actually need to, which in turn lessens the risk of malicious code being added that compromises the security and privacy of everyone who accesses Wikipedia. For more information, please review the FAQ.
  • Syntax highlighting has been graduated from a Beta feature on the English Wikipedia. To enable this feature, click the highlighter icon () in your editing toolbar (or under the hamburger menu in the 2017 wikitext editor). This feature can help prevent you from making mistakes when editing complex templates.
  • IP-based cookie blocks should be deployed to English Wikipedia in July (previously scheduled for June). This will cause the block of a logged-out user to be reloaded if they change IPs. This means in most cases, you may no longer need to do /64 range blocks on residential IPv6 addresses in order to effectively block the end user. It will also help combat abuse from IP hoppers in general. For the time being, it only affects users of the desktop interface.

Miscellaneous

  • Currently around 20% of admins have enabled two-factor authentication, up from 17% a year ago. If you haven't already enabled it, please consider doing so. Regardless if you use 2FA, please practice appropriate account security by ensuring your password is secure and unique to Wikimedia.