User talk:MusikAnimal/Archive 34

Archive 30

←

Archive 32

Archive 33

Archive 34

Archive 35

Archive 36

→

Archive 40

This week's article for improvement (week 47, 2016)

A cleaning sponge Hello, MusikAnimal. The following is WikiProject Today's articles for improvement's weekly selection: Sponge (material) Please be bold and help to improve this article! Previous selections: Dress • Sword dance Get involved with the TAFI project. You can: Nominate an article • Review nominations Posted by: MusikBot talk 00:07, 21 November 2016 (UTC) using MediaWiki message delivery (talk) on behalf of WikiProject TAFI •

Strange edit by MusikBot

[1]

HTH,

Samsara 00:24, 21 November 2016 (UTC)

@Samsara: That is strange. Thanks for letting me know! The page is in the Category:Wikipedia pages with incorrect protection templates category, which the bot goes off of, but I believe that's because the date is missing from the {{pp-protected}} template. The bot should have left it alone, despite this. Will look more into it!

I did want to point out however that on enwiki page moves are restricted to confirmed users, so you need not add this level of protection. Best — MusikAnimal ^talk 01:02, 21 November 2016 (UTC)

Ha, yes, I knew that and seem to have briefly forgotten about it. Thanks for reminding me. OTOH, I think it makes sense to keep the "unlock further options" checkbox unchecked for easier future elevation to ECP, so I think I will keep doing that as a matter of good practice. However, you are right to point out that it was superfluous in this specific case. Samsara 01:25, 21 November 2016 (UTC)

Tech News: 2016-47

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Administrators, bureaucrats, oversighters and checkusers can now use two-factor authentication. This makes their Wikimedia accounts more secure. This can be turned on in Special:Preferences. There are discussions on how to best turn it on for everyone. [2]
• You can now search for file properties. For example you can search for media type, how big a file is or what resolution it has. [3]
• The latest Collaboration team products newsletter has been published. It has more details about their work than Tech News has.

Problems

• A hacker group is hacking Wikimedia accounts. They can probably do this because users have the same passwords on Wikimedia wikis as on other sites. Please have a password you use only on the Wikimedia wikis and nowhere else. This is especially important for administrators, bureaucrats, oversighters and checkusers. These users can also turn on two-factor authentication. [4]

Changes this week

• There is no new MediaWiki version this week.
• RevisionSlider will be a default feature on German, Arabic and Hebrew Wikipedia. This will happen on 22 November. It will come to other wikis later. [5][6][7]

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 22 November at 19:00 (UTC). See how to join.

Future changes

• It will be possible to do cross-wiki search. The developers who work on this are looking for communities that want to test this. [8]
• Hovercards will leave the beta stage. The Wikimedia Foundation Reading Web team wants communities to set Hovercards as a default option for readers who are not logged in. Communities that are interested can say so on the Hovercards talk page. [9]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

15:33, 21 November 2016 (UTC)

ArbCom Elections 2016: Voting now open!

Hello, MusikAnimal. Voting in the 2016 Arbitration Committee elections is open from Monday, 00:00, 21 November through Sunday, 23:59, 4 December to all unblocked users who have registered an account before Wednesday, 00:00, 28 October 2016 and have made at least 150 mainspace edits before Sunday, 00:00, 1 November 2016.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2016 election, please review the candidates' statements and submit your choices on the voting page. MediaWiki message delivery (talk) 22:08, 21 November 2016 (UTC)

Robert Sepúlveda Jr. again

Remember semi-protecting the page recently? Seems the IP-hopping sock has been keeping an eye on its protection. They made the exact same edit they've been making even before your bot removed the {{pp-sock}} template. I've undone it again and asked for indefinite semi at WP:RPP, as the IP is quite adamant that these edits be made, even requesting them on the talk page while the article was semied. Would you mind taking care of my RPP request? — Gestrid (talk) 02:25, 22 November 2016 (UTC)

 Done A bit too soon for indefinite semi, let's try shorter periods first. Thanks for the report — MusikAnimal ^talk 07:11, 22 November 2016 (UTC)

RevDel might be in order

https://en.wikipedia.org/w/index.php?title=Peter_Siddle&type=revision&diff=750966111&oldid=750966058 Yintan  16:53, 22 November 2016 (UTC)

 Done I'd say so! Thanks — MusikAnimal ^talk 17:05, 22 November 2016 (UTC)

Saturday December 3: Contemporary Chinese Art Edit-a-thon @ Guggenheim

Saturday December 3: Contemporary Chinese Art Edit-a-thon @ Guggenheim

On Saturday December 3, 2016, in conjunction with a global campaign, the Guggenheim will host its fifth Wikipedia edit-a-thon—or, #guggathon—to enhance Wikipedia's coverage of modern and contemporary artists from Greater China. The event will cap off Wikipedia Asian Month, an online campaign dedicated to augmenting Asian content on Wikipedia throughout November. New and experienced editors are welcome. The event will include a training session for participants who are new to Wikipedia, and Wikipedia specialists will be on hand to provide basic instruction and editing support. Editors are invited to view the exhibition Tales of Our Time following the event. The Guggenheim aims to raise awareness of the artists featured in the Tales of Our Time exhibition supported by The Robert H. N. Ho Family Foundation Chinese Art Initiative, and build on the model of campaigns like the Wikipedia Edit-a-thon at the Guggenheim: Women in Architecture, Wikipedia Edit-a-thon at the Guggenheim: Contemporary Art of the Middle East and North Africa, and Art+Feminism. Saturday December 3: Contemporary Chinese Art Edit-a-thon @ Guggenheim Time: 11:00 am - 3:00 pm Location: Solomon R. Guggenheim Museum. 1071 Fifth Ave, Manhattan. Enter at the 88th Street entrance via the ramp at 88th Street and Fifth Avenue. RSVP: on Meetup.com or on Wikipedia Newcomers are very welcome! Bring your friends and colleagues! --Pharos (talk) 09:46, 23 November 2016 (UTC)

(You can subscribe/unsubscribe from future notifications for NYC-area events by adding or removing your name from this list.)

Massviews External links

Hi MusikAnimal! I'd like to use Massviews to search for pageviews for a specific URL, rather than a URL pattern, but I'm having some trouble making that work. When I search a specific URL (say http://bbc.co.uk/bach, which is linked to twice on the English Wikipedia), I get "no data found". Any help would be appreciated. Sam Walton (talk) 10:16, 23 November 2016 (UTC)

@Samwalton9: I got it to work by removing the protocol [10], but the tool should parse it. I will file a bug! Also it's only returning results in the mainspace, which I think did because that's probably desired by most. Maybe that should be an option? — MusikAnimal ^talk 16:02, 23 November 2016 (UTC)

Good to know - thanks! Perhaps that should be an option, though in finding this issue I was only interested in mainspace. What about if the link is https? Without the protocol it seems to default to http. Sam Walton (talk) 16:06, 23 November 2016 (UTC)

Yep, that's a problem! Will fix soon, phab at phab:T151463. Thanks for letting me know! — MusikAnimal ^talk 16:13, 23 November 2016 (UTC)

80.1.199.33

This IP user is once again making persistent disruptive editing on 19 Kids and Counting. Thanks for your help. --Musdan77 (talk) 19:32, 22 November 2016 (UTC)

Blocked for 2 weeks. Best — MusikAnimal ^talk 20:09, 22 November 2016 (UTC)

I appreciate it -- but it looks like the person just changed to another IP address. --Musdan77 (talk) 20:22, 23 November 2016 (UTC)

Page protection it is! I've gone with two weeks — MusikAnimal ^talk 20:24, 23 November 2016 (UTC)

New Page Reviewer - RfC

Hi MusikAnimal. You are invited to comment at a further discussion on the implementation of this user right to patrol and review new pages that is taking place at Wikipedia:New pages patrol/RfC on patrolling without user right. Kudpung กุดผึ้ง (talk) 00:01, 24 November 2016 (UTC)

mediawiki-gateway

Hello! So I stumbled across a gem on github called mediawiki-gateway that apepars to be yours. If it isn't I apologize and you can disregard the rest of this message. You are one of the few editors I have found who uses Ruby for their bots. I'm just getting started with bots and am looking for some assistance. There is one problem I am having at the moment that I'm wondering if you have previously found a solution to. I am working on a few bots to clean up deprecated parameters from inside of template occurrences. As such I need to restrict my gsub! calls to just look at the code inside of a specific template. I haven't found a good way to do this yet. Is this something you have previously done? Would LOVE any assistance you are willing to give. :-) Thanks! --Zackmann08 (^{Talk to me}/_{What I been doing}) 17:56, 22 November 2016 (UTC)

@Zackmann08: That is my fork of the original mediawiki-gateway gem, yes. The original gem is lacking many features and probably doesn't work on enwiki anymore. There is also an official Ruby client. Neither will help you with your problem, I'm afraid. What you need is to carefully parse wikitext, which is never fun :( I use a combination of scan or match and regular expressions to do similar things (example). Rubular is an online tool that may help when building your regex (put variations of the template in the test string, and make sure your regex correctly acts on them). Ruby aside, there is a Python library to parse wikitext that may be of help, if you are comfortable with that language. AutoWikiBrowser might also have similar functionality, not sure. Hope this helps! — MusikAnimal ^talk 20:07, 22 November 2016 (UTC)

Well your gem is LOADS better than the original. I love some of the features you've added. I seem to be having some issues with authenticating using your gem though. Any idea what I'm doing wrong?

mw = MediaWiki::Gateway.new('https://en.wikipedia.org/w/api.php')
mw.login('Zackmann08','<password>')
MediaWiki::APIError: MediaWiki::APIError: API error: code 'warning', info 'API warning: Fetching a token via action=login is deprecated. Use action=query&meta=tokens&type=login instead.'

As for thge parsing of wikitext.... GAGGGG. Not excited about this but I'll see what I can do. I use regexr.com for testing my RegExs but I'll take a look at thinks you provided. Really appreciate them. If you're interested, feel free to take a look at the two bots I am working on: ZackBot & ZackBot 2. Thanks again! --Zackmann08 (^{Talk to me}/_{What I been doing}) 02:52, 23 November 2016 (UTC)

So I wanted to let you know that I found a solution to the problem I was having! Gotta love StackOverflow!!!

/(?=\{\{[Ii]nfobox\s[Tt]elevision)(\{\{(?>[^{}]++|\g<1>)*}})‌​/

got me what I needed. I'm curious, are you still actively developing that gem of yours? If so I might be interested in helping if you are interested. Would be awesome to add some functionality around templates. I'm just envisioning a function that would extract a template to a hash for example.... --Zackmann08 (^{Talk to me}/_{What I been doing}) 19:37, 23 November 2016 (UTC)

@Zackmann08: Nice! Glad you got it figured out :) Yes, I am still actively maintaining the gem. If you have anything to contribute by all means, make a pull request! Or use your own fork, but I might also want whatever you add to it :) For the record, I have been very bad and have not been writing tests for the things I've added, and hence won't ask that you do the same... manual testing is fine for me. I also have some "extensions", and helpful little methods in my tiny MusikBot library. E.g. get_revision_at_date, get_page_props, date utilities, etc. Much of this I should probably merge into the gem for use by others. I'll try to take care of that at some point.

For your warning when logging, try using Special:BotPasswords, I think that's what got rid of it for me. Either way it's just a warning and logging in should still work. Glad to see another Ruby bot out there! Cheers — MusikAnimal ^talk 20:05, 23 November 2016 (UTC)

Unfortunately using the BotPassword didn't solve the problem. It isn't just a warning but a full on error:

irb(main):069:0> mw.create('User:ZackBot\testing', 'Hello world!', summary: 'My first page')
MediaWiki::APIError: MediaWiki::APIError: API error: code 'warning', info 'API warning: The intoken parameter has been deprecated.'
	from /Users/zack/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/mediawiki-gateway-1.1.0/lib/media_wiki/gateway.rb:241:in `warning'
	from /Users/zack/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/mediawiki-gateway-1.1.0/lib/media_wiki/gateway.rb:221:in `get_response'
	from /Users/zack/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/mediawiki-gateway-1.1.0/lib/media_wiki/gateway.rb:142:in `block in make_api_request'
	from /Users/zack/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/mediawiki-gateway-1.1.0/lib/media_wiki/gateway.rb:194:in `call'
	from /Users/zack/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/mediawiki-gateway-1.1.0/lib/media_wiki/gateway.rb:194:in `block in http_send'
	from /Users/zack/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/rest-client-1.8.0/lib/restclient/request.rb:493:in `call'
	from /Users/zack/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/rest-client-1.8.0/lib/restclient/request.rb:493:in `process_result'
	from /Users/zack/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/rest-client-1.8.0/lib/restclient/request.rb:421:in `block in transmit'
	from /Users/zack/.rbenv/versions/2.2.4/lib/ruby/2.2.0/net/http.rb:853:in `start'
	from /Users/zack/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/rest-client-1.8.0/lib/restclient/request.rb:413:in `transmit'
	from /Users/zack/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/rest-client-1.8.0/lib/restclient/request.rb:176:in `execute'
	from /Users/zack/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/rest-client-1.8.0/lib/restclient/request.rb:41:in `execute'
	from /Users/zack/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/mediawiki-gateway-1.1.0/lib/media_wiki/gateway.rb:183:in `http_send'
	from /Users/zack/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/mediawiki-gateway-1.1.0/lib/media_wiki/gateway.rb:130:in `make_api_request'
	from /Users/zack/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/mediawiki-gateway-1.1.0/lib/media_wiki/gateway.rb:65:in `send_request'
	from /Users/zack/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/mediawiki-gateway-1.1.0/lib/media_wiki/gateway.rb:72:in `get_token'
	from /Users/zack/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/mediawiki-gateway-1.1.0/lib/media_wiki/gateway/pages.rb:99:in `create'
	from (irb):69
	from /Users/zack/.rbenv/versions/2.2.4/bin/irb:11:in `<main>'

If you have any thoughts let me know. Otherwise I'll just keep using the other gem for now. --Zackmann08 (^{Talk to me}/_{What I been doing}) 20:36, 23 November 2016 (UTC)

(←) @Zackmann08: Yeah... if you don't use bot passwords you should get a warning when logging in like Main-account login via action=login is deprecated, so maybe that's not it. Anyway, I used the following code and get no warnings:

  mw = MediaWiki::Gateway.new('https://en.wikipedia.org/w/api.php')
  mw.login('MusikBot@MusikBot', 'bot password')
  mw.edit('User:MusikBot/sandbox', 'testing')
  mw.create('User:MusikBot/sandbox2', 'testing')

Note the gem does throw errors when it encounters API warnings (not just API errors). I'm not sure why you're getting API warnings, but you can disable the gem from erroring out with ignorewarnings: true, like so:

  mw = MediaWiki::Gateway.new('https://en.wikipedia.org/w/api.php', ignorewarnings: true)

That will get you past your issue for now. Finally, I'm using mediawiki-gateway version 1.2.0, not 1.1.0. The only difference there however is I fixed it to actually handle edit conflicts (if you provide the right parameters to do so). The weird intoken warnings should have been fixed with this commit, which was the 1.1.0 release — MusikAnimal ^talk 21:17, 23 November 2016 (UTC)

Hmmm. I will look into your tips. Thanks! By the way... If you are interested in a laugh, check this out: Wikipedia:Articles for deletion/Pál Milkovics (2nd nomination)... --Zackmann08 (^{Talk to me}/_{What I been doing}) 00:46, 24 November 2016 (UTC)

Red Dawn

Disruptive IP continuing immediately after removal of page protection, I also made this report at RFPP, Happy holidays :) - Mlpearc (open channel) 16:26, 25 November 2016 (UTC)

Sigh... semi'd for 2 months. Best — MusikAnimal ^talk 16:50, 25 November 2016 (UTC)

- Mlpearc (open channel) 16:53, 25 November 2016 (UTC)

Patrolling without the user right

Patrols are perfectly possible without the New Page Reviewer right. At least that is what BU Rob13 has given he community to understand in his recent RFC. And as far as I know , that is correct. The new right doesn't prevent rubbish tagging or biting new users in any way, shape, or form. --Kudpung กุดผึ้ง (talk) 03:02, 26 November 2016 (UTC)

@Kudpung: We should continue with the existing discussion at WT:PERM I think... but anyway yes, of course patrolling is still possible. I can, as a non-NPR account (or even an anonymous user), go to any page and add {{db-g12}} seeing that it is a copyright violation. However I did not click on "mark this page as patrolled" because that link is not there anymore, nor did I use Twinkle or Page Curation (both of which effectively click on that link). So the formal log is gone unless you are a New Page Reviewer, which is required to mark the page as "patrolled" in the database. We have to literally search their contributions to find such patrols unless they are a New Page Reviewer. All due respect, but it was your idea to do this...? It is not a bad thing at all. You can think of it as a step up: Rubbish tagging as you say, is still possible, and always will be (without the extremely unlikely use of a disallowing edit filter, and even then there are workarounds). Meanwhile new users can no longer mark inappropriate pages as patrolled as if they were appropriate. Instead, they will inevitably be re-evaluated by New Page Reviewers. Similarly, the rubbish tags added by new users may be removed. Hopefully that makes sense — MusikAnimal ^talk 03:46, 26 November 2016 (UTC)

It all makes sense now - for now, thanks. Meanwhile new users can no longer mark inappropriate pages as patrolled as if they were appropriate. Instead, they will inevitably be re-evaluated by New Page Reviewers, that's the only good thing about it, because it's still going to be too late for the users who get bitten. Kudpung กุดผึ้ง (talk) 04:05, 26 November 2016 (UTC)

I wholeheartedly agree, but there's not much we can do. Outright disallowing patrolling by new users is the whole premise behind Rob's RFC (which he actually opposes :). We're still doing better, though! New Page Reviewer is a big step up. As the wiki grows there will be more issues, but we are resilient, and I'm confident the strength of the community will ensure the success of the project :D — MusikAnimal ^talk 04:21, 26 November 2016 (UTC)

Nightpedia

Is your Nightpedia script still functional? I tried to get it to work and it wasn't working for me. :-( Is there something I need to do to get it to work? --Zackmann08 (^{Talk to me}/_{What I been doing}) 04:20, 26 November 2016 (UTC)

@Zackmann08: It should! Do you see the "Nightpedia" link at the top-right, next to the Watchlist link? — MusikAnimal ^talk 04:22, 26 November 2016 (UTC)

I do not... Is there some other script that is required or a pre-requisite? --Zackmann08 (^{Talk to me}/_{What I been doing}) 04:26, 26 November 2016 (UTC)

Got it to work! I had to actually copy and paste the code. Importing it didn't seem to work. --Zackmann08 (^{Talk to me}/_{What I been doing}) 04:27, 26 November 2016 (UTC)

@Zackmann08: Hmm... maybe try moving the importScript to where you've copied/pasted the code (and remove the copied/pasted code)? There may be a conflict with your other scripts, where the time of loading matters — MusikAnimal ^talk 04:32, 26 November 2016 (UTC)

The Signpost: 4 November 2016

• News and notes: Arbitration Committee elections commence

• In the media: Roundup of news related to U.S. presidential election and more

• Blog: The top fifteen winning photos from Wiki Loves Earth

• Gallery: Around the world with Wiki Loves Monuments 2016

• Featured content: Featured mix

• Special report: Taking stock of the Good Article backlog

• Op-ed: Fundraising data should be more transparent

• Traffic report: President-elect Trump

* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 09:06, 26 November 2016 (UTC)

New Page Review - newsletter

Hello MusikAnimal,

Breaking the back of the backlog

We now have 804 New Page Reviewers! Most of you requested the user right to be able to do something about the huge backlog. Now it's time for action.

Mid July to 01 Oct 2016

If each reviewer does only 10 reviews a day over five days, the backlog will be down to zero and the daily input can then be processed by each reviewer doing only 2 or 3 reviews a day - that's about 5 minutes work!
Let's get that over and done with in time to relax for the holidays.

Second set of eyes

Not only are New Page Reviewers the guardians of quality of new articles, they are also in a position to ensure that pages are being correctly tagged for deletion and maintenance and that new authors are not being bitten. This is an important feature of your work. Read about it at the new Monitoring the system section in the tutorial.

Getting the tools we need - 2016 WMF Wishlist Survey: Please vote

With some tweaks to their look, and some additional features, Page Curation and New Pages Feed could easily be the best tools for patrollers and reviewers. We've listed most of what what we need at the 2016 WMF Wishlist Survey. Voting starts on 28 November - please turn out to make our bid the Foundation's top priority. Please help also by improving or commenting on our Wishlist entry at the Community Wishlist Survey. Many other important user suggestions are listed at at Page Curation.

---

Sent to all New Page Reviewers. Discuss this newsletter here. If you wish to opt-out of future mailings, please remove yourself from the mailing list. MediaWiki message delivery (talk) 09:16, 26 November 2016 (UTC) .

quarry

Hi Musik, I'm interested in running a quarry report for certain inactive users. Think I keep timing out on quarry due to not having a handy "last seen" table to join. Any hints? Example output would be a list of (user names, last edit timestamp) where (user is in group 'bots') and (last edit timestamp > n days before today). Any hints? — xaosflux ^Talk 05:11, 24 November 2016 (UTC)

@Xaosflux: I'm running into timeouts too, but I think you want something like: quarry:query/14340. See also the report for AWB bots at User:MusikBot II/AWBListMan/Report/Bot, if that's what you're after :) If not, I'm happy to modify the script to generate a report for what you need. Best — MusikAnimal ^talk 16:45, 25 November 2016 (UTC)

Thank you. — xaosflux ^Talk 16:47, 25 November 2016 (UTC)

@Xaosflux: And actually I need to re-run that report, the full version is at Special:PermaLink/749730698. Also I'm retrying the query without a limit at quarry:query/14339. It will take quite some time to finish, if it finishes at all! — MusikAnimal ^talk 16:49, 25 November 2016 (UTC)

I did to through the AWB bots the otherday and removed at least one where both the bot and the operator had been inactive for a while. Trying to generate inactive bots in general (not jsut AWB) to see if their oeprators have left and they should be deflagged - or if their operators have decided to retire their bots. — xaosflux ^Talk 16:53, 25 November 2016 (UTC)

Gotcha. Well if the 14339 query gets killed, I can write a script for you, if you want. What are you considering inactive? I went with no edits for 1 year — MusikAnimal ^talk 17:00, 25 November 2016 (UTC)

Something odd with that report (14354) for example results Mathbot 20151123210136 while Mathbot has current 2016 edits. — xaosflux ^Talk 17:06, 25 November 2016 (UTC)

Oops! Yeah that "rev_timestamp <=" clause doesn't do anything, because we want to make that comparison against the MAX(rev_timestamp), so yet another subquery... I think quarry:query/14340 might work. It sucks we have to wait so long to find out! As far as I can tell I'm going off the proper indexes — MusikAnimal ^talk 17:36, 25 November 2016 (UTC)

Okay seems to be working :) Will try querying for all bots again with quarry:query/14339. Let's hope it doesn't time out! — MusikAnimal ^talk 17:57, 25 November 2016 (UTC)

Looks like quarry couldn't handle it. — xaosflux ^Talk 04:46, 26 November 2016 (UTC)

Yes... I'm confident the query would have worked but alas there is a timeout! I can run a custom script for you. Hold tight... — MusikAnimal ^talk 04:48, 26 November 2016 (UTC)

@Xaosflux: You are going to be very busy for a while! 219 of the 370 bots have not edited in 365 days. Should I increase the offset? The list is at User:MusikBot/InactiveBots/Report :) — MusikAnimal ^talk 05:15, 26 November 2016 (UTC)

I will sort the list too... give me a few minutes — MusikAnimal ^talk 05:16, 26 November 2016 (UTC)

Sorted :) I can also make a regular automated report of this, if you would like! — MusikAnimal ^talk 05:24, 26 November 2016 (UTC)

Thank you - this is going to take some time to go through! — xaosflux ^Talk 13:05, 26 November 2016 (UTC)

Wikipedia:Bot_owners'_noticeboard#Inactive_bots_over_5_years - I started with the oldest - lets see if there is community push-back. — xaosflux ^Talk 15:00, 26 November 2016 (UTC)

Talkback

Is this in fact a bug? Can we replace the text link permanently with the horziontal Curation bar? This would not conflict with any claims that access to Twinkle is being eroded. Kudpung กุดผึ้ง (talk) 08:21, 26 November 2016 (UTC)

BTW. As far as I understand, at Phabricator they consider the populating of Page Curation with all the options from Twinkle to be complete. Could you take a look and compare ths list from Twinkle with what we have in Curation? I wanted to propose a new article for merging today and I couldn't. I'm beginning to see why people are treating my claims of Curation being a brilliant piece of software as a joke and are not using it.

Twinkle list

Cleanup and maintenance tags General cleanup {{cleanup}}: article may require cleanup > {{copy edit}}: article needs copy editing for grammar, style, cohesion, tone, and/or spelling > Potentially unwanted content {{close paraphrasing}}: article contains close paraphrasing of a non-free copyrighted source > {{copypaste}}: article appears to have been copied and pasted from a source > {{external links}}: article's external links may not follow content policies or guidelines > {{non-free}}: article may contain excessive or improper use of copyrighted materials > Structure, formatting, and lead section {{cleanup-reorganize}}: article may be in need of reorganization to comply with Wikipedia's layout guidelines > {{condense}}: article may have too many section headers dividing up its content > {{lead missing}}: article has no lead section and one should be written > {{lead rewrite}}: article lead section needs to be rewritten to comply with guidelines > {{lead too long}}: article lead section is too long and should be shortened > {{lead too short}}: article lead section is too short and should be expanded > {{sections}}: article needs to be broken into sections > {{very long}}: article is too long > Fiction-related cleanup {{all plot}}: article is almost entirely a plot summary > {{fiction}}: article fails to distinguish between fact and fiction > {{in-universe}}: article subject is fictional and needs rewriting from a non-fictional perspective > {{plot}}: plot summary in article is too long > General content issues Importance and notability {{notability}}: article's subject may not meet the notability guideline > Style of writing {{advert}}: article is written like an advertisement > {{essay-like}}: article is written like a personal reflection or opinion essay > {{fansite}}: article resembles a fansite > {{manual}}: article is written like a manual or guidebook > {{news release}}: article reads like a news release > {{prose}}: article is in a list format that may be better presented using prose > {{technical}}: article may be too technical for the uninitiated reader > {{tense}}: article is written in an incorrect tense > {{tone}}: tone of article is not appropriate > Sense (or lack thereof) {{confusing}}: article may be confusing or unclear > {{incomprehensible}}: article is very hard to understand or incomprehensible > {{unfocused}}: article lacks focus or is about more than one topic > Information and detail {{context}}: article provides insufficient context > {{expert needed}}: article needs attention from an expert on the subject > {{metricate}}: article exclusively uses non-SI units of measurement > {{overly detailed}}: article contains an excessive amount of intricate detail > {{undue}}: article lends undue weight to certain aspects of the subject but not others > Timeliness {{update}}: article needs additional up-to-date information added > Neutrality, bias, and factual accuracy {{autobiography}}: article is an autobiography and may not be written neutrally > {{COI}}: article creator or major contributor may have a conflict of interest > {{disputed}}: article has questionable factual accuracy > {{hoax}}: article may be a complete hoax > {{globalize}}: article may not represent a worldwide view of the subject > {{overcoverage}}: article has an extensive bias or disproportional coverage towards one or more specific regions > {{peacock}}: article may contain peacock terms that promote the subject without adding information > {{POV}}: article does not maintain a neutral point of view > {{recentism}}: article is slanted towards recent events > {{too few opinions}}: article may not include all significant viewpoints > {{weasel}}: article neutrality is compromised by the use of weasel words > Verifiability and sources {{BLP sources}}: BLP article needs additional sources for verification > {{BLP unsourced}}: BLP article has no sources at all (use BLP PROD instead for new articles) > {{one source}}: article relies largely or entirely upon a single source > {{original research}}: article has original research or unverified claims > {{primary sources}}: article relies too heavily on primary sources, and needs secondary sources > {{refimprove}}: article needs additional references or sources for verification > {{self-published}}: article may contain improper references to self-published sources > {{third-party}}: article relies too heavily on affiliated sources, and needs third-party sources > {{unreferenced}}: article has no references at all > {{unreliable sources}}: article's references may not be reliable sources > Specific content issues Language {{not English}}: article is written in a language other than English and needs translation > {{rough translation}}: article is poorly translated and needs cleanup > {{expand language}}: article can be expanded with material from a foreign-language Wikipedia > Links {{dead end}}: article has no links to other articles > {{orphan}}: article is linked to from no other articles > {{overlinked}}: article may have too many duplicate and/or irrelevant links > {{underlinked}}: article may require additional wikilinks > Referencing technique {{citation style}}: article has unclear or inconsistent inline citations > {{linkrot}}: article uses bare URLs for references, which are prone to link rot > {{more footnotes}}: article has some references, but insufficient in-text citations > {{no footnotes}}: article has references, but no in-text citations > Categories {{improve categories}}: article may require additional categories > {{uncategorized}}: article is uncategorized > Merging {{merge}}: article should be merged with another given article > {{merge from}}: another given article should be merged into this one > {{merge to}}: article should be merged into another given article > Informational {{GOCEinuse}}: article is currently undergoing a major copy edit by the Guild of Copy Editors > {{in use}}: article is undergoing a major edit for a short while > {{new unreviewed article}}: mark your own article for later review > {{under construction}}: article is currently in the middle of an expansion or major revamping >

Kudpung กุดผึ้ง (talk) 08:35, 26 November 2016 (UTC)

I will investigate! Some were left out for good reasons, but the merge tags might have been overlooked. Also I hate the talk back templates, by the way, pings work just fine :) — MusikAnimal ^talk 17:52, 26 November 2016 (UTC)

The ironic argument is that if there is a good reason to leave them out, then there are bad reasons for having them in Twinkle - which of course would defy all logic! Leaving features out 'for a good reason' totally defeats the purpose not only of having spent the time and money to develop a better alternative to Twinkle, but these 'left outs' are partly the very reasons why Page Curation never caught on (at least with the pre-Curation users).Kudpung กุดผึ้ง (talk) 21:53, 26 November 2016 (UTC)

Not quite: things like {{under construction}}, {{GOCEinuse}}, {{in use}}, etc, do not really pertain to the reviewing process, but are still useful to Twinkle users. {{new unreviewed article}} in particular is meant to be applied to your own article, which would not even be possible with Page Curation (you can't review your own page). The one other missing tag (other than the merge tags) is {{metricate}}, currently being used on all of two articles. For that I agree it should be removed from Twinkle. It's rarely used, and for Twinkle and Page Curation we want to limit the selection to commonly used tags, given there is an exhaustive list out there. The merge tags I think are not as straightforward to add, but I am going to try! — MusikAnimal ^talk 22:29, 26 November 2016 (UTC)

No one doubts the absolute necessity of Twnkle. I do of course naturally agree with your mentioned tags, I also agree that over the years literally hundreds of tags (and user warnings) have been invented and added on-the-fly to Twinkle (one argument, I suppose, why it's not a bad thing that the Page Curation code is only accessible to official devs).

The number of tags is now so so extreme that it is often quicker for me to write an ad hoc warning longhand than search for a suitable one in the Twinkle drop-down, which BTW due to the immense length of the list has now had it font size reduced to an unreadable size - even for my eyes that are now 20/20 following two, many thousand dollar 3-day hospital operations this month. Twinkle is in need of severe pruning, but that's not my mission, nevertheless after all these years as a busy maintenance worker and admin, I doubt whether I have ever used more than 10% of them. Possibly the list of tags also increased dramatically when Friendly and Twinkle were merged in 2011. Kudpung กุดผึ้ง (talk) 04:46, 27 November 2016 (UTC)

PS: On Curation, the 'Not English' tag is also incomplete. Unlike Twinkle, the box to insert the language is missing. Also, it does not always place the message on the creators tp.Kudpung กุดผึ้ง (talk) 06:18, 27 November 2016 (UTC)

This week's article for improvement (week 48, 2016)

Homework may include mathematical exercises Hello, MusikAnimal. The following is WikiProject Today's articles for improvement's weekly selection: Homework Please be bold and help to improve this article! Previous selections: Sponge (material) • Dress Get involved with the TAFI project. You can: Nominate an article • Review nominations Posted by: MusikBot talk 00:08, 28 November 2016 (UTC) using MediaWiki message delivery (talk) on behalf of WikiProject TAFI •

Tech News: 2016-48

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Changes this week

• When someone tries to log in to a blocked account they will be blocked by a cookie. This means their browser will be blocked even if they change their IP address. This makes it more difficult for returning vandals. [11]
• When you use Content Translation to adapt a template to a new translation it will work differently. You can adapt big templates such as infoboxes. Translators will have control over the template parameters. A first version of this is released this week. It is possible it will not work correctly with all templates. There will be more updates for this soon. [12]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 29 November. It will be on non-Wikipedia wikis and some Wikipedias from 30 November. It will be on all wikis from 1 December (calendar).
• Gadgets will have a new option called "hidden". This means you can register gadgets that can't be turned on or off from the preferences page. Hiding gadgets was already possible by using [rights=hidden]. You should now use [hidden] instead. [rights=hidden] in old gadgets should be changed to [hidden]. [13][14]

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 29 November at 19:00 (UTC). See how to join.

Future changes

• Tool Labs could get two new policies. One would be to be able to adopt tools without an active developer. The other would be a right to fork. There is a request for comment on Meta.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

21:17, 28 November 2016 (UTC)

PERM Preload

I don't want to start undoing your recent change - can you reincorporate the text from [15] here to the TE preload area? — xaosflux ^Talk 23:07, 28 November 2016 (UTC)

Whoopsies, sorry about that! I can re-add it later this evening (my time). The idea was to refractor all the preloads since they're otherwise the same. I should be able to do some templating magic to get this in for the TE preload, though. Will ping you when finished! — MusikAnimal ^talk 23:51, 28 November 2016 (UTC)

@Xaosflux: Done! — MusikAnimal ^talk 06:03, 29 November 2016 (UTC)

Something appears to have broken. See the appearance on WP:PERM. ~ Rob₁₃^Talk 10:30, 29 November 2016 (UTC)

Thank you. — xaosflux ^Talk 12:28, 29 November 2016 (UTC)

Re: BU Rob13, should be fixed. Best — MusikAnimal ^talk 17:40, 29 November 2016 (UTC)

Block of my account

Hi, I am User:Angelo.romano (long-time user and Wikipedia admin since years). I am writing you because I just discovered my account had been compromised and blocked by you as a consequence. I am therefore asking you if you could review my account situation, please. Feel free to contact me by email (angelo [dot] romano [AT] gmail [dot] com) to discuss it further, of course. Thank you, regards --90.74.141.34 (talk) 20:49, 29 November 2016 (UTC)

Another UAA question

I notice that response helper still has "only edits are to AFC/draft space" as an option. Per this discussion from 2013, this was basically an exemption to the policy thought up by one admin (who used be the most active admin at UAA but has since moved on) and never really was a real exemption.

Other than that, may I say I wish I had had this awesome tool back in 2009 when I started doing this, it makes this kind of work significantly less tedious. Beeblebrox (talk)

@Beeblebrox: Hehe, glad the script is of help! The options you see I took from {{UAA}}. If we remove it from there (and others agree with the change), I can remove it from the script. Best — MusikAnimal ^talk 20:09, 23 November 2016 (UTC)

That's fair enough. I do have one more request which hopefully is simple and uncontroversial. Is there any way to add an extra blank line when replying with response helper? The reports at UAA can very difficult to navigate when there's no spaces between them. Beeblebrox (talk) 06:09, 30 November 2016 (UTC)

Discussion at WP:ANI#Range block needed - LTA IP editor who reverts Eik Corell

You are invited to join the discussion at WP:ANI#Range block needed - LTA IP editor who reverts Eik Corell. Regarding an edit filter I think you helped with. --Cameron₁₁₅₉₈ ^(Talk) 03:19, 2 December 2016 (UTC)

Donald Trump filmography

Hi there, you said the following on my IP address's talk page:
<Start> Please refrain from making unconstructive edits to Wikipedia, as you did at Donald Trump filmography. Your edits appear to constitute vandalism and have been reverted. If you would like to experiment, please use the sandbox. Repeated vandalism can result in the loss of editing privileges. Thank you. — MusikAnimal ^talk 19:56, 9 November 2016 (UTC)

If this is a shared IP address, and you did not make the edits, consider creating an account for yourself so you can avoid further irrelevant notices.

<End>
I would like to inform you that my IP address is transferred to other people on a regular basis. This is done by my Internet provider. I have not made any edits on Wikipedia. Thanks. 86.45.66.67 (talk) 23:24, 3 December 2016 (UTC)

Apologies, you can ignore the warning. As the message says, consider creating an account for yourself so you can avoid further irrelevant notices — MusikAnimal ^talk 20:56, 4 December 2016 (UTC)

Edit summary with userRightsManager script

Currently, the edit summary just says "(done (using userRightsManager))" when using the script to mark a request as "done". I think the script should be modified to include the username between "/*" and "*/" in the edit summary, like this: "(→User:Username: done (using userRightsManager))". GeoffreyT2000 (talk, contribs) 17:32, 3 December 2016 (UTC)

I can add this! Thank you for the suggestion — MusikAnimal ^talk 20:25, 3 December 2016 (UTC)

 Done [16] — MusikAnimal ^talk 22:58, 4 December 2016 (UTC)

This week's article for improvement (week 49, 2016)

Three Martinis Hello, MusikAnimal. The following is WikiProject Today's articles for improvement's weekly selection: Three-martini lunch Please be bold and help to improve this article! Previous selections: Homework • Sponge (material) Get involved with the TAFI project. You can: Nominate an article • Review nominations Posted by: MusikBot talk 00:10, 5 December 2016 (UTC) using MediaWiki message delivery (talk) on behalf of WikiProject TAFI •

Suspected sockpuppet

[17] Are you serious? How uncourteous. I'm not anybody's sockpuppet. --El santacruzano (talk) 02:01, 5 December 2016 (UTC)

@El santacruzano: Sorry!! My mistake. I was careful who I blocked but apparently not careful who I tagged... — MusikAnimal ^talk 02:07, 5 December 2016 (UTC)

I should explain: The mistake was you were in the recent editing history of Extracts from the Album A Hard Day's Night [18]. I simply clicked on your userpage by mistake. Apologies again! — MusikAnimal ^talk 02:09, 5 December 2016 (UTC)

Don't worry, it's all fine! Kind regards, --El santacruzano (talk) 02:30, 5 December 2016 (UTC)

4th Annual GA Cup - Round 1

WikiProject Good Articles's 2016-2017 GA Cup Greetings, GA Cup competitors! November 28, 2016 was supposed to mark the end of the first round. However, we needed 16 competitors to move on, and currently only 10 have completed articles. Thus, the judges have come together to let the participants decide what we shall do. Please complete this quick survey to let us know whether you would like a holiday break. There will be two options for what we will do next in terms of Round 2 depending on the results of this poll. If the survey indicates that the competitors want a break, we will have a 2nd round after the break ends with just the 10 competitors who have reviewed articles, starting in January (with a specific date TBA). If the survey does not indicate that participants want a break, we will extend Round 1 until the end of December. We apologize for sending out this newsletter late. Cheers from 3family6, Figureskatingfan, Jaguar, MrWooHoo, and Zwerg Nase! To subscribe or unsubscribe to future GA Cup newsletters, please add or remove your name to our mailing list. If you are a participant, you will be on the mailing list no matter what as this is the easiest way to communicate between all participants.

--MediaWiki message delivery (talk) 15:00, 5 December 2016 (UTC)

Tech News: 2016-49

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• You can choose to see users from specific user groups in Special:ActiveUsers. [19]
• Everyone can now see Special:UserRights. Previously only those who could change user rights could. Other users got an error message. [20]
• ORES can now show how likely an edit is to be damaging to the wiki with different colours. This only works for languages that have trained ORES to recognize damaging edits. [21]

Changes this week

• You will now see categories with 0 pages in Special:Categories. Previously you did not see empty categories there. [22]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from 6 December. It will be on non-Wikipedia wikis and some Wikipedias from 7 December. It will be on all wikis from 8 December (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 6 December at 20:00 (UTC). See how to join.

Future changes

• The 2016 Community Wishlist Survey will decide what the Community Tech team will work on next year. You vote for wishes on the survey page until 12 December. You can see what has happened to last year's wishes on the 2015 results page.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

18:07, 5 December 2016 (UTC)

Discussion at Wikipedia:Sockpuppet investigations/Aboobackeramani

You are invited to join the discussion at Wikipedia:Sockpuppet investigations/Aboobackeramani. Vanjagenije (talk) 20:09, 5 December 2016 (UTC)

Rules for Fools

Hi MusikAnimal. I just wanted to clarify my thought process regarding the addition to the hatnote at Wikipedia:Edit filter. I was thinking if "WP:AF" could mean "WP:April Fools'", then someone looking for April Fools' could likely also be looking for the community's conduct expectations on April Fools' Day, which would be at Wikipedia:Rules for Fools. Ultimately, this doesn't strike me as a big deal, since Rules for Fools is listed in the hatnote at Wikipedia:April Fools. Best, Mz7 (talk) 04:58, 6 December 2016 (UTC)

Hey, no problem! In fact, let's just restore it. It read oddly to me, sort of like "you may be looking for the Wikipedia:April Fools, but make sure you read Wikipedia:Rules for Fools first!". I know that's not what you meant, and indeed one might be looking for some consensus-based documentation using the WP:AF shortcut. I've added it back :) Regards — MusikAnimal ^talk 06:34, 6 December 2016 (UTC)

Ah excellent. I see how you read it oddly at first, and again, this doesn't strike me as a huge deal. Thanks! Mz7 (talk) 17:52, 6 December 2016 (UTC)

A message from Bddmagic

Would you mind taking a look at my request for Pending changes reviewer? Bddmagic (talk) 23:22, 5 December 2016 (UTC)

Thanks for the action on my request! Could you maybe point me toward a few examples of what a 'good' revert looks like? (comments-wise, I mean)?? --Bddmagic (talk) 22:17, 6 December 2016 (UTC)

@Bddmagic: If the edit was made in good-faith, or rather, if it is not blatant vandalism, simply explain why you rejected the change. So "unsourced" or what have you. All we are looking for is your rationale. The decision to revert is left to your judgement, in accordance with policies and guidelines — MusikAnimal ^talk 01:45, 7 December 2016 (UTC)

Thanks......I swear I had it just a few days ago:Where can I find the list of articles needed a review? --Bddmagic (talk) 15:08, 7 December 2016 (UTC)

Please review the message I left on your talk page — MusikAnimal ^talk 17:05, 7 December 2016 (UTC)

Just a Question

I know that you frequently answer Requests for Permissions, and I wanted to know if you think I'd qualify for Rollback permissions for use in STiki. Also please ping me to here if you reply, as my watchlist is impossible to deal with, as Twinkle watches every page I revert to. _{Adotchar| reply here} 23:13, 4 December 2016 (UTC)

 Done @Adotchar: Seems like you have the hang of it. A few things, though: Regarding your comments at WP:PERM, you should know it admins will routinely check things like the user's talk page, basic editing stats, block log, etc. There is no need to indicate this to us, but thank you anyway! Regarding Twinkle, you can choose what pages will be added to your watchlist in your preferences, or disable that functionality altogether, if you wish. Anyway, happy reverting! Don't go too fast with the semi-automated tools :) Best — MusikAnimal ^talk 23:57, 4 December 2016 (UTC)

Yes. Thanks. I know not to go too fast, see my to do list on my user page. I'm watching the user Justeditingtoday, whose reverts usually have the same exact timestamp as the edit itself. _{Adotchar| reply here} 23:59, 4 December 2016 (UTC)

MusikAnimal Just a heads up, there's an ongoing discussion on Adotchar's talk regarding their continued issues with STiki-assisted vandalism patrol. Mike1901 (talk) 19:23, 7 December 2016 (UTC)

Incoming carrier pidgeon

...which (provided it doesn't get lost in the complex branches of the Wikipedia e-mail system) contains mail for you! Mike1901 (talk) 19:58, 7 December 2016 (UTC)

BBC 12-hour Editathon - large influx of new pages & drafts expected

New Page Reviewers are asked to be especially on the look out 08:00-20:00 UTC (that's local London time - check your USA and AUS times) on Thursday 8 December for new pages. The BBC together with Wikimedia UK is holding a large 12-hour editathon. Many new articles and drafts are expected. See BBC 100 Women 2016: How to join our edit-a-thon. Follow also on #100womenwiki, and please, don't bite the newbies :) (user:Kudpung for NPR. MediaWiki message delivery (talk) 23:55, 7 December 2016 (UTC))

NPR

I wonder if it would re possible to make your bot automatically populate this list every time a New Page Reviewer right is granted at PERM. It's just a thought, so don't worry if it cant be done. Save a lot of work though. --Kudpung กุดผึ้ง (talk) 06:46, 8 December 2016 (UTC)

@Kudpung: Good idea! I can make that happen :) The thing is we should allow people to remove themselves, and the bot will have to respect those that have. Following the mass message guide: When you mass message the list, we should include a link back to the list so they can unsubscribe, if they want. Barring an emergency like when we had to mass message all admins about the account compromises, I think any regular mailings should not be forced on people. I realize the BBC editathon is anticipated to be a big deal, but moving forward maybe we could inform users they can opt-out. So anyway the bot could still add users as they are granted the right, it just wouldn't restore any that have been removed. I guess it should also automatically remove any users who no longer hold the right, too... A little tricky, but can be done! — MusikAnimal ^talk 07:15, 8 December 2016 (UTC)

That sounds good - it really would save a lot of work. An opt out link to the list is always included in the footer in every regular mass Newsletter message I send out. The Hackethon message was an emergency one-off thing I was asked to do in the middle of the night. BTW, the backlog is still growing. All our efforts have been in vain, and there are a couple of theories being floated... Kudpung กุดผึ้ง (talk) 07:27, 8 December 2016 (UTC)

WP:BAG

Are you still active in the WP:BRFA?? I have a couple of bots in there that I'd love some feedback on. :-) --Zackmann08 (^{Talk to me}/_{What I been doing}) 21:33, 8 December 2016 (UTC)

Perhaps I will be soon :) — MusikAnimal ^talk 01:05, 9 December 2016 (UTC)

More work (for somebody)

We now need to start monitoring the effect/effectivity of Page Curation. This is something that has never been done since its creation. If the Quarry strings can be done for the following, then we have them for regular updates to he data. Believe me , if I knew how to do this myself, I would, rather than having to pester other Wikipedians. Regex (or whatever is used) is one of the most frustrating gaps in my education, there are so many professional fields where I could be using it.

Details

From this log, I need to know: A sortable Wikitable showing columns for List of names of users since September 7, 2012 by number of uses of the tool Which of those have the New Page Reviewer right Which of those have the Administrator (Sysop) right Date of registration or first edit to Wikipedia Date of last use of Curation Date of last edit to Wikipedia Total edit count Summary: x% of users registered before 6 December 2015. x% of users have edit counts over 10,000. A graph (not a bar chart) showing Total uses of the tool by month from 6 Dec 2015 A graph (not a bar chart) showing three lines Total uses of the tool by day from 6 Nov 2016 Uses of the tool by day by New Page Reviewer right holders from 6 Nov 2016 Uses of the tool by day by non New Page Reviewer right holders from 6 Nov 2016 Summary: 'x% of the uses are a being done by x% of the users. x% of the users using the Curation Tool have the New Page Reviewer right.

If you think any additional stats would be valuable, please let me know. If you haven't got time for all this, or if it's not in your sphere of interest, please suggest someone who has. Thanks. Kudpung กุดผึ้ง (talk) 19:39, 8 December 2016 (UTC)

Did you see the flood of new pages due to the BBC hackethon, and the things that patrollers got wrong? The work getting the NPP system system is far from concluded.Kudpung กุดผึ้ง (talk) 02:36, 9 December 2016 (UTC)

I can try to run some Quarry's for you soon. As for those BBC articles, what I observed were patrollers (most without the user right) doing drive-by tagging for trivial things like categories and linking when they could easily help out themselves. Some inappropriate speedy nominations, and BLP PROD less than a minute after the article was created. I talked to each and every one of those "patrollers" personally. Most of the articles I reviewed otherwise appeared to be in an acceptable shape. I'm going to try to do more — MusikAnimal ^talk 02:43, 9 December 2016 (UTC)

Total Page Views?

How do I get the total number of page views of one page? The tool currently connected counts only from 2015 onwards. And the tool referred to: http://stats.grok.se/de/201612/Widerstandsthermometer gives only "internal server error" back. --Manorainjan (talk) 11:59, 8 December 2016 (UTC)

@Manorainjan: Correct, the Pageviews API only provides data from July 2015. You can use stats.grok.se to get older data though, such as December 2014, etc. Note this older data used a different, less accurate pageview definition, and should not be compared alongside the data you see with Pageviews Aanlysis — MusikAnimal ^talk 17:03, 8 December 2016 (UTC)

I can not use http://stats.grok.se can You use it? When I try to use it, it returns only the "internal server error" message. --Manorainjan (talk) 23:19, 8 December 2016 (UTC)

@Manorainjan: Try older dates, 2015 and before — MusikAnimal ^talk 23:39, 8 December 2016 (UTC)

That does return results, thank You. But for getting the total number of page views since page creation I would have to call that tool 12 times per year and add all results manually. Is there no tool to get such a number in one shot? Manorainjan (talk) 23:56, 8 December 2016 (UTC)

@Manorainjan: I have a ticket to incoroporate the stats.grok.se data into Pageviews Analysis (see phab:T149358). I hope to get to it sometime in early 2017. Until then yes, you'll have to do the calculations manually :( Mind you again the numbers you get from stats.grok.se provide only a rough synopsis of actual traffic. Actual traffic is probably considerably higher — MusikAnimal ^talk 00:40, 9 December 2016 (UTC)

Great :-) I'm looking forward to that. I "subscribed" to that ticked in the hope that this will result in notifications for me, if anything happens there. Manorainjan (talk) 12:29, 9 December 2016 (UTC)

Stop

Hi, please stop process : Eranbot/MusikBot turn endlessly : User:MusikBot/CopyPatrol/Error_log. Thanks --Framawiki (please notify) (talk) 17:35, 9 December 2016 (UTC)

The password for the copyright database evidently was changed. Looking into it! — MusikAnimal ^talk 17:44, 9 December 2016 (UTC)

OK should be fixed. I guess that user/password was removed access entirely. Not sure what happened. Thanks for letting me know! — MusikAnimal ^talk 17:51, 9 December 2016 (UTC)

New Page Review - newsletter #2

Hello MusikAnimal,

Please help reduce the New Page backlog

This is our second request. The backlog is still growing. Your help is needed now - just a few minutes each day.

Getting the tools we need

ONLY TWO DAYS LEFT TO VOTE

• Improve the tools: Vote here.
• Reduce your review load: Vote here

---

Sent to all New Page Reviewers. Discuss this newsletter here. If you wish to opt-out of future mailings, please remove yourself from the mailing list MediaWiki message delivery (talk) 06:55, 11 December 2016 (UTC) .

A barnstar for you!

	The Technical Barnstar
	For writing TWO FULL modules for bot(s), all the tasks that MusikBot is performing, helping me, being one of the more-active edit filter managers, I "hereby" award you this technical barnstar (but seriously, those modules are goddamn amazing) Dat GuyTalkContribs 16:41, 10 December 2016 (UTC)

Many thanks, friend! — MusikAnimal ^talk 18:35, 11 December 2016 (UTC)

Alysson Wonderland

• Alysson Wonderland (talk · contribs)

Did you mean to disable autoblock on this one? 172.58.40.80 (talk) 21:31, 11 December 2016 (UTC)

Nothing intended here, just patrolling this. 172.58.40.80 (talk) 21:34, 11 December 2016 (UTC)

All good, and thanks for pointing it out. I need to update Twinkle to have better defaults for this type of block — MusikAnimal ^talk 21:37, 11 December 2016 (UTC)

Can you also place a tag on New edit account (talk · contribs)? 172.58.40.80 (talk) 21:41, 11 December 2016 (UTC)

I'm not going to bother with that right now. The hole is much deeper, will need to speak with some colleagues first — MusikAnimal ^talk 22:00, 11 December 2016 (UTC)

This week's article for improvement (week 50, 2016)

The Dreadnought hoaxers in Abyssinian regalia; the bearded figure on the far left is in fact the writer Virginia Woolf. Hello, MusikAnimal. The following is WikiProject Today's articles for improvement's weekly selection: Hoax Please be bold and help to improve this article! Previous selections: Three-martini lunch • Homework Get involved with the TAFI project. You can: Nominate an article • Review nominations Posted by: MusikBot talk 00:07, 12 December 2016 (UTC) using MediaWiki message delivery (talk) on behalf of WikiProject TAFI •

Tech News: 2016-50

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• Users who have Yahoo email addresses could not use Special:EmailUser to send emails. This has now been fixed. Emails will now come from a @wikimedia.org address. Users who get an email from you will still reply to your email address and be able to see it. [23]
• You can now see how many categories and pages there are in the categories in Special:TrackingCategories. This is to help you find pages that could need attention. [24]
• Markup colours for reviewed and pending revisions in the page history and recent changes and logs now match Wikimedia standard colours. The "You have a new message on your talk page" notification will have a slightly different colour. [25]

Problems

• Because of work on cross-wiki watchlists global renaming is not working. The plan is to turn it on again on 16 December. Global renaming was turned off for a while in late November and early December as well. [26]

Changes this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from 13 December. It will be on non-Wikipedia wikis and some Wikipedias from 14 December. It will be on all wikis from 15 December (calendar).

Meetings

• You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on December 13 at 20:00 (UTC). See how to join.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

19:29, 12 December 2016 (UTC)