Misplaced Pages

Revision as of 13:32, 5 August 2017

Archives

Protection request

Persistent vandalism just like Song Joong-ki's page due to recent engagement news Pain and Powed (talk) 13:45, 5 July 2017 (UTC) https://en.wikipedia.org/search/?title=Song_Hye-kyo&action=history

14 years!

Happy 14th wiki-anniversary in advance.
—usernamekiran(talk) 12:58, 7 July 2017 (UTC)

Thank you, Usernamekiran, kind of you to notice and say so. :) Samsara 13:17, 7 July 2017 (UTC)

You've got mail!

— fortunavelut luna 14:05, 13 July 2017 (UTC)

Sing (My Chemical Romance song)

I see that on Misplaced Pages:Requests for page protection you said that Sing will be semi-protected for a period of 10 weeks but on the page for Sing I noticed that the page is not protected yet. Bowling is life (talk) 20:54, 13 July 2017 (UTC)

@Bowling is life: The display of locks is not automatic, but done by a template. This is a long term known flaw/feature of mediawiki - there's a link on my userpage if you want to know more about it. Samsara 22:59, 13 July 2017 (UTC)

I've added the template now - you can always check the history to see if something is protected. Samsara 23:02, 13 July 2017 (UTC)

Thanks

Dera Samsara,

Thank you for all you've done in supporting my work on the Sony E-mount lens articles and for talking with User:Usernamekiran. I've been absent as of late due to home life and multiple family emergencies occurring all at once, which has mad doing much difficult as of late. However, I am glad that the majority of the articles in jeopardy have been cleared.

- Raine

Chevy111 (talk) 20:31, 14 July 2017 (UTC)

Thanks for the note, Chevy111 - pleased to meet you! Of course, family must always go first - please take good care of them! I've sometimes thought it unfortunate that some of Misplaced Pages's processes DO work towards a deadline - I personally lean towards Misplaced Pages:There is no deadline#View two: Don't rush to delete articles, but that may not be reflected by the people typically attracted to AfD. I was happy to see that usernamekiran offered to help. I look forward to seeing that collaboration begin, and will try to continue to personally contribute as well. Thanks again, for now, for all the good work you've put in! Looking forward to more. Best, Samsara 15:13, 15 July 2017 (UTC)

Hello Samsara :)
Hi Raine I hope all is well with you, and your family. I wanted to let you know that it wasnt Samsara's words that changed my mind, but it was the passion of both of you that did the trick. :)
Although I respected Samsara before this AfD incident, his polite demeanour through this debacle, and his passion obviously, increased my respect for him further. Also, I am not at all attracted towrds deletion. I always think of deletion as a lost resort, it can be seen here: Misplaced Pages:Articles for deletion/Barel. But unfortunately I have been casting a lot of delete votes recently. The reason I pinged you both, is an essay that I have been working on since almost a month a now. I would appriciate it very much if both you provide your opinions of the talk-page of that essay. Also, this very essay was a reason why I nominated these articles. User:Usernamekiran/Notability (electronic devices). There is no hurry at all regarding your comments. Just to be on the safe-side, I will add a DNAU notice for the bot. I hope Samsara wouldn't mind. :)
See you guys around. —usernamekiran(talk) 19:59, 16 July 2017 (UTC)

Geological ranges in taxoboxes

As present isn't a geological epoch people might not want it used in statements of geological ranges. Recent is an epoch, but the Holocene article states that it is invalid under current rules. My opinion is that Holocene is the appropriate usage, but it might be worth raising the issue at WP:TOL (and other relevant major biological projects). (I changed Cycad to say Holocene, before discovering that you had made similar changes elsewhere.) Lavateraguy (talk) 23:24, 16 July 2017 (UTC)

@Lavateraguy: I did not change any articles that already said "Holocene". I do think "Recent" is potentially confusing, and I observed that many of the more edited articles and many of the higher taxonomic levels (phylum, order, etc.) already used "present", presumably because of this reason. If you want to change all articles to "Holocene", I will not stand in your way, but it's also not a battle I will fight on your behalf. :) As a minor point of interest, I believe I discovered that if the template is given names of epochs as parameters, and if the most recent point is given as any string that isn't recognised as an epoch, the template will behave as though Holocene was specified, and display as though the taxon is extant or extant until "recently" (for some value of "recent" - not sure off-hand how much non-recency a pixel's width would imply). Best, Samsara 02:57, 17 July 2017 (UTC)

PS In some edit summaries, I referenced MOS:JARGON, which arguably bears on this case. Samsara 21:01, 17 July 2017 (UTC)

Category:Disambiguation pages with potential has been nominated for discussion

Category:Disambiguation pages with potential, which you created, has been nominated for possible deletion, merging, or renaming. A discussion is taking place to see if it abides with the categorization guidelines. If you would like to participate in the discussion, you are invited to add your comments at the category's entry on the categories for discussion page. Thank you. Pariah24 (talk) 20:19, 17 July 2017 (UTC)

Microsoft Office 2010 protection

Greeting, Samsara

I wonder if I could have a word with you about the Microsoft Office 2010 article, which you have protected on the grounds of content dispute. I am afraid this is a case of editor harassment, not content dispute.

The 2601:5c2:200:31ae:f15b:f5c2:8a8c:9212 belongs to a very well-known stalker who exclusively chases Codename Lisa around Misplaced Pages and reverts her. (This type of harassment is explained in WP:HOUND.) Although he contributes (=attacks) from different IP addresses, his IP ranges are known. Example of what he did in the past:

• : Committed revert-vandalism in List of typefaces included with Microsoft Windows, brazenly claiming that PP (page protection) won't stop him. (He is unrelated to the IP that originally vandalized that page.)
  • This IP range is blocked by Materialscientist for harassment. Clearly, there has been many other instances of harassment from this range.
• : The edit summary of this revert reads: "Another editor was asking for clarification which you did not provide." No. Not another editor. Codename Lisa herself had asked for clarification. Later changed her own mind. But any excuse for harassment, right?
  • This IP range is blocked by Mr. Stradivarius for harassment.
• , , , : Tried bad-mouthing Codename Lisa in four admin's talk pages. Mr. Stradivarius blocked his IP range.
• : Grossly insulted Mr. Stradivarius for blocking his other IP range.
  • This IP range is blocked by Materialscientist for harassment.
• : Tried to do revert-harassment in ANI. Another admin dealt with it.
  • This IP range is blocked by Materialscientist for harassment.

This isn't a full list. (I am not in the habit of keeping a list of what a third-party does to another third-party.) But Codename Lisa keeps a full list along with IP geolocation information.

Now, you are probably asking what is my interest this matter? Well, Microsoft Office 2010 is now showing wrong info because of the work of a malicious person who was smart enough to write an average edit summary.

FleetCommand (Speak your mind!) 08:39, 21 July 2017 (UTC)

@FleetCommand:

m:WRONG VERSION Samsara 13:07, 21 July 2017 (UTC)

And here is his latest vandalism today: Changing some dates to something random. FleetCommand (Speak your mind!) 08:42, 21 July 2017 (UTC)

I do not have checkuser to confirm that. I'm also concerned that you may be misrepresenting the situation. What triggered my involvement was an edit by RecentEdits who has edited a variety of topics not known to me to have any particular connection with Codename Lisa, and who looks to be an editor in good standing. The edit was summarily reverted partly based on containing weasel words, but that is always poor reasoning as weasel words can simply be removed. Furthermore, no attempt was made to find a source that clearly states that XP is not affected - I would expect this to be easy to do, if only in the phrase "versions of Windows prior to are not affected". As the dispute seemed to be spreading to engulf other articles, I decided to pull the brakes. The reason for this spread may well be the harassment you describe. However, also note that protecting for disputes nearly ALWAYS generates the sort of complaint that you've just shown, which is why (1) (I suspect) most admins pick those "fights" quite carefully, and (2) the mere fact that you responded in this already-anticipated way holds no particular weight. The time would have been better spent on resolving the dispute.

The bottom line is that if you want to build a case page for this harrassment, I'm the wrong person to turn to as I don't have CU available, but it seems to me that a valid question was raised by RecentEdits. Based on your query, I just looked this up, and it turns out that Microsoft does remark on disabling the feature underlying Petya vulnerability in Windows XP. That being true, it would be easy to see how an editor might be frustrated at having the entire material reverted, and suspect a conflict of interest on the part of the reverting editor. So I would encourage you to go to some more effort to convincingly clarify whether this is or isn't an issue that can affect XP and merits inclusion in the article. Petya was front page news, so I think the issue of notability is already sufficiently addressed. We are trying to build a comprehensive encyclopedia, and accusing other editors of this-and-that may not be helpful in this regard, for anyone! Focus on content, not the contributor!

I will always immediately lift full protection as soon as it's clear the conflict has been resolved in the spirit of our goals.

Regards, Samsara 13:07, 21 July 2017 (UTC)

Hello, Samsara

How do you do?

I see that FleetCommand started this post about the Microsoft Office 2010 article but your response is exclusively about the Windows XP article. But there are few mistakes in your message that I feel I must address anyway:

• I do not have checkuser to confirm that. You cannot use CU to confirm that; you need the geolocation tool that you (and I) already have. (CU does something entirely different.) Other people who have attended this case were all admins, such as yourself. The question is: Assuming you could see the truth full and untarnish, would you have attended this case?
• We are trying to build a comprehensive encyclopedia, and accusing other editors of this-and-that may not be helpful in this regard, for anyone! Quite true. But the sordid fact is that vandalism, COI, spam, harassment, socking, hounding, lobbying and disruptive editing has been part of our effort to build this encyclopedia. The important fact is: You say this sentence when you know for sure that the accusation is false and non-constructive.
• Focus on content, not the contributor! If ask so, then so be it. This contribution is false: The source says so.
• I will always immediately lift full protection as soon as it's clear the conflict has been resolved in the spirit of our goals. This person had been hounding me for four years. There is no end and no resolution in view. Of course, I personally do not insist that you lift this protection; it is suboptimal but not a catastrophe at all. (If the situation was serious, I'd have presented my evidence in ANI and asked the admins who previously dealt with the person to reduce the protection.) While you and I are not here for a victory, this certain hound definitely is. And getting this certain poor edit to stick for 8 years is the biggest victory he has achieved to this day. Let's let him have that. After all, he wastes his numbered days in this world on a futile effort to disrupt Misplaced Pages and spends his afterlife getting punished for it. The way I see it, he is the true loser in this whole affair.

By the way, there is something I always wanted to ask you: How do you manage to become an admin with only 23715 edits? That's quite an accomplishment. (No, I am not being sarcastic; I have been to many RFAs.)

Best regards,
Codename Lisa (talk) 16:21, 21 July 2017 (UTC)

RfA

Thank you, Cullen328, for this well thought out note. I should say clearly that withdrawing the !vote was done only for the stated reason - I think it important that we give admin candidates thorough consideration, and - which has been a problem over the last year or so, and is mentioned here as an aside - treat opposers with respect. I saw that some people expressed a belief that admins with particularly well-supported RfAs do not always live up to community expectations (which did not factor into my vote or subsequent withdrawal). I can think of many reasons why this might be so, but I am heartened by you taking criticism seriously, and am hopeful that you can avoid this pitfall.

While I've had active periods as an admin, now isn't one of them, so my "case knowledge" may be limited, but if you ever want to get a second opinion or some such, feel free to call on me. Best wishes, Samsara 07:09, 29 July 2017 (UTC)

Protection on Sean Spicer

Hello. The original expiration date for semi-protection was February 2022. Can it be changed back, or can you extend time a little bit? --George Ho (talk) 04:18, 25 July 2017 (UTC)

 Done Thanks for mentioning it. Samsara 04:21, 25 July 2017 (UTC)

Samsara, having noticed this, I think you might want to look at related issues at White House Press Secretary; for the last two weeks, there has been a slow-moving edit war between a number of different contributors (extended confirmed, autoconfirmed and IP), some of whom are involved at Sean Spicer now. I took the matter to EdJohnston the other day (he had previously banned one of the parties for edit warring), suggesting page protection, but he didn't seem to agree it was warranted (though many of the reversions had not been made at that point). I became aware of the situation after being RfC'd to the talk page, where I found a pretty toxic situation. So after Ed declined my suggestion, I decided the leave the situation alone, rather than take it to RFPP. To be clear, it looks like the edit warring has died down, owing to the sourcing becoming clearer (which is what I was hoping would happen, so no more direct action was necesary), but you may want to review the last couple of pages of the revision history, because there were a couple dozen reverts and some of these editors seem to be edit warring unchecked across multiple pages under discretionary sanctions, relating to American national politics. Snow 04:23, 5 August 2017 (UTC)

Thanks for this. Per policy, White House Press Secretary and Sarah Huckabee Sanders would both need to go under full protection. However, the admin corps is no longer fully supportive of such actions. Regards, Samsara 08:33, 5 August 2017 (UTC)

Huh. I hadn't realized such a strong aversion to full protection had developed. That explains Ed's hesitance. Well, I just hope the edit war ends when the current bone of contention (who is officially press secretary) shortly becomes moot. Unfortunately, having discovered that this contest of wills apparently spans several articles, I suspect that its more likely that this will end with someone falling afoul of discretionary sanctions on the wrong page. Snow 08:55, 5 August 2017 (UTC)

Happening to notice my name in this thread, I looked at White House Press Secretary again. The prior discussion on my talk was at this link. Since problems are ongoing, I've gone ahead with two months of WP:ECP for the article. (User:Ad Orientem had previously applied two days of ECP in late July but this protection had expired). Thank you, EdJohnston (talk) 13:32, 5 August 2017 (UTC)

List of European countreis by average wage

Have a look to User talk : Galgah and hungarian IPs in this page to prevent vandalism and original researches.I already stopped him once.Thanks.Benniejets (talk) 17:04, 29 July 2017 (UTC)

@Benniejets: Your problem is with all the 84.* IPs and with Galgah? Thanks for clarifying. Samsara 17:09, 29 July 2017 (UTC)

They are the same person.84.* is from Budapest area and Galgah writes about hungarian subjects.He also wrote the same things of 84* in the article.User talk:Csalinka is another username of this guy.He uses also this one to write always the same things in the article in the last days.There's evidence and they should be blocked.Thanks again for your attention.Benniejets (talk) 17:12, 29 July 2017 (UTC)

Thanks. I'll see if a rangeblock might be a good solution. Samsara 17:26, 29 July 2017 (UTC)

You realized the not correct position of this guy and the risks for the article to be vandalized with original numbers. Thanks Samsara.

Hi again, Benniejets. Given that there are two logged-in users involved, I would suggest that you report the issue to Misplaced Pages:Sockpuppet investigations. Regards, Samsara 17:49, 29 July 2017 (UTC)

I followed your suggest.What about locking article?ThanksBenniejets (talk) 18:27, 29 July 2017 (UTC)

With up to thirty edits a day, and only one or two coming from those IPs or accounts, I think any protection would be more disruptive than the problematic edits themselves. But once you have a checkuser result, things will be much more straightforward in terms of getting blocks and rangeblocks. Hope this helps, Samsara 19:08, 29 July 2017 (UTC)

Question

I didn't know there was a policy specifically regarding the protection of Latin letters. Can you point me to it? Thanks, Enigma 15:57, 31 July 2017 (UTC)

@Enigmaman: If you look at my RfPP contribs, you'll see that I classify all my actions by subject area, for possible future statistics purposes. Regards, Samsara 19:02, 31 July 2017 (UTC)

A cup of coffee for you!

Thanks for volunteering to do page protection review. Blue Rasberry (talk) 00:06, 4 August 2017 (UTC)

Mail call

pbp 14:09, 4 August 2017 (UTC)

@Purplebackpack89: Replied. Samsara 17:50, 4 August 2017 (UTC)

And replied pbp 18:14, 4 August 2017 (UTC)

Semi for two related articles please?

Morning! You recently semi-protected Linkage disequilibrium after it came off its previous pp and immediately got hit with the same refspam again. Could you please do the same thing for Supergene and Co-adaptation, which are subject to the same treatment? (came off semi and got spammed again right away) Thank you! --Elmidae (talk · contribs) 15:43, 4 August 2017 (UTC)

 Done Thanks. Samsara 15:48, 4 August 2017 (UTC)

Jess Glynne discography

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

What did you mean by "the effect of is not expected to kick in until after the IP first encounters it"? Their pending revision was accepted before I even knew it had happened, by an editor who somehow didn't know it was blatantly false information. This IP will just keep changing the page and having their revision accepted by editors who don't know it's vandalism, then it will need to keep being reverted, so it just feels like there is no protection status on the page at all (or at least, it's not having the intended effect). Ss112 02:21, 5 August 2017 (UTC)

What I meant was that an IP will not reduce editing frequency until after the first time they realise their changes aren't displayed live. @Snow Rise: Your pending change reviewing is being discussed. Samsara 02:27, 5 August 2017 (UTC)

Thank you Samsara, I appreciate the ping. :) Ss112, I studied that edit for a long moment trying to figure out if it was a good faith improvement. Since I was uncertain about it, I should have reviewed the edit history in more detail than I apparently did. I will say this in my defense: looking at it, it seems you didn't leave an edit summary for you revert (which you always should for any reversion, regardless of context), which might have made the back and forth stand out more. That said, Samsara's edit protection notice was just a few items down in the log, so I should have seen the dispute regardless and it was clearly a lapse in my own process. I wouldn't panic about pending changes not being up to the task; it mostly suffices and you're unlikely to get two reviewers in a row missing the context. Since I now know there is a controversy on the sourcing for this content, I will watch the page and reject any identical proposed edit that may be forthcoming from the IP in the next couple of days, with a note that they should take the issue to the talk page (also something your edit summaries should suggest, if you are going to be edit warring with the IP, even if you are on the right side of WP:V). Will that address your concerns? Snow 03:54, 5 August 2017 (UTC)

@Snow Rise: Why are you treating this like a content dispute? They're making up song titles, and adding peaks and certifications that don't even exist. That is blatant vandalism in my eyes. There's nothing to explain in the reverts and if I were not reverting vandalism, I would leave an edit summary. I'm well aware of the etiquette. Anybody can do a simple Google search (if they don't know who Jess Glynne is) and find out that all the songs this IP is insisting on adding don't even exist (at least, they're not hers). It's not a "controversy over sourcing". They are outright inventing information: please look at this diff again. Release dates for albums in 2021, 2027 and beyond? I don't think reverting that needs to be explained and I don't mean to be rude, but I'm stumped as to how you studied that for very long and didn't work out it's not constructive—chart positions and certifications for albums that haven't even been released? Albums coming out in 2035? Same here and here. Obviously the IP is having fun making up things, because what they're adding isn't even consistent between edits. There's nothing for them to discuss, and they won't anyway as I'm sure they're well aware what they're adding is made up. Ss112 04:34, 5 August 2017 (UTC)

You're certainly not required to explain reversion of vandalism in an edit summary, but it's still advisable, precisely because it can prevent any ambiguity about the edit in a situation like this (though I am sorry to have missed the dates that would have flagged that as vandalism, regardless). I'm sorry to have gone out on AGF here where it wasn't warranted, but I'm not sure what more I can do for you but to keep an eye on the page and revert any further repetition of the edit. I can appreciate your being a little frustrated here, but just give the protection scheme a little time; the IP will get tired of this game soon enough, assuming no one repeats my mistake, and my next revert will include an edit summary that flags the issue for any reviewer that comes after me, to reduce the likelihood of that happening. Pending changes protection isn't perfect, but with a little patience, it usually quiets trolling before long. Snow 04:39, 5 August 2017 (UTC)

If you would revert any repetitions of clearly made up albums and singles, that would be appreciated, yes. Thanks. Ss112 04:42, 5 August 2017 (UTC)

Surely: I just wish there was more to be done about the vandal but to freeze them out; they seem to be doing this to other discographies (), but are jumping too rapidly between IPs (which are not, unfortunately, within a blockable range). We'll just have to wait the juvenile behaviour out. Snow 04:58, 5 August 2017 (UTC)