Jump to content

User talk:Materialscientist: Difference between revisions

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Content deleted Content added
m Reverted edits by Dibangoai (talk) to last version by JBW
Line 516: Line 516:
Good morning Materalscientist, I am not an admin, but I think that you are (or may know one). You have helped me in the past to get several articles to "Good" status. I am writing to ask for help in dealing with an editor who persistently inserts "bare URLs" into a page that I created more than a decade ago. I, as well as various other editors have tried clean up the persistent edits of an editor known as "MountainHiker" who has reverted attempts to conform to good Wikipedia formatting standards and now is posting private URLs on the article, [[The Preserve at Sharp Mountain, Georgia]]. In particular, "MountainHiker" continues to insert a private bare URL that is "members only" and not accessible to Wikipedia community. Further, "MountainHiker" persists in including a redundant "frontend website" bare URL that is already referenced correctly in the External links section. After I (and several others) have tried to correct these edits, I give up and am passing it up the line (through you) to block this editor or protect the article as you see appropriate. Thanks. ''<b>&nbsp;&#8259;&nbsp;<font style="font-family: Verdana">[[User:Firewall|<span style="color:red">Fire</span><span style="color:blue">wall</span>]]</font></b>'' 15:32, 22 December 2023 (UTC)
Good morning Materalscientist, I am not an admin, but I think that you are (or may know one). You have helped me in the past to get several articles to "Good" status. I am writing to ask for help in dealing with an editor who persistently inserts "bare URLs" into a page that I created more than a decade ago. I, as well as various other editors have tried clean up the persistent edits of an editor known as "MountainHiker" who has reverted attempts to conform to good Wikipedia formatting standards and now is posting private URLs on the article, [[The Preserve at Sharp Mountain, Georgia]]. In particular, "MountainHiker" continues to insert a private bare URL that is "members only" and not accessible to Wikipedia community. Further, "MountainHiker" persists in including a redundant "frontend website" bare URL that is already referenced correctly in the External links section. After I (and several others) have tried to correct these edits, I give up and am passing it up the line (through you) to block this editor or protect the article as you see appropriate. Thanks. ''<b>&nbsp;&#8259;&nbsp;<font style="font-family: Verdana">[[User:Firewall|<span style="color:red">Fire</span><span style="color:blue">wall</span>]]</font></b>'' 15:32, 22 December 2023 (UTC)
:Please do explain this issue to MountainHiker on their talk, especially the inaccessibility of the links - this is important. As to formatting, usually experienced editors bear with it, because we have semi-automatic tools that improve bare urls, such as https://refill.toolforge.org/. Very often editors are much more understanding than we think, and quickly straighten up their attitude without admin intervention (which should be a last resort). [[User:Materialscientist|Materialscientist]] ([[User talk:Materialscientist#top|talk]]) 23:07, 22 December 2023 (UTC)
:Please do explain this issue to MountainHiker on their talk, especially the inaccessibility of the links - this is important. As to formatting, usually experienced editors bear with it, because we have semi-automatic tools that improve bare urls, such as https://refill.toolforge.org/. Very often editors are much more understanding than we think, and quickly straighten up their attitude without admin intervention (which should be a last resort). [[User:Materialscientist|Materialscientist]] ([[User talk:Materialscientist#top|talk]]) 23:07, 22 December 2023 (UTC)
::As you suggested, I left a note at User talk:MountainHiker explaining the various problems with recent edits by MountainHiker-- in particular the inclusion of a private bare URL that is "members only" and not accessible to Wikipedia community. I have not reverted MountainHiker's most recent edit, but instead encouraged MountainHiker to remove/fix the most recent edits without intervention by another editor. We'll see if MountainHiker takes the suggestions to heart. If after a week or so, there is not correction, I will revert MountainHiker's most recent edit as nothing will be lost in the article [[The Preserve at Sharp Mountain, Georgia]] since one of the bare URLs inserted by MountainHiker is already listed in the External links section and the other is a private URL which should not appear in the article. ''<b>&nbsp;&#8259;&nbsp;<font style="font-family: Verdana">[[User:Firewall|<span style="color:red">Fire</span><span style="color:blue">wall</span>]]</font></b>'' 21:22, 24 December 2023 (UTC)


== 2A02:842A:1BF:1901:0:0:0:0/64 ==
== 2A02:842A:1BF:1901:0:0:0:0/64 ==

Revision as of 21:22, 24 December 2023



IPBE FYI

Hello! :) Just FYI I've pulled IPBE from Aman.kumar.goel (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log· investigate · cuwiki) per the findings here. I pinged you in the SPI but forgot that you don't get those so am just flagging it here. firefly ( t · c ) 16:09, 3 December 2023 (UTC)[reply]

Pulling IPBE is Ok with me. I couldn't see this coming when granting it. Materialscientist (talk) 21:11, 3 December 2023 (UTC)[reply]

Zavier Cut Up The Water Heater Box

Hey! You! You dig my nose!

Te lauya te Speedy Gonzales mai deks water heater box!

Te Zavier Gonzales!

Water Heater box being cut up by Zavier! 2402:1980:82D4:2005:0:0:0:1 (talk) 06:00, 17 December 2023 (UTC)[reply]

Chakswari

Please Chakswari page as you have locked it. It is incomplete.

I am from Kalyal Chakswari and can trace my last 7 generations back to Chakswari. 2A00:23C8:D48F:5301:DB55:5C59:EAD2:3A30 (talk) 00:11, 4 December 2023 (UTC)[reply]

Requesting a range block

An IP editor on range 2603:8000:2A00:0:0:0:0:0/41 has persistently added unreferenced, poorly referenced, and highly POV material to articles. They also have a history of edit-warring to retain their unsourced additions going back at least to July (when I first encountered them). They generally refuse to use an edit summary, save for rare exceptions like today's name-calling of Low Protestant imbecile (which isn't even true). I would appreciate a range block, as the damage is spread across a wide variety of topics and this range appears to be used almost exclusively by the disruptive editor, so minimal collateral. You blocked at least one IP on this range within the last 24h. ~ Pbritti (talk) 01:06, 4 December 2023 (UTC)[reply]

Blocked. Materialscientist (talk) 01:08, 4 December 2023 (UTC)[reply]
Thanks! Please let me know if I should come back if the same issues continue post-block. Best, ~ Pbritti (talk) 01:11, 4 December 2023 (UTC)[reply]

Your revert

How exactly was this edit not constructive? I reverted the insertion of an unsourced claim. 62.73.69.121 (talk) 07:05, 4 December 2023 (UTC)[reply]

Please do not revert without checking the cited source.
G-INFO shows that the aircraft in question is not currently airworthy.
By reverting my correction, you are perpetuating incorrect information. 146.200.131.19 (talk) 02:23, 5 December 2023 (UTC)[reply]

Shtreimel

Materialscientist, you reverted 2 of my edits. One of them clarified that the shtreimel was probably not Turkish/Anatolian as that suggests a Near Eastern/Mediterranean origin of a hat worn in cold climates (which is implausible). You additionally reverted an edit I made that claimed some scholars believe the shtreimel was of Central Asian origin. I did not link the publication, I apologize as I should have. 148.76.179.7 (talk) 07:44, 4 December 2023 (UTC)[reply]

separate article about women in bangladesh police should be kept

@Materialscientist:, A separate article should be kept about 'Women in Bangladesh Police', writings will be elaborated, please wait. নূর-এ-আলম সিদ্দিকী (talk) 11:25, 4 December 2023 (UTC)[reply]

Range Block Request

There's an IP editor on the range 2601:408:C500:2000:0:0:0:0/64 who adds unnecessary info next to show names on award ceremony articles and/or a person's accolade page. Please block them for disruptive editing Scoophole2021 (talk). 11:56, 4 December 2023 (UTC)[reply]

FYI

Hello, Materialscientist. Please check your email; you've got mail!
It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the {{You've got mail}} or {{ygm}} template.

Miss Charm

Contrary to your statement regarding my edit which was "unexplained", here's the link to that. Special:MobileDiff/1188407111

It would be kind and best for you to revert it. Thanks. 180.195.115.174 (talk) 06:33, 5 December 2023 (UTC)[reply]

Thanks for reverting it. Appreciated it. 180.195.115.174 (talk) 07:04, 5 December 2023 (UTC)[reply]

Madison Hotel

Hey, I certainly hope this is how one gets in touch with you. My apologies if I got it wrong. Much appreciated that you followed up with the post on Madison Hotel, however I can assure you it is VERY closed. The best source I can offer is the updated street view as well as having been in front of the hotel myself last month. If I can provide any more information, let me know. But if you search the property itself it is gone and Google is in the process of updating the listing as well. I hope that helps. Thanks

Question

Hi there, there are several pages who's subjects are former NFL players who have been out of football for awhile now but their pages are still PC protected. These pages are:

Is PC really necessary for these pages anymore? And if not, can you please reset those settings for all the above pages? Ambertuck (talk) 23:37, 5 December 2023 (UTC)[reply]

Unprotected. Materialscientist (talk) 01:44, 6 December 2023 (UTC)[reply]

Erick Fedde

You didn’t make a mistake. Fedde’s deal is still pending a physical. Can you lock the article until the deal is official? Thank you. 174.228.65.107 (talk) 00:12, 6 December 2023 (UTC)[reply]

A barnstar for you!

The Anti-Vandalism Barnstar
I've seen you around erasing vandalism faster than I can blink, so I'm going to pile on your barnstar collection because you're amazing and you blocked the IP that vandalized my talk page. ❤HistoryTheorist❤ 00:56, 6 December 2023 (UTC)[reply]

Sophie

I added her real name as it appears on her marriage certificate. It’s not something I am particularly adamant needs to be on the article. She kept it private for a reason. Jamesington (talk) 01:30, 6 December 2023 (UTC)[reply]

Correcting pages by the person being discussed like me Mike Kernell MikeKernell (talk) 03:07, 6 December 2023 (UTC)[reply]

Bio

I like to correct the page about me and y’all won’t let me. Mike Kernell St. Rep.Tn 1974-2012 MikeKernell (talk) 03:09, 6 December 2023 (UTC)[reply]

What should I do in the future when encountering someone like AnonBlogs?

I gave them warnings on their talk page User_talk:AnonBlogs but is there something else I should do? Immanuelle ❤️💚💙 (talk to the cutest Wikipedian) 07:40, 6 December 2023 (UTC)[reply]

email

I've emailed you about something that requires urgent attention. Please check at your earliest convenience. Thanks, SamX [talk · contribs] 08:21, 6 December 2023 (UTC)[reply]

Done. Materialscientist (talk) 08:24, 6 December 2023 (UTC)[reply]

Mike Kernell

I don’t know about pings or if this will get to you. My school was wrong, election year was wrong, David died in 2018,ect. The source is me- Mike Kernell Do I need to get a source to write a true bio? Mike Kernell

Constructive criticism

When [username:Person X] edits the article on [Person X], and claims to be making changes based on their personal knowledge, I think it's incumbent upon us to not just use one of the templated "I've reverted your edits" messages. They need something that's obviously a note from a human. DS (talk) 20:58, 6 December 2023 (UTC)[reply]

Thanks, will try to talk to them next time. Virtually all such changes are replacing sourced information with unsourced one, thus the revert reason is obvious, and it is hard to add something meaningful to the template. Materialscientist (talk) 21:17, 6 December 2023 (UTC)[reply]

Block

Hello! I want to ask why my new IP address is blocked. I changed my internet provider today. How come this address is blocked? Gasforth-2021 (talk) 23:31, 6 December 2023 (UTC)[reply]

Mark Brunnel Edits

Hi there, I've added reason for edits several times. The latest edits are well explained. Please let me know if I'm doing something wrong. Ericlmitchell (talk) 23:39, 6 December 2023 (UTC)[reply]

User 24.224.240.102

User 24.224.240.102 is a school so there are meny people so you should probably permanently ban them from editing. NormalHuman1 (talk) 17:14, 7 December 2023 (UTC)[reply]

Thanks. What school is it? Materialscientist (talk) 21:08, 7 December 2023 (UTC)[reply]
https://en.wikipedia.org/wiki/Kensington_Intermediate_Senior_High_School
The one in this wikipedia page NormalHuman1 (talk) 23:52, 7 December 2023 (UTC)[reply]
Thanks. Materialscientist (talk) 23:53, 7 December 2023 (UTC)[reply]

First National Lacrosse Assocation

Information on First Nations Lacrosse Association (FNLA) was moved and cited properly to Haudenosaunee men's national lacrosse team, Haudenosaunee men's national under-19 lacrosse team, Haudenosaunee women's national lacrosse team, Haudenosaunee women's national under-19 lacrosse team, and Haudenosaunee national indoor lacrosse team. The FNLA is a Lacrosse Canada Member organization, which was cited. Faaksee (talk) 00:40, 8 December 2023 (UTC)[reply]

Neil Duff

There is no citation or reference I can find for this information, however I've watched him play in his last handful of tournaments and I personally throw the same dart. Given it's a winmau pro design barrel, it makes it a unique design and, from the two different grip levels and colour profile, unmistakeable. He's currently playing with them in the 2023 WDF World Championships, rather than his old 23g RedDragon darts as was listed on his wiki.

An arrow to the heart of her/his psyche? BlueWren0123 (talk) 08:17, 8 December 2023 (UTC)[reply]

Medidata

I'd be interested in learning why WP:NOTADIRECTORY is an "invalid rationale" Thanks. 76.14.122.5 (talk) 03:44, 8 December 2023 (UTC)[reply]

What you removed was not a loose list, but two sentences describing pertinent details, such as location of headquarters and geographical presence worldwide. This is definitely not what NOTADIRECTORY is about. Materialscientist (talk) 04:09, 8 December 2023 (UTC)[reply]
Thank you. 76.14.122.5 (talk) 04:20, 8 December 2023 (UTC)[reply]

was actually relevant, although it was formatted wrong. Just letting you know. Prezbo (talk) 14:48, 8 December 2023 (UTC)[reply]

IPv6 user removing refs

Hi there,

I first sought a recently-active admin (Muboshgu), but they said they didn't have the technical capabilities for to block an IPv6 user. Reaching out to you as you warned this user as well.

I noticed an IP user has been removing cites and adding unsourced content, mostly to firefighting-related articles, all without explanation. I've tried warning them ([1][2][3]), but they appear to have a moving(?) IP address and the actions haven't ceased. Any help is appreciated, thanks!

Sorted 3 IPv6 addresses:

2603:9000:9900:510b:3973:b20d:3ffe:4b08
2603:9000:9900:510b:493d:765d:2c6b:cbbe
2603:9000:9900:510b:59bc:703d:ecf1:63a7
Total
affected
Affected
addresses
Given
addresses
Range Contribs
1 /64 1 /64 3 2603:9000:9900:510b::/64 contribs

Wracking talk! 19:00, 8 December 2023 (UTC)[reply]

I've semiprotected Santa Clara County Fire Department. Blocking would cause too much collateral. Materialscientist (talk) 21:44, 8 December 2023 (UTC)[reply]
Makes sense, thanks! Wracking talk! 00:14, 9 December 2023 (UTC)[reply]

Good article reassessment for Liquid crystal

Liquid crystal has been nominated for a good article reassessment. If you are interested in the discussion, please participate by adding your comments to the reassessment page. If concerns are not addressed during the review period, the good article status may be removed from the article. ~~ AirshipJungleman29 (talk) 20:21, 8 December 2023 (UTC)[reply]

Please Slow Down

I know I've mentioned this at least once before (though it was a while ago), but please slow down with the block button. There is no need to block without warning for this routine disruptive editing, and it is absolutely overkill to be indeffing a registered account after only one disruptive edit without any warnings (I was literally in the process of leaving a {{welcomevandal}} on their talk when you blocked them). Unless the vandalism/disruption is egregious (i.e. racist rants, etc.) or unless the user is flooding the filter log with attempted vandalism, please always issue at least one warning before blocking. Taking Out The Trash (talk) 22:32, 8 December 2023 (UTC)[reply]

Thanks for feedback. Please look both at the edits and filter logs. Materialscientist (talk) 22:34, 8 December 2023 (UTC)[reply]
For the account in particular, unless something has been deleted, I see one single instance of vandalism (and a corresponding filter log hit). That's it. And the nature of the vandalism isn't particularly egregious either... run of the mill disruption. Not something that needs an immediate indef without warning. Taking Out The Trash (talk) 22:45, 8 December 2023 (UTC)[reply]
I am always happy to unblock upon a reasonable unblock request. Vandalism is "not Ok", I daily see missed reverts, months or even years after the edit. Materialscientist (talk) 22:48, 8 December 2023 (UTC)[reply]
Nobody said that vandalism is "ok". The issue here is that you are being too hasty with blocking for vandalism. In the vast majority of cases users need to receive at least three, generally four, warnings before AIV will take action on a vandalism report. Baring exceptional circumstances, if a report from a non-admin to AIV would be declined on the basis of "not enough warnings", you shouldn't block unilaterally either. Taking Out The Trash (talk) 22:51, 8 December 2023 (UTC)[reply]
I know where this is coming from, but this advice is not a policy, and has long been abandoned. Please note that this is not my opinion, but a common WP:AIV practice. Further, you can find a similar message from Jimbo Wales (that obvious vandals should be blocked on sight) in his talk page archives. Materialscientist (talk) 22:56, 8 December 2023 (UTC)[reply]
As an admin who patrols AIV, as well as edit filters, I think most of what Taking Out The Trash has written is inaccurate.-- Ponyobons mots 22:57, 8 December 2023 (UTC)[reply]
I see reports to AIV declined on the basis of the user having not been given enough warnings all the time. The only cases when blocking without warning is appropriate is for egregious vandalism, like racism, or severe BLP issues, or other stuff like that. Routine run-of-the-mill disruption/blanking/whatever, should go through the warning series first. Taking Out The Trash (talk) 22:59, 8 December 2023 (UTC)[reply]
Please understand, that what you are saying is not a policy or even a guideline, but is a matter of choice for a given admin. Materialscientist (talk) 23:01, 8 December 2023 (UTC)[reply]
All warnings are not on the vandal's talk page. They are often warned when they trip filters, explaining what the issue is with their edit. Admins will often review the logs in addition to the talk page. The idea that a vandal has to go through all stages of warnings 1 - 4 is outdated.-- Ponyobons mots 23:04, 8 December 2023 (UTC)[reply]
They absolutely do not need four warnings but even in this day and age I don't think a lot of people realise that their changes will go live immediately so in general they should be told "yes, that worked, please don't do it again", then "that's disruptive and we'll block you if you carry on". I count the edit filter warnings towards this. Hate speech, libel, etc, should be met with an immediate block. I agree with TOTT that the block of the account was premature and would have been declined at AIV. HJ Mitchell | Penny for your thoughts? 08:26, 9 December 2023 (UTC)[reply]
Many times you take the appropriate action. Many times you act so rapidly and without clear explanation. A few weeks ago there was a recommendation made to you to explain more when you revert. Recently you have criticized an editor for not explaining their edit, because you wrote, even editors of long standing do that.
The rapid aspect of your activity is what has been mentioned. Please Slow Down. BlueWren0123 (talk) 23:42, 8 December 2023 (UTC)[reply]
If you have substantive examples of a problem, present them. Otherwise, please gain some experience before waving your hands. Johnuniq (talk) 00:07, 9 December 2023 (UTC)[reply]
Please quantify the level of experience required before I am permitted to express a view.
The fundamental principles of Wikipedia may be summarized in five "pillars":
WP:5P4 Wikipedia's editors should treat each other with respect and civility.
Do I need your permission to 'wave my hands'. Are only Administrators who have been around for years allowed to speak? BlueWren0123 (talk) 00:35, 9 December 2023 (UTC)[reply]
@Taking Out The Trash: There are at least two reasons reports at AIV are declined when the user has not been properly warned. First is the minor issue that patrolling a noticeboard like that is mind-numbing in that it goes on forever and ever. That means an admin might want to spend a minimum amount of time considering each report and if there are no warnings it is simplest to just reject the report. Second is the big point that Wikipedia relies on empowering everyone to at least some degree and dealing with bad edits by referring everything to an admin is not scalable. Non-admins should take on a fair bit of the burden and try to explain procedures to new editors in the hope that some of them are just trying things out and will settle down. So, an admin might decline an AIV report because not all the boxes have been ticked by the reporting editor because the burden needs to be shared. However, if that same admin encounters an obviously bad editor, the admin might just indef them without any fanfare because the admin has seen the story countless times and understands when warnings are a waste of time. For another example of how the times change, ten years ago editors were strongly discouraged from reverting misguided comments or edit requests on talk pages. Now, it is very common for those comments to be rolled back without thought because the incoming nonsense would otherwise be overwhelming. Johnuniq (talk) 00:07, 9 December 2023 (UTC)[reply]
Thanks. Yes, we do block on sight obvious, and especially returning vandals/spammers, but we (at least I) do go through all 3-4 levels of warning when the editor does not mean to do harm, and does it per ignorance. Such editors are often not blocked at AIV, and even if blocked, the block duration is minimal. Materialscientist (talk) 00:12, 9 December 2023 (UTC)[reply]

None of this sufficiently explains why it was acceptable/appropriate to indef the user account linked above after one single non-egregious disruptive edit that didn't even trigger any filter warnings, let alone without any talk page warnings (as I noted, the account was blocked while I was in the middle of leaving a welcome-vandal template). Taking Out The Trash (talk) 00:54, 9 December 2023 (UTC)[reply]

Because patrolling AIV requires thousands of judgment calls, and a block for vandalizing the name of a sports ball player is a reasonable judgement based on having seen hundreds of similar editors contribute that behavior. The purpose of blocking is to prevent disruption. There's no rule, or even common practice, to wait until a requisite amount of disruption has occurred.
They're have been times where I've left a warning as Materialscientist blocked, and also times where as I blocked they had left a warning. Each admin that patrols AIV, UAA, and filter logs makes these judgment calls thousands of times, and you've provided a couple examples of blocks you don't agree with due to lack of warnings, not because the edits in question were not disruptive. I don't see an issue here. ScottishFinnishRadish (talk) 01:33, 9 December 2023 (UTC)[reply]
Could you please relate your views to wp:aiv where it states:
Important! Please remember the following:
2. Except for egregious cases, the user must have been given enough warning(s) to stop their disruptive behavior.
Is it possible that what you say is wp:or? BlueWren0123 (talk) 02:12, 9 December 2023 (UTC)[reply]
OR is a content policy and doesn't apply. My view is based on my experience of patrolling AIV and UAA and having made thousands of blocks based on the reports. Materialscientist has made degrees of magnitude more blocks than have, and you're concerned about how many? ScottishFinnishRadish (talk) 02:21, 9 December 2023 (UTC)[reply]
Hi BlueWren0123. The AIV process guidelines tell non-administrators how to best file something that an administrator can action quickly. For the actual policy in play here: see WP:VAND. For example, the policy says "warnings are by no means a prerequisite for blocking a vandal (although administrators usually block only when multiple warnings have been issued)". WP:OR has no bearing here, as it applies to article content. Firefangledfeathers (talk / contribs) 02:21, 9 December 2023 (UTC)[reply]
There is a reason for existence of that green poster at AIV - many editors file a report there, while they should have used other means and venues. Materialscientist (talk) 02:26, 9 December 2023 (UTC)[reply]
Yes I agree that or is directed to article content. I intended to show an approach being taken and just used it as an abbreviation. All of this is getting away from the original point which is
Please Slow Down.
Materialscientist does much that is valuable.
Taking Out The Trash is asking for Please Slow Down.
Both can be true. BlueWren0123 (talk) 02:32, 9 December 2023 (UTC)[reply]
For what it’s worth, I have also found myself feeling concerned before about blocks after a single (non-egregious) edit - mainly out of a worry for biting. I also appreciate, though, that administrators have a judgement call to make whenever they come across an account that’s made such an edit/such edits. I find myself wondering if this subject would benefit from a discussion at Wikipedia talk:Blocking policy or somewhere similar. All the best, user:A smart kittenmeow 06:35, 9 December 2023 (UTC)[reply]
Ok, I've unblocked the discussed user (Kotv22). Materialscientist (talk) 06:37, 9 December 2023 (UTC)[reply]
I support and agree with your rationale for many of your blocks. I had/have not looked at your reasoning for Kotv22. Many editors do not require 4 warnings before a block. It depends. Life is complicated. An editor may just insert a random combination of characters and just demonstrate immaturity. Another may insert offensive edits. Another may threaten. In my opinion these should be responded to in a different manner. The experience of an admin to assess the appropriate response is invaluable. When the response appears almost automated, I am concerned. Are the barbarians at the gates? BlueWren0123 (talk) 23:43, 9 December 2023 (UTC)[reply]
There are barbarians at all the gates, halfway up the walls, tunneling under the ground, and catapulting over the parapets. Many are already inside the city. Firefangledfeathers (talk / contribs) 03:36, 10 December 2023 (UTC)[reply]
Correct. And "many" likely means "many tens of thousands" (depending on degree of vandalism/spam). They (their edits that we missed) hide behind millions of our articles. Materialscientist (talk) 03:42, 10 December 2023 (UTC)[reply]
It may have been unwise of me to add the last sentence as I intended the rest of the comment to have more weight. In my mind the process of an admin considering their actions rather than an almost automated response is the more significant point. BlueWren0123 (talk) 09:35, 10 December 2023 (UTC)[reply]
The barbarians will always be at the gates. Vandalism is a fact of life. Just as there has been graffiti for as long as there have been surfaces to deface, there will be unhelpful edits for as long as anyone can edit Wikipedia. Most vandals aren't malicious, they're bored or they want to vent their opinion on something they read on the Internet. Many will go away if we tell them they're being disruptive. We shouldn't get into a siege mentality. HJ Mitchell | Penny for your thoughts? 19:51, 10 December 2023 (UTC)[reply]
I love those vandals who return and revert their edits. Most of them don't. And we don't (notice those edits). That's the problem .. Materialscientist (talk) 21:05, 10 December 2023 (UTC)[reply]

Editing Chinese Canadians

Apologizes for the edit, but I made a slight error when making edits with that section in Chinese Canadians. Instead of removing portions that I deemed unfit for the section and then adding or rewording some portions I seemed to have removed portions I would've kept. Also you mentioned that they were not constructive, I don't seem to understand what you mean by that. The edits I made have made the section more neutral and also concise and clear. I also believed it need more imagery. But if you disagree, please let me know! Jut008 (talk) 23:21, 8 December 2023 (UTC)[reply]

template:surname

I see your edits like:

Ivashchenko‎ diff hist +8‎ Materialscientist talk contribs (clean up, replaced: {{surname → {{surname|2=nocat)

category:Surnames says "For convenience, all surnames should be included in this category. This includes all surnames that can also be found in the subcategories." I see it also says " However, do not use the template on disambiguation pages that contain a list of people by family name." But Ivashchenko is not a disambiguation page. So, what is your rationale for these edits? - Altenmann >talk 06:17, 9 December 2023 (UTC)[reply]

Removal of unnecessary parent category (Category:Surnames). Plus occasional cleanup. Materialscientist (talk) 06:19, 9 December 2023 (UTC)[reply]
Once again, the parent category explicitly says "all surnames should be included in this category. This includes all surnames that can also be found in the subcategories". What makes you think it is unnecessary? - Altenmann >talk 06:21, 9 December 2023 (UTC)[reply]
Good point. I don't see the reason for that hatnote, and will try to find it out. Meanwhile, I'll terminate the AWB run. Materialscientist (talk) 06:24, 9 December 2023 (UTC)[reply]
I have personally found the catch-it-all category useful for double-checking similarly spelt surnames. Also Wikimedia category browser is extremely unwieldy when, eg, I want to browse all villages in Belarus. I have to traverse all this tree of Region and District subcategories. Or, more recntly, I wanted to compare category:Massacres" with category:Mass murders for (mis)consistencies, but quickly gave up. - Altenmann >talk 06:27, 9 December 2023 (UTC)[reply]
I know what you mean .. not from surnames, but from image categorization on Commons. Materialscientist (talk) 06:30, 9 December 2023 (UTC)[reply]
I too find it convenient to have Category:Surnames fully populated. I run queries such as 'incategory:Surnames student' to find updates where a young person added their own name. Wire723 (talk) 18:12, 9 December 2023 (UTC)[reply]

Socks?

See User:Patil megha already blocked.

New accounts:
User:Ashwini Balagi
User:PriyankaJadav
User:Bhavyashree hegde
User:Suman palled
User:Shwetasadhunavar
User:Mallu Telabakkanavar
User:Sukanya Mudhol
User:Baligar Sanjana
User:Vinayak S A
User:Bengerilakshmi
User:Nivedita Belagali
User:Saikiran R S Cahk (talk) 08:35, 9 December 2023 (UTC)[reply]

@Cahk: I saw a few of these yesterday. My guess is a spambot. MS might be able to see if there's an easily blockable underlying IP/range. I've blocked all the accounts. HJ Mitchell | Penny for your thoughts? 09:31, 9 December 2023 (UTC)[reply]
@HJ Mitchell: In that case:

User:Veena chikkamath
User:Padmakurli
User:Rashmi yaliwal
User:Dhanya hegde
User:Vandana S K
User:Bharathgoudaa
User:Abhipanda1234
User:Apeksha anand hesarur
User:Tamim mangoli
User:Priyanaka patil05
User:Sahana C Shivabasayyanavar
User:Vidyacgouda
User:Bhushan.p.bhat
User:Ujwalangrampurohit
User:JssChaitra
--Cahk (talk) 09:42, 9 December 2023 (UTC)[reply]

Blocked them as well. Interesting that some of these accounts have been around a while. It could be multiple people with off-wiki coordination but I suppose it doesn't really matter unless one of them appeals the block. Might it be worth pursuing blacklisting of the domain or do you think they'd just evade that? HJ Mitchell | Penny for your thoughts? 10:10, 9 December 2023 (UTC)[reply]
@HJ Mitchell: Blacklist could be a good starting point, but we both know Wiki's spam filtering capabilities leave something to be desired.--Cahk (talk) 10:23, 9 December 2023 (UTC)[reply]
The underlying ranges are notoriously spammy, huge and dynamic; they have been and remain an unsolved problem for admins and checkusers. Materialscientist (talk) 10:31, 9 December 2023 (UTC)[reply]
Quelle surprise. Blacklisting and/or filters is probably the way to go. HJ Mitchell | Penny for your thoughts? 10:56, 9 December 2023 (UTC)[reply]

Holiday Greetings

Peace is a state of balance and understanding in yourself and between others, where respect is gained by the acceptance of differences, tolerance persists, conflicts are resolved through dialog, people's rights are respected and their voices are heard, and everyone is at their highest point of serenity without social tension. Happy Holidays to you and yours. Hope all is well in your corner of WikiWorld! ―Buster7 

I have an angry IP user on my talk page making some vague threats of legal action. What's the best way to deal with this, in your opinion? A type of cabinet (talk) 21:46, 9 December 2023 (UTC)[reply]

This is not a legal threat, but just an editing dispute. You can decide how to handle it - stand your grounds, give up, etc. Materialscientist (talk) 21:49, 9 December 2023 (UTC)[reply]
Never mind. Scottish gave them a temporary block right after you replied.
Taylor Swift fans... A type of cabinet (talk) 21:53, 9 December 2023 (UTC)[reply]

Sorry

It is late and the sleeping pills are kicking in I am so sorry😅 Notsayingmyname (talk) 04:43, 10 December 2023 (UTC)[reply]

Mtel (Montenegro)

I have added a source for the CEO change in this edit. The full company name is also visible on that website, as well as on its "About" page. Why are you reverting the edits now? 92.241.157.193 (talk) 05:35, 10 December 2023 (UTC)[reply]

Thanks, I have reverted myself. Materialscientist (talk) 05:37, 10 December 2023 (UTC)[reply]

Eminem

why did you undo my edit on the Eminem article AwesomeJewishMan446 (talk) 07:59, 10 December 2023 (UTC)[reply]

I couldn't parse your replacement [4]. Materialscientist (talk) 08:02, 10 December 2023 (UTC)[reply]
in the quote, and you know something is a quote when it has " marks, the Eminem article used a quote where Eminem addressed misogyny in his songs by saying "my overall look on things is a lot more mature than it used to be." For some reason that's in the homophobic section of the Eminem article, even thought Eminem wasn't even talking about homophobia in that quote. So I changed the quote and removed the quotation marks to make it a regular sentence instead of a quote, and for some reason my edits get reverted. And other constructive edits on the Eminem article get reverted too. I honestly don't know what's so serious about changing a few sentences in a wiki article AwesomeJewishMan446 (talk) 08:14, 10 December 2023 (UTC)[reply]

Riverbanks Zoo

May I ask why you reverted my edit to Riverbanks Zoo that added the street address? 204.116.251.194 (talk) 08:12, 10 December 2023 (UTC)[reply]

We usually don't add street address into infobox of any article, only location. Materialscientist (talk) 08:14, 10 December 2023 (UTC)[reply]

Mont Aiguille in France

Are you a robot or AI? I identified a place in the movie. It is not some figures or opinion. So what source do you want? 45.64.243.230 (talk) 14:02, 10 December 2023 (UTC)[reply]

Sockpuppets?

Can you check is these users are socks? User:Viishhaaal
User:Dashan Ghasan
User:AmNaTi200
User:Auhabeeb
User:Ijick . Juvalkjolly (talk) 14:37, 10 December 2023 (UTC)[reply]

David Lammy

2A00:23C6:2722:B01:0:0:0:0/64 (talk · contribs · deleted contribs · filter log · WHOIS · RBLs · block user · block log) Any chance of a week pblock from David Lammy for this IP? They started with[5] which asked them to discuss in an edit summary. They continued with[6][7], for which the were warned[8] and I also tried something less templatey[9]. They responded with[10] and the edit you reverted[11]. It could be, expanding a lot of good faith, that it's a case of 'they can't here you'. -- LCU ActivelyDisinterested «@» °∆t° 15:22, 11 December 2023 (UTC)[reply]

Done. Materialscientist (talk) 20:21, 11 December 2023 (UTC)[reply]
Thanks Materialscientist. -- LCU ActivelyDisinterested «@» °∆t° 21:00, 11 December 2023 (UTC)[reply]

Caños de Carmona

Sorry but there is no vandalism, I simply inserted the Template:Infobox_ancient_site Best regards

Nagorno-Karabakh

Hi there, I noticed that you reverted an edit on "Visa requirements for New Zealand citizens" regarding Nagorno-Karabakh. The user who changed it is correct though; this is no longer in place as Nagorno-Karabakh is now under Azeri control and subject to normal Azeri immigration control. As a consequence, visiting Nagorno-Karabakh could not make you persona non grata in Azerbaijan as it is now effectively Azerbaijan itself. Regardless of whether you agree with the politics, this is the situation from an immigration/visa point of view. I couldn't figure out how to revert it back and thought it would be rude and disrespectful to you just do that even if I knew how. Thanks Mike 219.89.209.87 (talk) 08:53, 12 December 2023 (UTC)[reply]

Explanation

I found this explanation in the introduction of the article "Nagorno-Karabakh"

"On 19 September 2023, after a blockade lasting several months, Azerbaijan launched a fresh large-scale military offensive in Nagorno-Karabakh. The Artsakh forces collapsed rapidly, resulting in an Azerbaijani victory, the dissolution of the Republic of Artsakh, the exodus of almost the entire Armenian population from the region and the entry of Azerbaijani security forces into the former Artsakh capital, Stepanakert (Khankendi)."

Thanks

219.89.209.87 (talk) 08:58, 12 December 2023 (UTC)[reply]

Grae Cleugh

Hi Please do not Remove Grae Cleugh. He won an Olivier award in 2002 while a student at RSAMD. A quick google search will confirm. 81.147.111.139 (talk) 12:02, 12 December 2023 (UTC)[reply]

Could you please revert your removal. The page has been protected to prevent vandalism! check Laurence Olivier Award for Most Promising Playwright, 2002 Laurence Olivier Awards, https://www.doollee.com/PlaywrightsC/cleugh-grae.php, and https://www.bloomsbury.com/uk/author/grae-cleugh/ 81.147.111.139 (talk) 12:11, 12 December 2023 (UTC)[reply]
It is permenantly logged in the edit history, and at Laurence Olivier Award for Most Promising Playwright 81.147.111.139 (talk) 12:30, 12 December 2023 (UTC)[reply]

Borana page

They keep making a Photo of a non Borana girl on the page. Check the photo it have no source whatsoever. 2A00:A040:198:F2D3:3C5C:3EFD:252C:4C33 (talk) 13:08, 12 December 2023 (UTC)[reply]

Saxophone

I was going to add the C Melody saxophones, Mezzo-Soprano and Conn-o-sax to the table of saxophones along with their SPN ranges, but the page is semi-protected and I haven't edited 4+ articles. I see you decided not to include/removed the C Melodies, or maybe that was another editor/author, but has this page really seen so much vandalism that semi-protection is necessary until 2028?

Have a care, P. James Norris Pjamesnorris (talk) 23:18, 13 December 2023 (UTC)[reply]

Overlap on your user page

You probably already know this, but using Vector-2022 your horizontal collection of Userboxes overlaps the Tools menu, on my fairly wide screen. I don't know if that could be considered a bug of the new skin or a call to shorten the list of boxes.

Screenshot here. David Brooks (talk) 18:50, 14 December 2023 (UTC)[reply]

Fighting vandalism

December: story · music · places

Thank you for your quick eyes on symphonies redirected, and other vandalism! -- Gerda Arendt (talk) 09:00, 15 December 2023 (UTC)[reply]

Today, I have a special story to tell, of the works of a musician born 300 years ago. --Gerda Arendt (talk) 09:43, 22 December 2023 (UTC)[reply]

question about citation

Hi i made several edits to the Oddworld: abe's exoddus as i noticed several developers in the credits of the game weren't listed such as some artists, programmers, and a audio designer. I am unsure how i would cite that as its just in the game itself.

Please lock Bigg Boss 7 Telugu page

Hi Materialscientist, there are so many unknown users changing the context of Bigg Boss (Telugu season 7) page with unsourced data. Please lock the page for few hours until the grand finale Pawan Sparkle (talk) 07:22, 16 December 2023 (UTC)[reply]

Thank you!

Just wanted to thank you for your service, especially in reverting vandalism. Wikipedia owes you a great debt 😊 JohnLaurensAnthonyRamos333 (correct me if I'm wrong) 05:55, 17 December 2023 (UTC)[reply]

why did you reverted all of my edits most of them where good accept for the alien one the images they need to put them back move them to wikipedia Bearcoolreal94 (talk) 06:03, 17 December 2023 (UTC)[reply]
fair use page Bearcoolreal94 (talk) 06:03, 17 December 2023 (UTC)[reply]

Jack swing

hi there - thanks for your quick response. I actually tried to hyperlink Boy George, but re-entering, I got the "this has already been modified by another user" -message - which was obviously me, like 10 mins ago :) 181.176.117.154 (talk) 07:06, 17 December 2023 (UTC)[reply]

Widen block of 2A02:27AA:0:0:0:0:0:C89?

Hi! Just wanted to note that 2A02:27AA:0:0:0:0:0:C89, which you blocked as a proxy, is back as 2A02:27AA:0:0:0:0:0:1571. The entire /32 is a webhost, per WHOIS. — Mdaniels5757 (talk • contribs) 21:46, 17 December 2023 (UTC)[reply]

Indeed. Blocked, thanks. Materialscientist (talk) 02:40, 18 December 2023 (UTC)[reply]

bruh

bruh 74.205.133.138 (talk) 05:48, 18 December 2023 (UTC)[reply]

This old edit

Hi. I just reverted a link substitution you made in the Bangkok article back in 2018. It's several years late, but if you remember whether it was suggested by a tool, it might still be worth filing a bug report? --Paul_012 (talk) 06:05, 18 December 2023 (UTC)[reply]

Karen O's birthplace.

Reference #2 on the main wiki page of Karen O. "Phares, Heather. "Karen O". AllMusic. Retrieved October 28, 2015." When you click the link:(https://www.allmusic.com/artist/karen-o-mn0000186401#biography)

On the second paragraph "Born in Busan, South Korea, to a Korean mother and Polish father, Karen O spent most of her childhood in Englewood, New Jersey. While attending Ohio's Oberlin College, she met drummer Brian Chase."

The person who wrote the article, Karen O, wrote Seoul instead of Busan for some reason even though the article he/she referenced states that she was born in Busan. Not Seoul. 104.172.38.254 (talk) 08:12, 18 December 2023 (UTC)[reply]


Manly dam

Hello, I come from the manly dam page and am wondering about your deletion of the removal of the duck problem at manly dam. this was a true problem so why did you remove it.

(talk page stalker) Quite simply, and already explained to you - you need to quote a reliable source - see reliable source. David J Johnson (talk) 13:09, 19 December 2023 (UTC)[reply]

Front Desk

Hello. I noticed you reverted an edit on Front Desk. An IP had changed the part where it said "4-part series" to "5-part series". However, I am not sure why you reverted this. Front Desk is a five-part series. It consists of Front Desk, Three Keys, Room to Dream, Key Player, and Top Story. Did you revert that edit because the IP didn't provide a source? JohnLaurensAnthonyRamos333 (correct me if I'm wrong) 20:15, 19 December 2023 (UTC)[reply]

yes. Materialscientist (talk) 21:56, 20 December 2023 (UTC)[reply]
Okay, thanks for responding. JohnLaurensAnthonyRamos333 (correct me if I'm wrong) 21:58, 20 December 2023 (UTC)[reply]

A barnstar for you!

The Original Barnstar
You deserve it Abo Yemen 18:47, 20 December 2023 (UTC)[reply]

202.133.54.90 back at it with Indian film languages

Less than an hour after the 31-hour block you applied to 202.133.54.90, they are back at disruptive editing (adding/re-ordering Indian languages) in India actors' biographies. FWIW: The Proxy IP Checker thinks this is a Proxy/VPN node [12].  — Archer (t·c) 23:43, 20 December 2023 (UTC)[reply]

A barnstar for you!

The Original Barnstar
Awesome
WhizzyDude (talk) 04:48, 21 December 2023 (UTC)[reply]

Good article reassessment for Mercury (element)

Mercury (element) has been nominated for a good article reassessment. If you are interested in the discussion, please participate by adding your comments to the reassessment page. If concerns are not addressed during the review period, the good article status may be removed from the article. ~~ AirshipJungleman29 (talk) 20:17, 21 December 2023 (UTC)[reply]

IP vandalism again

Hello Materialscientist. The vandal IP from here is back again.

https://en.wikipedia.org/wiki/Special:Contributions/185.70.52.0/22 (similar to previously blocked IP)

https://en.wikipedia.org/wiki/Special:Contributions/85.117.48.0/20

The IPs always seem to start with 185.70, 85, and 91. Could you please block the range of each IP since this person keeps causing trouble with different addresses? KhndzorUtogh (talk) 00:26, 22 December 2023 (UTC)[reply]

Hello @Materialscientist i am here for asking help to you. a editor @Dotdotcomma who is blocked in Sock Puppet Case in https://en.wikipedia.org/wiki/en:Wikipedia:Sockpuppet_investigations/50mMidas is now actively live on Simple English Wikipedia and recreaing all promotional pages on Simple The Vach , Poybo Media, Justin Jin, Bayu Prihandito these are deleted in English Wikipedia but he recreates on Simple English Wikipedia and recently he creates another Sock account Anwi6644 and tried again to create these above articles on English Wikipedia . Both account Dotdotcomma and @Anwi6644 found guilty in same case of Sock puppetry En:Wikipedia:Sockpuppet investigations/50mMidas but still Dotdotcomma this user is unblocked. First Admin @Fr33kman blocked @Dotdotcomma and suddenly after some times he unblocked him this is really questionable. I want a proper Investigation aginst them now i doubt they are paid or not.Brandom Mc Thompson (talk) 09:03, 22 December 2023 (UTC)[reply]

We don't have tools to tell if a certain Wikimedia editor is paid for editing, only a wild guess based on editing pattern. Note that I don't have any administrative privileges on Simple English Wiki. Materialscientist (talk) 09:18, 22 December 2023 (UTC)[reply]
so sir who can help me better will you please suggest me >?Brandom Mc Thompson (talk) 09:28, 22 December 2023 (UTC)[reply]

ANI

Information icon There is currently a discussion at Wikipedia:Administrators' noticeboard/Incidents regarding an issue with which you may have been involved. The thread is 103.5.0.238. Thank you. Nobody (talk) 09:40, 22 December 2023 (UTC)[reply]

Potassium requested to be unprotected

Protection imposed in 2019; unprotection requested at Talk:Potassium#I_think_this_article_should_be_not_protected.. –LaundryPizza03 (d) 11:58, 22 December 2023 (UTC)[reply]

The Preserve at Sharp Mountain, Georgia

Good morning Materalscientist, I am not an admin, but I think that you are (or may know one). You have helped me in the past to get several articles to "Good" status. I am writing to ask for help in dealing with an editor who persistently inserts "bare URLs" into a page that I created more than a decade ago. I, as well as various other editors have tried clean up the persistent edits of an editor known as "MountainHiker" who has reverted attempts to conform to good Wikipedia formatting standards and now is posting private URLs on the article, The Preserve at Sharp Mountain, Georgia. In particular, "MountainHiker" continues to insert a private bare URL that is "members only" and not accessible to Wikipedia community. Further, "MountainHiker" persists in including a redundant "frontend website" bare URL that is already referenced correctly in the External links section. After I (and several others) have tried to correct these edits, I give up and am passing it up the line (through you) to block this editor or protect the article as you see appropriate. Thanks.  ⁃ Firewall 15:32, 22 December 2023 (UTC)[reply]

Please do explain this issue to MountainHiker on their talk, especially the inaccessibility of the links - this is important. As to formatting, usually experienced editors bear with it, because we have semi-automatic tools that improve bare urls, such as https://refill.toolforge.org/. Very often editors are much more understanding than we think, and quickly straighten up their attitude without admin intervention (which should be a last resort). Materialscientist (talk) 23:07, 22 December 2023 (UTC)[reply]
As you suggested, I left a note at User talk:MountainHiker explaining the various problems with recent edits by MountainHiker-- in particular the inclusion of a private bare URL that is "members only" and not accessible to Wikipedia community. I have not reverted MountainHiker's most recent edit, but instead encouraged MountainHiker to remove/fix the most recent edits without intervention by another editor. We'll see if MountainHiker takes the suggestions to heart. If after a week or so, there is not correction, I will revert MountainHiker's most recent edit as nothing will be lost in the article The Preserve at Sharp Mountain, Georgia since one of the bare URLs inserted by MountainHiker is already listed in the External links section and the other is a private URL which should not appear in the article.  ⁃ Firewall 21:22, 24 December 2023 (UTC)[reply]

2A02:842A:1BF:1901:0:0:0:0/64

Back in November, you warned them twice: [13].

This range has a ton of unsourced edits. I see a bunch that are in filmography tables for Indian actors I watch. Ali filmography is a recent one where they've repeatedly added content that is reverted for not having sourcing. Dec. 13, Dec. 18, Dec. 21, Dec. 22

I have issued warnings to a few of the IPs: [14] [15] [16], but since they are IPv6, they hop around within the /64, so I am uncertain they are seeing the warnings.

They are a prolific editor, and it appears that some of the edits are good (or, at least, not bad). However, there are enough bad or questionable edits that it takes a fair amount of time and effort to assess and clean-up.  — Archer (t·c) 19:39, 22 December 2023 (UTC)[reply]

This issue is a pain, because there are reference sites like IMDb, etc., where we can quickly check if the actor was part of a movie, and because there are thousands of such good-faith editors who add movies without bothering about references (some of them mention their source in the edit summary, which is not sufficient). How to deal with such edits is a matter of personal choice. If the editor is repeatedly warned for unsourced, and especially dubious additions, then admins can intervene. Materialscientist (talk) 23:13, 22 December 2023 (UTC)[reply]


Unblock request

Hello, Materialscientist. There's an unblock request at User talk:MrCrazyMan02, relating to a block which you imposed three years ago. I would like to unblock to give another chance, but do you have any opinion you would like to express? JBW (talk) 11:52, 23 December 2023 (UTC)[reply]