User talk:Ged UK/Archives/2013/November

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

A barnstar for you!

The Civility Barnstar
It was while ago. Thank you. Angry Mustelid (talk) 17:40, 30 October 2013 (UTC)
Thanks :) GedUK  12:22, 1 November 2013 (UTC)

I believe you can now lift the pending changes protection on the article. It has lived its purpose.—Ryulong (琉竜) 07:57, 31 October 2013 (UTC)

 Done Kudos to you for admitting the circumstances have changed  :) GedUK  12:26, 1 November 2013 (UTC)

The Signpost: 30 October 2013

Vandalism on Apurv Gupta again

Moved here from Template talk:Talkback -- John of Reading (talk) 07:43, 5 November 2013 (UTC)

Dear Ged UK,

You have now added semi protection on the page Apurv Gupta, the UN Association Youth President's page two times.

It is constantly host to vandalism after the last expiry only a few days ago. The user is noted to be making fake wikipedia accounts and is adding negative information about a living person without any extraordinary reference.

It is therefore, my request to kindly look into this matter and protect the page once again for a longer duration perhaps.

Best,

Gregyuri — Preceding unsigned comment added by Gregyuri (talkcontribs) 02:32, 5 November 2013 (UTC)

It's already been done by another admin. GedUK  12:31, 8 November 2013 (UTC)

The Signpost: 06 November 2013

Sinbad (comedian)

I see you protected Sinbad (comedian), presumably due to repeated changing of his date of birth.

The irony is that if it weren't for them, nobody would've noticed that the sources themselves disagree, and as none of the sources we have are obviously more reliable than the others, it's best to have the "disputed" tag near the date of birth. Without those meddling non-logged-in editors this would've gone undetected much longer. davidwr/(talk)/(contribs) 03:09, 12 November 2013 (UTC)

Yup, it's surprising how often that happens! GedUK  12:46, 12 November 2013 (UTC)

Edit war at Kelly Baugher

I was wondering about your comment that you have warned 'the user' in this dispute. Since it takes two (or more) to war I was interested in learning whether you made an active decision not to warn the other participant. Fiddle Faddle 14:09, 12 November 2013 (UTC)

Hmm, I thought I'd done that. Too many tabs open, it was just sitting there. Done now. GedUK  14:13, 12 November 2013 (UTC)
I have days like that! Welcome to my strange and twilight world :) Fiddle Faddle 14:31, 12 November 2013 (UTC)

Namit Das

Hi,

I am in personal contact with the person. Not much is there on the internet about the actor. That is the reason it is i have not added any references. So what should i do? TanmayRaoM (talk) 18:12, 13 November 2013 (UTC)

Hi there. If there aren't references on the internet or in print media (newspapers, magazines) then we can't use it. Basically if websites, newspapers, magazines etc aren't writing about him, then he's not notable enough to have an article on wikipedia. Sources don't have to be on the internet, paper, TV etc is fine too. GedUK  12:07, 14 November 2013 (UTC)

This page has been vandalized for three months or so. Is "one month" enough? At least "pending changes" is enough protection. --George Ho (talk) 22:08, 14 November 2013 (UTC)

The protection usually increases steadily. This page hasn't been protected in 3 years, and only once for vandalism. That means I start from a low base, especially as it's not a BLP. If I'd have added semi-protection it would probably have been for a week or 10 days. As it's pending changes, which still allows IPs to edit, I usually start with one month.
If it continues after a month, then the next protection will be longer, like three months, then 6/1 year etc up to indef as a last resort.
Of course, if PC proves to be ineffective, then we can switch to semi protection. GedUK  12:33, 15 November 2013 (UTC)

The Signpost: 13 November 2013

Administration Noticeboard

Information icon There is currently a discussion at Wikipedia:Administrators' noticeboard/IncidentArchive819#Conflict of Interest / Paid Advocacy regarding an issue with which you may have been involved by virtue of inspecting or otherwise looking at the edits of the reported user. Thank you. Fiddle Faddle 14:02, 16 November 2013 (UTC)

Noted. GedUK  12:29, 18 November 2013 (UTC)

Just wanted to let you know that I'm okay with the latest edit made by another user before you protected the article and had no intent on reverting. The other editing actually didn't completely revert the content I had added, but only one of three items.--Oakshade (talk) 01:27, 18 November 2013 (UTC)

I'm not favouring one side or the other, nor singling out any particular user or users. The article was unstable and needed protection. GedUK  12:30, 18 November 2013 (UTC)

VisualEditor newsletter for November 2013

Since the last newsletter, the VisualEditor team has worked on some feature changes, major infrastructure improvements to make the system more stable, dependable and extensible, some minor toolbar improvements, and fixing bugs.

A new form parsing library for language characters in Parsoid caused the corruption of pages containing diacritics for about an hour two weeks ago. Relatively few pages at the English Wikipedia were affected, but this created immediate problems at some other Wikipedias, sometimes affecting several dozen pages. The development teams for Parsoid and VisualEditor apologize for the serious disruption and thank the people who reported this emergency at Wikipedia:VisualEditor/Feedback and on the public IRC channel, #mediawiki-visualeditor.

There have been dozens of changes since the last newsletter. Here are some of the highlights:

  • Accidental deletion of infoboxes and other items: You now need to press the Delete or ← Backspace key twice to delete a template, reference or image. The first time, the item becomes selected, and the second time, it is removed. The need to press the delete key twice should make it more obvious what you are doing and help avoid accidental removals of infoboxes and similar (bug 55336).
  • Switch from VisualEditor to the wikitext editor: A new feature lets you make a direct, one-way editing interface change, which will preserve your changes without needing to save the page and re-open it in the wikitext editor (bug 50687). It is available in a new menu in the action buttons by the Cancel button (where the "Page Settings" button used to be). Note that this new feature is not currently working in Firefox.
  • Categories and Languages are also now directly available in that menu. The category suggestions drop-down was appearing in the wrong place rather than below its input box, which is now fixed. An incompatibility between VisualEditor and the deployed Parsoid service that prevented editing categories and language links was fixed.
  • File:, Help: and Category: namespaces: VisualEditor was enabled for these namespaces the on all wikis (bug 55968), the Portal: and Viquiprojecte: namespaces on the Catalan Wikipedia (bug 56000), and the Portal: and Book: namespaces on the English Wikipedia (bug 56001).
  • Media item resizing: We improved how files are viewed in a few ways. First, inline media items can now be resized in the same way that has been possible with block ones (like thumbnails) before. When resizing a media item, you can see a live preview of how it will look as you drag it (bug 54298). While you are dragging an image to resize it, we now show a label with the current dimensions (bug 54297). Once you have resized it, we fetch a new, higher resolution image for the media item if necessary (bug 55697). Manual setting of media item sizes in their dialog is nearly complete and should be available next week. If you hold down the ⇧ Shift key whilst resizing an image, it will now snap to a 10 pixel grid instead of the normal free-hand sizing. The media item resize label now is centered while resizing regardless of which tool you use to resize it.
  • Undo and redo: A number of improvements were made to the transactions system which make undoing and redoing more reliable during real-time collaboration (bug 53224).
  • Save dialogue: The save page was re-written to use the same code as all other dialogs (bug 48566), and in the process fixed a number of issues. The save dialog is re-accessible if it loses focus (bug 50722), or if you review a null edit (bug 53313); its checkboxes for minor edit, watch the page, and flagged revisions options now layout much more cleanly (bug 52175), and the tab order of the buttons is now closer to what users will expect (bug 51918). There was a bug in the save dialog that caused it to crash if there was an error in loading the page from Parsoid, which is now fixed.
  • Links to other articles or pages sometimes sent people to invalid pages. VisualEditor now keeps track of the context in which you loaded the page, which lets us fix up links in document to point to the correct place regardless of what entry point you launched the editor from—so the content of pages loaded through /wiki/Foobar?veaction=edit and /w/index.php?title=Foobar&veaction=edit both now have text links that work if triggered (bug 48915).
  • Toolbar links: A bug that caused the toolbar's menus to get shorter or even blank when scrolled down the page in Firefox is now fixed (bug 55343).
  • Numbered external links: VisualEditor now supports Parsoid's changed representation of numbered external links (bug 53505).
  • Removed empty templates: We also fixed an issue that meant that completely empty templates became impossible to interact with inside VisualEditor, as they didn't show up (bug 55810).
  • Mathematics formulae: If you would like to try the experimental LaTeX mathematics tool in VisualEditor, you will need to opt-in to Beta Features. This is currently available on Meta-wiki, Wikimedia Commons, and Mediawiki.org. It will be available on all other Wikimedia sites on 21 November.
  • Browser testing support: If you are interested in technical details, the browser tests were expanded to cover some basic cursor operations, which uncovered an issue in our testing framework that doesn't work with cursoring in Firefox; the Chrome tests continue to fail due to a bug with the welcome message for that part of the testing framework.
  • Load time: VisualEditor now uses content language when fetching Wikipedia:TemplateData information, so reducing bandwidth use, and users on multi-language or multi-script wikis now get TemplateData hinting for templates as they would expect (bug 50888).
  • Reuse of VisualEditor: Work on spinning out the user experience (UX) framework from VisualEditor into oojs-ui, which lets other teams at Wikimedia (like Flow) and gadget authors re-use VisualEditor UX components, is now complete and is being moved to a shared code repository.
  • Support for private wikis: If you maintain a private wiki at home or at work, VisualEditor now supports editing of private wikis, by forwarding the Cookie: HTTP header to Parsoid ($wgVisualEditorParsoidForwardCookies set to true) (bug 44483). (Most private wikis will also need to install Parsoid and node.js, as VisualEditor requires them.)

Looking ahead:

  • VisualEditor will be released to some of the smaller Wikipedias on 02 December 2013. If you are active at one or more smaller Wikipedias where VisualEditor is not yet generally available, please see the list at VisualEditor/Rollouts.
  • Public office hours on IRC to discuss VisualEditor with Product Manager James Forrester will be held on Monday, 2 December, at 1900 UTC and on Tuesday, 3 December, at 0100 UTC. Bring your questions. Logs will be posted on Meta after each office hour completes.
  • In terms of feature improvements, one of the major infrastructure projects affects how inserting characters works, both using your computer's built-in Unicode input systems and through a planned character inserter tool for VisualEditor. The forthcoming rich copying and pasting feature was extended and greater testing is currently being done. Work continues to support the improved reference dialog to quickly add citations based on local templates.

If you have questions or suggestions for future improvements, or if you encounter problems, please let everyone know by posting a note at Wikipedia:VisualEditor/Feedback. Thank you! Whatamidoing (WMF) 22:15, 20 November 2013 (UTC)

Cascading on Martin Bashir

It looks like you accidentally enabled cascading on Martin Bashir. Just a heads up. Ramaksoud2000 (Talk to me) 05:27, 20 November 2013 (UTC)

It seems clear at this point that there is no BLP problem. Strong sources have been listed on the talk page. At this point, the article should be unprotected, so that normal BRD editing can resume. If you had protected it (in either version) simply to stop an edit-war, I wouldn't have a problem with letting the protection run its full course. Since you edited it and then protected it, I don't feel that's appropriate here. If you're not willing to unprotect it, I'd like to hear what specific BLP concerns you feel exist at this time. Joefromrandb (talk) 07:11, 20 November 2013 (UTC)
I've corrected the cascade, sorry about that.
I did protect it because there's an edit war. I edited it first to remove the potential BLP violation before the protection; that's clearly sensible. Whilst there's a does appaar to be a consensus on the talk page and BLPN (though not everyone involved has responded recently), there clearly isn't agreement on what the content should be, and in my view there remain BLP issues until that is resolved. Doesn't look like it will take much longer though, and when there's consensus, I'll be happy to unprotect the page.
However, if you wish another admin to have a look at this, then please raise at RfPP, but please make reference to this conversation. GedUK  12:09, 20 November 2013 (UTC)
I have submitted an edit request, following establishment of consensus.Anythingyouwant (talk) 17:30, 20 November 2013 (UTC)
Since it appears that I am a minority of one, I accept that it is probably appropriate to unprotect the page so that further edits can be made. I still am absolutely certain that everyone else is wrong, but I'll have to decide if it's worth pursuing dispute resolution for; the burden is now clearly on me to make my case since the opposition is complete save myself. Qwyrxian (talk) 09:24, 21 November 2013 (UTC)
I've lowered the protection after reading the whole discussion on the talk page. Thanks for being sensible about this Qwyrxian. I can see where you are coming from, but I do not share the BLP concerns because the facts are not in dispute and the passage is written neutrally. There also seems a good compromise worked out on the talk page regarding the potentially gratuitous offensive words. You may well be right that this small incident is being given undue weight, but I don't see how the incident can reasonably be omitted from the biography as this stage. — Martin (MSGJ · talk) 12:46, 21 November 2013 (UTC)
Thanks for keeping me in the loop. GedUK  14:26, 21 November 2013 (UTC)

I saw you closed the AFD. Two things I want to bring up. First could you also SALT WP:2016 Formula One Season? The recreations have been happening there too. Also the end date(November 21, 2014) for the SALTING. The Bushranger thought August was fine, I was for sometime in the summer. Just maybe a 9 month SALT(August 21 2014) might be an idea. It's up to you. Cheers! — Preceding unsigned comment added by WilliamJE (talkcontribs)

Do you mean that page? It doesn't exist, nor has it ever.
Re the salt length, I went initially for two years, but that was clearly too long. A year from now will be Nov 2014, so that still gives us about 18 months before the 2016 season starts. If someone wants the article creating sooner with decent sources, then they can always ask for unprotection nearer the time. GedUK  15:37, 21 November 2013 (UTC)
I meant 2016 Formula One Season. It was recreated this week. November is fine for the end of SALTING and I understand how the an editor can request it be unsalted. Cheers and thanks....William 15:41, 21 November 2013 (UTC)
 Done GedUK  14:12, 22 November 2013 (UTC)

The Signpost: 20 November 2013

You just deleted this as I was going to "prod" it instead. Can you please userfy this to my user space, so I can try to rescue it? Bearian (talk) 13:41, 27 November 2013 (UTC)

Well, I deleted the AfC, so you can't prod that. I don't think. Anyway, yes, I'll restore it for you momentarily. GedUK  13:43, 27 November 2013 (UTC)
 Done It's now at User:Bearian/Atlanta Sacred Chorale. GedUK  13:46, 27 November 2013 (UTC)

Thanks

Thanks for finding a good version of John Paul Mitchell Systems -- I was too impatient. I made a fewfurther small edits. DGG ( talk ) 17:34, 27 November 2013 (UTC)

No worries. :) GedUK  12:07, 28 November 2013 (UTC)