Jump to content

User talk:MSGJ: Difference between revisions

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Content deleted Content added
m Archiving 3 discussion(s) to User talk:MSGJ/2016) (bot
Line 168: Line 168:


[[Image:Symbol question.svg|25px]] Hello! Your submission of [[Selly Oak Park]] at the [[Template talk:DYK|Did You Know nominations page]] has been reviewed, and some issues with it may need to be clarified. Please review the comment(s) underneath '''[[Template:Did you know nominations/Selly Oak Park|your nomination's entry]]''' and respond there as soon as possible. Thank you for contributing to Did You Know! <!--Template:DYKproblem--> <span class="smallcaps" style="font-variant:small-caps;">[[User:Northamerica1000|North America]]<sup>[[User talk:Northamerica1000|<font size="-2">1000</font>]]</sup></span> 05:49, 16 April 2016 (UTC)
[[Image:Symbol question.svg|25px]] Hello! Your submission of [[Selly Oak Park]] at the [[Template talk:DYK|Did You Know nominations page]] has been reviewed, and some issues with it may need to be clarified. Please review the comment(s) underneath '''[[Template:Did you know nominations/Selly Oak Park|your nomination's entry]]''' and respond there as soon as possible. Thank you for contributing to Did You Know! <!--Template:DYKproblem--> <span class="smallcaps" style="font-variant:small-caps;">[[User:Northamerica1000|North America]]<sup>[[User talk:Northamerica1000|<font size="-2">1000</font>]]</sup></span> 05:49, 16 April 2016 (UTC)

== Breach of editing restriction that you enacted. ==

You may recall that you enacted an editing restriction against [[User:Wtshymanski|Wtshymanski]] just over a year ago. Wtshymanski, has started breaching that editing restriction, including reverting an IP editor, but disguising it as a regular edit. There is an ANI on the issue at [https://en.wikipedia.org/wiki/Wikipedia:ANI#Wtshymanski_reverting_IP_editors_in_breach_of_editing_restrictions here]. It is suffering from a lack of adminstrator action. Could you please take a look? [[Special:Contributions/212.183.128.147|212.183.128.147]] ([[User talk:212.183.128.147|talk]]) 15:58, 19 April 2016 (UTC)

Revision as of 15:58, 19 April 2016

Mafia

Hello, MSGJ, please have a look here.
Have you read? If you have not, please do it before continuing the reading. As you can see, there is one more user and also a user since 2005 who agree to add the pronunciation of the Italian word "Mafia". Is this enough for you? I would like to hear your answer to be sure, I have learnt to be careful with trigger (block) happy admins. If you have no objection about that matter, I will write in the talk page that a consensus has been reached, then one of the two users shall add the pronunciation. Is this ok? — Preceding unsigned comment added by 151.20.112.193 (talkcontribs)

I'm going to ask that you rewrite your close there. I was the nominator at AFD but I didn't do the move. Legacypac did the move but didn't nominate the page for deletion. Your close implies that this was a coordinated plan between the two of us to have it moved and deleted. I closed the MFD, Legacypac moved it to mainspace an hour later, tagged it and ten hours later, after fixing the screwed-up MFD notice (since it was moved), I then nominated the page for deletion at AFD where it's been taken back. You can argue about moving bad drafts into mainspace but I don't think those are being moved for the express purpose of starting a discussion at AFD to have it deleted there. -- Ricky81682 (talk) 08:39, 21 March 2016 (UTC)[reply]

Actually, this is exactly what has happened in the past, e.g. Graffiki was moved into mainspace by Legacypac and then three minutes later was nominated at AfD by him. I'll take another look at Chaz Knapp and look at rewording the closure. I didn't mean to imply you were actively colluding in this regard. — Martin (MSGJ · talk) 09:30, 21 March 2016 (UTC)[reply]
As I explained at Wikipedia:Administrators'_noticeboard/Incidents#Back_on_point, that was the prior case. The two other cases weren't that. I would agree that "moving an article you believe to be unsuitable into mainspace is disruptive" is appropriate, the AFD implication is not. This is all stupidly moot since the userspace page was later deleted by DGG under U5 but given the reverts to my relistings and repeated draggings to ANI over "admin deletionist gameplaying at MFD", I'd prefer to not leave any vague insinuations out there. -- Ricky81682 (talk) 09:41, 21 March 2016 (UTC)[reply]
I've reworded the close, basically using your suggested words above. Hope this is satisfactory. Regards — Martin (MSGJ · talk) 12:34, 21 March 2016 (UTC)[reply]

Perfect. That's all I ask. -- Ricky81682 (talk) 18:26, 21 March 2016 (UTC)[reply]

Hi MSGJ . Two months ago, you removed the background color from the edit notice at List of Islamist terrorist attacks, asking "is the yellow background needed". I believe it is. Without any color, the edit notice is hard to see, and in the two months since you changed it, new editors have added about two dozen incidents that were either not attributed to Islamists or not described as terrorist attacks by reliable sources. There's no way to know, of course, but I think there might have been fewer had the edit notice been more... well, noticeable.

I'd like you to reconsider your decision and restore the color to the edit notice. Thank you. — Malik Shabazz Talk/Stalk 20:36, 27 March 2016 (UTC)[reply]

Will respond shortly. Sorry for the delay — Martin (MSGJ · talk) 23:56, 29 March 2016 (UTC)[reply]
@Malik Shabazz: I am not too worried about this particular template. My general concern is about consistency with all edit notice templates. I believe that all of them should be yellow, or else none or them should be yellow. Do you think that your rationale for making this editnotice yellow could equally apply to all edit notice templates? — Martin (MSGJ · talk) 10:47, 4 April 2016 (UTC)[reply]
I created the editnotice based on Template:Editnotice for lists of people, which still has the line you deleted:
textstyle = font-size: 110%; background: #ffeebb
That template is in use on hundreds of editnotices.
— Malik Shabazz Talk/Stalk 02:03, 5 April 2016 (UTC)[reply]

It seems as if another user has come along to revert the formatting I implemented a week after the discussion. When they restored the previous reversion, I reverted in good faith with a solid explanation, but they continued to revert under the impression that I have modified comments. I've ceased any further reverts and posted on their talk page with further explanation; I await a reply. However, I think that some sockpuppetry may be involved, as three different but similar IPs have contributed on this particular issue (217.248.20.109, 217.248.0.219, 217.248.22.214). Alex|The|Whovian? 12:27, 29 March 2016 (UTC)[reply]

I wanted to leave this alone, but the bullshit accusation of sockpuppetry is too much. Maybe you should ask for a checkuser? Oh right, that doesn't make sense, because only accounts can sockpuppet. Alex, step back, and don't touch other editor's comments ever again.-217.248.22.214 (talk) 12:36, 29 March 2016 (UTC)[reply]
Here is the diff in question.-217.248.22.214 (talk) 12:38, 29 March 2016 (UTC)[reply]
Please remain civil. This is simply an informative message to MSGJ, not a discussion in itself. An official third opinion has also been requested. Alex|The|Whovian? 12:40, 29 March 2016 (UTC)[reply]

No time to look into this now I'm afraid, but I suggest you both find something more productive to do ;) — Martin (MSGJ · talk) 23:56, 29 March 2016 (UTC)[reply]

I'd love to.-217.248.10.121 (talk) 10:10, 30 March 2016 (UTC)[reply]
Ditto. Alex|The|Whovian? 11:30, 30 March 2016 (UTC)[reply]
Simple: Stop mucking with my talk page comments, as promised in your unblock request.-217.248.10.121 (talk) 12:05, 30 March 2016 (UTC)[reply]
This still isn't a discussion page. Take it elsewhere. Alex|The|Whovian? 12:10, 30 March 2016 (UTC)[reply]
Now you think of that?
I looking forward to your response elsewhere then.-217.248.10.121 (talk) 13:04, 30 March 2016 (UTC)[reply]

March 1932 lunar eclipse Rating

I rated the page March 1932 lunar eclipse as a stub and of low importance. 78.148.76.115 (talk) 16:44, 4 April 2016 (UTC)[reply]

Template Multiple issues 2

Hi. However misguided Boghog is to have created {{Multiple issues 2}} for use in Acetone peroxide, it's temporarily slightly better than using the sandbox of {{Multiple issues}}. If any work is done (by anyone at any time) to the sandbox, the result will be immediately seen in Acetone peroxide, which is clearly not appropriate - Multiple issues is protected for a reason.

Multiple issues 2 was correctly tagged for speedy deletion, and should have been deleted by now for obvious reasons. Acetone peroxide should be using the consensus agreed templating of Multiple issues but trying to put that right turned into a minor edit war.

My attempts to find a solution to these problems have failed, but without question, I hope you can see that, Acetone peroxide should not be utilising a template sandbox for anything. I therefore ask that you revert or understand the reverting of your edit to redirect Multiple issues 2 to Multiple issues/sandbox - which needs to should happen as soon as possible. fredgandt 17:35, 4 April 2016 (UTC)[reply]

Okay, it is not an ideal situation and I have already advised Boghog that they are being disruptive. But I don't think you need to stress about it. (Will all come out in the wash.) Cheers — Martin (MSGJ · talk) 10:03, 5 April 2016 (UTC)[reply]

Taking a look at the broader picture:

I've worked to cleanup all the inappropriate deletions because of page moves from the userspace to the mainspace of content clearly not suitable for the mainspace above. It looks like you found some additional problematic page moves (e.g. User:Akeefe98/Joseph Summer). Where all of the above issues based on problematic moves originate can be seen at Special:log/Legacypac. Two of the pages restored have been nominated for deletion by the same user who inappropriately moved them, Wikipedia:Miscellany for deletion/Draft:Solitaire & Mahjong and Wikipedia:Miscellany for deletion/Draft:Duplekita (see also: Wikipedia:Redirects for discussion/Log/2016 April 2#User:Trekie9001/Duplekita at RfD and User:Aaaloco/Solitaire & Mahjong a speedy deletion request). My actions to clean up their "mistakes" (I'll call them that per extreme AGF and CIVILITY, though some of them can be explicitly shown not to be, and are in some of the links above) have been called into question at AN/I by said user. I noticed your most recent comment at their talk page regarding this matter was on April 4. If the inappropriate moves haven't stopped, they need to, because they are leading to out of process actions which are creating work for the community. Best Regards,Godsy(TALKCONT) 00:25, 5 April 2016 (UTC)[reply]

The inappropriate moves from the userspace to the mainspace are happening again. I reverted another move that was clearly not suitable for the mainspace. Another recent move has been nominated for deletion. Special:Log/Legacypac.Godsy(TALKCONT) 07:40, 5 April 2016 (UTC)[reply]
Sorry to slam you with all this information here. I'd have replied at User talk:Legacypac#Moving unsuitable drafts to mainspace, but I didn't think it would be welcome there.Godsy(TALKCONT) 18:34, 5 April 2016 (UTC)[reply]

A kitten for you!

A kitten for you! CounterTime (talk) 11:20, 5 April 2016 (UTC)[reply]

Well thank you. What did I do to deserve such a cute kitten? — Martin (MSGJ · talk) 11:21, 5 April 2016 (UTC)[reply]

DDG-121

nevermid

Please at least put the pages (a & b) back to status quo before he started his silly anti-comma-crusade page-move-war. Can't have every decision go against me. - theWOLFchild 15:26, 5 April 2016 (UTC)[reply]

Have you see this? - Wikipedia:Administrators' noticeboard/Incidents#Dicklyon and his treatment on commas before Jr/Sr. Apparently he's on a project-wide rampage against commas. Meanwhile, are you going to move the articles back to where they were until a decision is made? Since it seems now that this affects more than just this page, it make take awhile. If we follow basic BRD, he moved, I reverted, it should stay the way it was until resolved. Add to that the policy, refs and other ships I noted on the talk page, it would seem prudent to move to the pages back to where they where. - theWOLFchild 16:17, 5 April 2016 (UTC)[reply]
Some further digging has shown that the page should be moved back to the original title (with comma) per WP:MOS; Where more than one style is acceptable, editors should not change an article from one of those styles to another without a good reason. Edit warring over optional styles is unacceptable.[b] If discussion cannot determine which style to use in an article, defer to the style used by the first major contributor. There is also this RfC at the Village Pump; please note the closing comments by Drmies.
It's clear the pages should be returned, based on WP:MOS, WP:JR (& supporting RS), WP:OSE (& supporting ship articles), and the RfC at WP:VP. Of course there's also the article talk page as well. Thank you. - theWOLFchild 18:02, 5 April 2016 (UTC)[reply]

It would be better if the wolf would join the discussion that I've pointed him at, on implementing the consensus decision in WP:JR, and make a case there for why this article should be treated as an exception to the guideline. Dicklyon (talk) 18:14, 5 April 2016 (UTC)[reply]

Seriously, you need to stop following me to every page I go to. It's called WP:WIKIHOUNDING. Before I go anywhere, you need to go back to the DDG-121 talk page and explain why you feel the guidelines here don't apply to you and your bizarre war on commas. - theWOLFchild 18:19, 5 April 2016 (UTC)[reply]
Anyone home?

I'm not sure when you're coming back, but I can't say the USS Frank E. Petersen, Jr. page is any better from the way you left it. Through basic enabling, Dicklyon has made multiple, unconstructive changes, all geared to the "war on commas". I've had to leave the article for fear of being labeled as edit-warring. I created that stub yesterday and now I can't even work on it. As soon as you return, you need to review what has taken place there, along with his contribs in general (all geared towards removing commas) and, the closely-related issues at his talk page (1, 2 & 3) and ANI (4).

Along with all those, I'm sure you were aware of his recent standard offer? Or the disruptive page moves and subsequent ban on page moves (and socking) that led to his recent indef in the first place? I'll leave to you, as an admin, to determine how his recent behaviour should be dealt with, in light of both the surrounding issues and recent history. For my part, all I'm asking is that the page be return to status quo, as it should have been in the first place and how I've since clearly demonstrated is should be per WP-guidelines. I would like to resume working on it without any further harassment. Thank you. - theWOLFchild 21:07, 5 April 2016 (UTC)[reply]

Apparently so...

I see you've been active since I posted these comments here, and while I still wonder if you're ever going to respond, mainly I would just like to the pages moved back to where they belong;
USS Frank E. Petersen, Jr. is the article, USS Frank E. Petersen Jr. is the redirect - as per the all the supporting guidelines noted above. They are in the incorrect places due to your page moves, please correct them. - theWOLFchild 16:39, 6 April 2016 (UTC)[reply]

It's clear you are deliberately ignoring my requests here for a response (and ignoring WP:ADMINACCT, again). I'm not going to waste anymore of my time here.. Disregard my previous posts. - theWOLFchild 22:08, 6 April 2016 (UTC)[reply]

Requesting update to Antivandal tool script

Hi MSGJ, I'm requesting an update to Lupin's Anti-vandal tool script at User:Lupin/recent2.js. The field recent2.userIsSysop should include a check for whether the user is a rollbacker, because rollbackers can use admin rollback. (it's also faster than non-admin rollback javascript anyway). (recent2.userIsSysop). Also wouldn't it make sense for the tool to ignore the user's own edits as well?? (recent2.ignore_my_edits = true; /*instead of false;*/) Thanks. — Andy W. (talk · contrib) 17:52, 5 April 2016 (UTC)[reply]

I just realized that the reason I cannot edit the script is not because I'm not an admin... right? I'm assuming there's a new policy about editing another user's js files? So perhaps I should simply duplicate the script myself and import my own version, then. Let me know if you have a different suggestion. Thanks anyway. — Andy W. (talk · contrib) 18:02, 5 April 2016 (UTC)[reply]
@Andy M. Wang: Not a new policy, it's always been the case that if you're not an admin the only .js and .css pages that you can edit are those that are subpages of your own user page. --Redrose64 (talk) 23:35, 5 April 2016 (UTC)[reply]
@Redrose64: Thanks for letting me know. I've since made a personal script with the change. — Andy W. (talk · contrib) 23:37, 5 April 2016 (UTC)[reply]

I've commented at User talk:Lupin/Anti-vandal tool — Martin (MSGJ · talk) 20:03, 6 April 2016 (UTC)[reply]

From Miss Click

Thanks for catching that. I must have, well, yes, misclicked. Cheers. :) Anna Frodesiak (talk) 10:17, 6 April 2016 (UTC)[reply]

Template:User:ClueBot III/ArchiveThis

Dear User:MSGJ. Thanks for your interest for the {{User:ClueBot III/ArchiveThis}} template. But, to tell the truth, this template was only edited once since 2013... and don't seems to be the target of any attack. Moreover, this template (and its master, the {{User:ClueBot III}} template) are less and less used due to a complexity wall when modifying the back-links after a move. Perhaps could you help with this problem, that appears to be the actual threat ? Best regards. Pldx1 (talk) 19:59, 6 April 2016 (UTC)[reply]

Sorry I don't understand the last two sentences. What is meant by "complexity wall when modifying the back-links"? — Martin (MSGJ · talk) 20:00, 6 April 2016 (UTC)[reply]
See User:ClueBot_III#How_your_page_is_archived. Pldx1 (talk) 21:10, 6 April 2016 (UTC)[reply]

Hi MSGJ, you recently made the above edit to Template:Casenav. I've reverted it – just temporarily – to ask you if you meant to change the appearance of the box or if you just meant to switch to the mbox. In any event, your edit created a significantly different look and feel (white instead of ivory, ~80% width instead of 100%, etc.) that should recieve ArbCom's, or at least the clerks', consent. Thanks. (This edit is in my role as an arbitration clerk, but I am not acting on behalf of the full Committee here.) Kevin (aka L235 · t · c) 13:41, 8 April 2016 (UTC)[reply]

Hi Kevin. I did indeed intend to switch it to standard mbox colors, although I did not envisage this would be controversial. The rationale is to use the width and colors consistent across Wikipedia for these kind of header templates, so a sort of off-white (#f9f9f9) on the project page and the yellowy (#f8eaba) on talk pages. Is there anything you don't like about it? I reject the notion that I should get permission before editing this template, but happy to discuss with you or anyone else interested on the template talk page. Best regards — Martin (MSGJ · talk) 15:36, 8 April 2016 (UTC)[reply]
Thanks for the reply, Martin! I've started a discussion at Template talk:Casenav#Changing the header to an mbox; please feel free to chime in. I've also sent a mail to clerks-l about this. Kevin (aka L235 · t · c) 20:26, 8 April 2016 (UTC)[reply]
Have now replied there — Martin (MSGJ · talk) 20:16, 10 April 2016 (UTC)[reply]

Category question

Why did you remove the suspected hoax category in the Guingon Group of Companies article? TheGGoose (talk) 03:15, 9 April 2016 (UTC)[reply]

(talk page stalker) @TheGGoose: I expect that it was because it was added as a bare category, instead of by using the {{hoax}} template, which is the proper way since it produces a warning message as well as categorising. --Redrose64 (talk) 09:01, 9 April 2016 (UTC)[reply]
I was thinking of that too; the solo category addition is a mistake. TheGGoose (talk) 14:26, 9 April 2016 (UTC)[reply]
Redrose is correct. And as it was already listed as AfD, I decided that the hoax tag would be superfluous. Regards — Martin (MSGJ · talk) 19:11, 10 April 2016 (UTC)[reply]

Template:ArbComBlock Template:Ivory messagebox

Hi User:MSGJ I just noticed that your last [1] to Template:Ivory messagebox broke the Template:ArbComBlock image as you can also see in the Template:Ivory messagebox/testcases. Just thought I'd point it out so it could be fixed as I don't have the ability/permission to fix myself. Cheers KylieTastic (talk) 11:36, 9 April 2016 (UTC)[reply]

Thanks for letting me know. It was using an undocumented parameter in a strange way ... — Martin (MSGJ · talk) 19:10, 10 April 2016 (UTC)[reply]

Milli's edits

See their talk page, as I think they might be on the right track, but ended up breaking many page histories in the process. Kevin Rutherford (talk) 09:41, 14 April 2016 (UTC)[reply]

Why does {{Kazan Metro|right}} cause all that breakage? — Martin (MSGJ · talk) 09:44, 14 April 2016 (UTC)[reply]
Because I overhauled the template to allow for it to better fit into the infobox and to make it look a bit better. As such, it should have never been on the station article to begin with, so I was in the process of removing it when you started doing the same. Kevin Rutherford (talk) 09:47, 14 April 2016 (UTC)[reply]

DYK

Hello! Your submission of Selly Oak Park at the Did You Know nominations page has been reviewed, and some issues with it may need to be clarified. Please review the comment(s) underneath your nomination's entry and respond there as soon as possible. Thank you for contributing to Did You Know! North America1000 05:49, 16 April 2016 (UTC)[reply]

Breach of editing restriction that you enacted.

You may recall that you enacted an editing restriction against Wtshymanski just over a year ago. Wtshymanski, has started breaching that editing restriction, including reverting an IP editor, but disguising it as a regular edit. There is an ANI on the issue at here. It is suffering from a lack of adminstrator action. Could you please take a look? 212.183.128.147 (talk) 15:58, 19 April 2016 (UTC)[reply]