User talk:MusikAnimal

User
Talk
Dashboard
Articles
Scripts
Tools
Templates
Userboxes
Awards

Talk

It is around 12:33 where this user lives in New York City. ⁽⁾

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)

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)

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 798 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) .

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. [1]
• 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. [2]
• 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]. [3][4]

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 [5] 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)

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)Template:Z48

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)

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)