Wikidata:Administrators' noticeboard

Administrators' noticeboard

This is a noticeboard for matters requiring administrator attention.

• If you wish for something to be deleted, please use Wikidata:Requests for deletions.
• If you want to report a bug in Wikidata software, please use Wikidata:Report a technical problem or Phabricator.
• Matters not requiring administrator action should be raised at Project chat.
• Matters that may involve CheckUser should be raised at Wikidata:Requests for checkuser.
• To report vandalism on wikidata: please click here.
• Please add {{section resolved|1=~~~~}} to resolved sections.

IRC channel: #wikidata^connect

Translate this header box!

Start a new discussion

On this page, old discussions are archived. An overview of all archives can be found at this page's archive index. The current archive is located at 2024/12.

SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 1 day and sections whose oldest comment is older than 7 days.

Requests for deletions

high

_{~178 open requests for deletions.}

Requests for unblock

empty

_{0 open requests for unblock.}

User:Quesotiotyo

Scripted mass edits even after several complaints. See User_talk:Quesotiotyo#Adding_lifespan_to_WikiData_item_descriptions. The bot should be stopped until consensus is reached. --Rodomonte (talk) 09:03, 31 December 2021 (UTC)

Quesotiotyo ( talk  · contribs  · logs ) — Reasons: User keeps performing bot-like operations (adding year of birth and year of death) without approval and without consensus (see for example batch 72725). He has started new batches after having been asked by several users to stop this operation. See User talk:Quesotiotyo and Wikidata:Project_chat#Should_the_description_of_a_person_include_year_of_birth_and_death,_if_applicable? for previous discussions. Emu (talk) 09:51, 31 December 2021 (UTC)

Sorry for the duplication, I haven’t seen Rodomonte’s request. @The-Pope, Jmax, MisterSynergy, Hjart: FYI. --Emu (talk) 09:53, 31 December 2021 (UTC)

For the record, I consider this edit as falsifying a report. That’s not what I wrote. --Emu (talk) 10:24, 1 January 2022 (UTC)

I have commented in this case as well, so I cannot act in admin role.
That said, there is urgend need to revisit the running QS batch:

• May the reported user simply change the convention regarding English descriptions in spite of several complaints, or do we need to find formal consensus first? An RfC comes to mind here.
• Quesotiotyo reported on their user talk page that the batch will run "1-2 weeks" continuously. This is usually bot territory, so a bot approval process seems appropriate as well.

—MisterSynergy (talk) 10:55, 1 January 2022 (UTC)

@Quesotiotyo: I am going to block you. Please stop your batch edits and confirm you have done so here and I will unblock you. Please request approval at Wikidata:Requests for permissions/Bot before running this task again. Thank you. BrokenSegue (talk) 18:39, 1 January 2022 (UTC)

@BrokenSegue: The QuickStatements batch has been stopped. As I am not running a bot, could you please amend the wording of the block to reflect that? I would appreciate it.

--Quesotiotyo (talk) 19:22, 1 January 2022 (UTC)

@Quesotiotyo: Great thank you. You have been unblocked. BrokenSegue (talk) 22:52, 1 January 2022 (UTC)

@BrokenSegue: Can you please confirm that the use of QuickStatements to assist in performing human-generated edits does not qualify as operating a bot and that I am free to continue doing so without needing approval?

--Quesotiotyo (talk) 01:55, 4 January 2022 (UTC)

@Quesotiotyo: I will not confirm that. Bot actions are bot actions independent of how they are technically achieved. I can't just smuggle my bot's edits through QS and bypass our rules. Please seek approval for your bulk edits before restarting the process. BrokenSegue (talk) 02:05, 4 January 2022 (UTC)

@BrokenSegue: Many editors use Quickstatements. How is a Quickstatements user to know when their edits become bot actions? What standard is being applied here? Gamaliel (talk) 04:13, 4 January 2022 (UTC)

@BrokenSegue: Then why did you state here that "We require approval for bot actions but do not for bulk QuickStatement actions." and here that "you shouldn't need bot flag for QS though."? I am not trying to bypass any rules, just trying to understand why I was blocked indefinitely without warning for "Running unapproved bot" when I was simply using a tool which is described at Wikidata:Bot requests as being "available to all users which can be used to accomplish the work without the need for a bot", a tool which I have used to perform over 2.7 million edits [1] without any previous issues. If the actual problem was with the content that I was adding, please show me just one instance where something that I added was either incorrect or not within the guidelines at Help:Description and I will happily undo those batches.

I hope to get this issue settled soon so that I may continue contributing in an efficient and effective manner.

Thanks,

--Quesotiotyo (talk) 05:42, 4 January 2022 (UTC)

How on earth were you blocked “without warning”? I can’t remember a single recent case with warnings by that many users. The bottom line is that you used (and still want to use, if I understand your comments correctly) bot-like operations to force through a new standard for descriptions without any form of consensus and without any real need (quite to the contrary actually). That’s the problem, not some rules minutiae. Emu (talk) 14:29, 4 January 2022 (UTC)

@Quesotiotyo: Unfortunately the Wikidata guidelines here are unclear. Many/most QS jobs are totally fine and require no approval. It's a question of scale and probability of objection which comes down to judgement. The bot policy cannot be limited to some technical means (i.e. it makes no sense to allow bots to operate indiscriminately if they send their updates through QS). The job you were running was very big (editing basically every human item), required the use of automated software to build the QS and was apparently controversial. To me this means it should request bot approval. I don't think getting approval for this action is onerous. I agree policy should be better written (the text you quote conflates the need for a software "bot" with "bot approval") and would encourage anyone with time to open an RFC to clarify the situation. The fact that you previously made large bulk edits without approval does not mean this batch was ok. A change of this size/controversy deserves discussion. Personally I think we should restrict QS further (e.g. require edit comments / require references where applicable / lower maximum size). BrokenSegue (talk) 14:39, 4 January 2022 (UTC)

Also, please try not to interpret my blocking you as a rebuke. I only blocked you because I had no means (I think?) to stop the QS job and I felt more discussion should happen before it continued. BrokenSegue (talk) 14:45, 4 January 2022 (UTC)

Thank you for the responses. They are helping me to see how a misunderstanding about the intent and extent of the edits that I was performing led to the block. I only wish that I had been given a chance to provide more clarity before such an action was taken. I would like to do so now with regards to several things that you mentioned:

• I had no plan to edit basically every human item (which currently amounts to over 9.5 million); the end total was going to be around 670,000 people. This was in no way an attempt to "change the convention regarding English descriptions" or "force through a new standard for descriptions" (as others have conjectured above). On the contrary, I was following a convention that was already in use on almost half a million items.
• I did not use any automated software to generate these edits. I wrote queries by hand to run at both QLever and WDQS and then used a text editor and spreadsheet program to filter and sort the data before copying and pasting each batch into QuickStatements, each time manually inspecting a sample of the edits for correctness before submitting and again while they were being carried out. Thus my objection to the allegation that I was operating a bot (which Wikidata:Bots specifically says "make[s] edits without the necessity of human decision-making") and confusion at being directed to Wikidata:Requests for permissions/Bot.

I hope that things are clearer for you now as well. If you still feel that this topic warrants further discussion, I will refrain from making any more edits of this kind until everyone has had their say. There is plenty else for me to work on in the meantime.

--Quesotiotyo (talk) 22:38, 5 January 2022 (UTC)

I still don’t get it: What exactly is your thought process that you think it’s okay to change hundreds of thousands of descriptions because of your personal preferences – even though there is strong opposition to this plan? Your response seems to be that (1) not all descriptions conform to convention and therefore you can choose another convention that you like better and (2) you might not technically need bot approval. Emu (talk) 23:00, 5 January 2022 (UTC)

Report concerning User:

[[User:|]] ([[User talk:|talk]] • contribs • deleted contribs • logs • filter log • block user • block log • SUL (for IP: GUC)) — Reasons: RSAmusiclover (talk) 15:36, 3 January 2022 (UTC) --RSAmusiclover (talk) 15:36, 3 January 2022 (UTC)

@RSAmusiclover: Seems like something went wrong, I do not see a user name. --Ameisenigel (talk) 15:46, 3 January 2022 (UTC)

Yes, this is regarding User:Din-nani1. He/she has been making 1000s of edits adding identical profile descriptions with a bot in dagbanli language. When I Google translated these they were saying derivative things about USA, France, Ghana and South Africa. I’ve been undoing some of the damage but I don’t have the knowledge or the tools to do this properly. The vandalism to American profiles goes in the many many thousands. I’m not an admin but I think this profile should be blocked (maybe it was hacked?) RSAmusiclover (talk) 17:35, 3 January 2022 (UTC)

I believe this was intended to refer to Din-nani1 (talk • contribs • deleted contribs • logs • filter log • block user • block log • SUL (for IP: GUC)) who has been using Quick Statements to add the description "Ghana siyaasa nira ŋun nyɛ paɣa" (GT: Ghanaian politics is difficult) to many items. Bovlb (talk) 15:56, 3 January 2022 (UTC)

They appear to have had a number of similarly problematic batches over the last week. Previously, they appear to have been a normal productive editor. I have invited them to join this discussion. If they continue with batches without addressing this, they will need to be blocked. Bovlb (talk) 16:08, 3 January 2022 (UTC)

Sorry for joining the discussion very late and after been already blocked indefinitely. I think this is a serious misunderstanding and I would blame it on the Dagbani Language not been recognized on the google translate tool or any other tools used in translation. I am so disturbed on seeing that my translation of USA Wikidata items description is understood as "saying derivative things about USA", who am I to commit such things! I hope someone who understands the Dagbani language very well could be contacted on this issue so that I can be cleared of this misunderstanding. Again, "Ghana siyaasa nira ŋun nyɛ paɣa" has been translated wrongly by Google Translate to mean "Ghanaian politics is difficult". Frankly speaking it's so sad to see these kind of translations. "Ghana siyaasa nira ŋun nyɛ paɣa" means "Female Ghananian politician". Initially I thought I was blocked because QS batch is not allowed but for this issue I don't think I have done anything wrong. Please, I apologize for the misunderstanding created and pray that I be pardoned and unblocked to enable me continue to contribute to Wikidata. I would stop contributing using the QS batch tool until the issue of Dagbani Language translation is resolved.Din-nani1 (talk) 07:46, 5 January 2022 (UTC)

See also: [2], [3], [4]. Looking too suspiciously. --Wolverène (talk) 04:40, 4 January 2022 (UTC)

Batches have resumed, apparently without any attempt to discuss, so I have blocked Din-nani from mainspace. I would be happy to see them unblocked as soon as possible. Bovlb (talk) 20:21, 4 January 2022 (UTC)

I have stumbled on this discussion following RSAmusiclover's mass reversion of these Dagbani labels with the rather unhelpful label of "Spam". An edit description referencing this discussion would have been much more useful. I don't know Dagbani but I am concerned that the core premise of this problem is flawed. In the comments above, RSAmusiclover states that Google Translate has revealed these labels to be incorrect. However, as far as I can tell, Google Translate does not include an option for Dagbani. Using the "auto detect" function of Google Translate causes it to pick a random language and try to offer a translation into English; the label I tried it with thought the original language was Japanese. This results in a nonsensical English translation that may not reflect the original meaning in Dagbani. I would suggest freezing both the insertions and reversions here and trying to find someone who can verify whether the labels are genuinely Dagbani and that they are correct. From Hill To Shore (talk) 23:09, 4 January 2022 (UTC)

For reference, we currently have Achiri Bitamsimli (talk • contribs • logs) working through quickstatements with a batch edit of adding large numbers of Dagbani labels. At the same time we have RSAmusiclover (talk • contribs • logs) working through EditGroups on a mass reversion of Achiri Bitamsimli's Dagbani labels. Both editors are making thousands of edits undoing each other's work and neither appear to be talking to each other. Can an administrator please implement a temporary block on both users to stop this disruptive behaviour until we clarify the situation and gain consensus? From Hill To Shore (talk) 23:30, 4 January 2022 (UTC)

The other two editors are also now blocked from mainspace. They can be unblocked as soon as they undertake to stop the QS batches pending the results of this discussion. Bovlb (talk) 23:59, 4 January 2022 (UTC)

Like From Hill To Shore, I'm also working in the dark here with respect to the content issue here. Regardless of who is right, we need to resolve this in a way that does not involved massive edit warring via QuickStatements. (And bulk batch editors need to be very responsive to concerns raised, not just keep running batches.) Bovlb (talk) 00:09, 5 January 2022 (UTC)

Hi there, just to clarify, I noticed these users adding identical description labels to profiles on a massive scale. I’ve been trying to undo this vandalism and as it seems I’m now getting blocked as a result myself. So, I’m more than happy to stop doing this and leave this to the administrators to sort out. I was simply trying to help and I’d appreciate it if you could unblock my profile. Regards 102.65.160.39 04:47, 5 January 2022 (UTC)

Sorry, this was my reply, I forgot to log in. RSAmusiclover (talk) 04:49, 5 January 2022 (UTC)

I've unblocked RSAmusiclover and Din-nani1 per requests. Let's see some discussion take place before anyone does any more batches. Bovlb (talk) 05:44, 5 January 2022 (UTC)

Thanks unblocking me. I am grateful.Din-nani1 (talk) 08:13, 5 January 2022 (UTC)

You shouldn't have done that without my knowledge sir. You don't understand something doesn't mean that it is wrong. Beside, is it wrong to have identical descriptions for items on wikidata? A description does not need to be unique; multiple items can have the same description, only labels can not be the same. Achiri Bitamsimli (talk) 22:26, 5 January 2022 (UTC)

With the above reply I pray that you unblock me to continue contributing to Wikidata. I would stop using the QS tool until Dagbani langauge is fully accepted by the Google translate tool or other translation tools that may be developed. Thank you.Din-nani1 (talk) 08:04, 5 January 2022 (UTC)

@Din-nani1: I’m sorry I had to block you, but another user had raised concerns about your batch edits and had reverted some of them, and you were continuing to run new batches without making any response to those concerns. I’m afraid that bulk editors have to be highly responsive to concerns raised and not proceed in the face of strong opposition without engaging in discussion. I felt obliged to step in and give you a partial block to prevent more batches from adding to the problem.

Regarding the concerns, I have no knowledge of Dagbani, and am unable to judge the actual merits of the content here. (It is not a project requirement that editors only work in languages well-supported by Google Translate.) Perhaps it would help the discussion here if you could explain how you’re generating these batches and how you would translate some of the descriptions (e.g. Ghana siyaasa nira ŋun nyɛ paɣa). Hopefully we can get this resolved quickly and get everything back to normal. Bovlb (talk) 17:22, 5 January 2022 (UTC)

Din-nani1’s response appears to be in the wrong place, but having read their explanation I think it’s fair to say that this was entirely in good faith, and I would support them being able to restore their previous batch edits. Furthermore, I’d say that users should be very careful when trying to use Google Translate to verify meaning in a language they have no knowledge of, for exactly the reasons demonstrated in this thread (even if Google does support the language in the first place). That goes doubly-so for somewhere with structured data like Wikidata, where subtle differences in phrasing can be highly meaningful. Theknightwho (talk) 18:25, 5 January 2022 (UTC)

Din-nani1's explanation seems perfectly reasonable, and probably applies to Achiri Bitamsimli as well. @RSAmusiclover: Do you have anything else to say here, or are we clear to let @Din-nani1 and @Achiri Bitamsimli continue? Bovlb (talk) 19:55, 5 January 2022 (UTC)

To add a little context to the discussion; since my previous comment I have been hunting around online for Dagbani to English dictionaries to try to verify some of the labels that have been inserted. While not every Dagbani word has a translation available in the online dictionaries, every word I have been able to confirm aligns with the relevant item. For example, paɣa means "female" and has been used by Din-nani1 in the labels of items for human (Q5) female (Q6581072). Likewise, Achiri Bitamsimli has been using Dagbani words related to schools (shikuru = school) on items with occupation (P106) university teacher (Q1622272). I don't think there is any case to answer here and both users should be allowed to resume inserting the Dagbani labels. This may appear as "spam" solely from the perspective of Dagbani labels starting from a low level of implementation; labels will need to be inserted on millions of items. At a practical level, an automated sweep of generic labels based on one or more occupation (P106) stated in the items makes the most sense. Once the generic labels have been inserted, Dagbani language users may update the generic labels with more specific details for each item in future months or years. From Hill To Shore (talk) 22:39, 5 January 2022 (UTC)

Thanks From Hill To Shore, that's very helpful. It sounds like we're about done here, but I'd like to give RSAmusiclover just a little more time to respond, to make sure we don't have any future problems. Bovlb (talk) 00:59, 6 January 2022 (UTC)

It doesn't look like RSAmusiclover has time for us right now.

@Achiri Bitamsimli, Din-nani1: You are clear to proceed. Again, please accept my apologies for the interruption. When you're doing batches, please try to keep an eye out for feedback.

@RSAmusiclover: I appreciate your good intentions here, but if you have future concerns, please try harder to communicate before embarking on a QS edit war. Thanks, Bovlb (talk) 17:25, 6 January 2022 (UTC)

@Bovlb @Ameisenigel @From Hill To Shore: Sorry for my late response. I'm surprised to read that you are planning to allow Din-nani1 to continue. He is adding the same description to labels of thousands of profiles. It does not make any sense to me. Whenever I google-translate any of his statements the translations sound political and seem like verbal 'warfare'. For example: this user @Din-nani1 just added another batch (batch #73247) via quickstatements today to thousands of Chinese profiles with the description "China siyaasa nira ŋun nyɛ doo". This translates to "China's politics are weak" in Somali(!!). Now some here are implying this is just a coincidence and that they are meaning well and that the translation is wrong... So let's look at another recent one by Din-nani from 29.12.21, he added batch #temporary_batch_1640776782516 to thousands and thousands of profiles, with this profile label description: "USA alikaali nira" which translates to "The USA remained a yoke" in Chichewa language. Another massive batch via quick statements by the same user on 8.1.22 (batch #73246): "India siyaasa nira ŋun nyɛ paɣa". None of these words seem to even be part of the dagbani language according to an online dictionary.. It seems like sometimes the batches even though added under dagbani are in other languages. For example, this batch (batch #73194) addition by the same user from 8.1.22 states "France siyaasa nira ŋun nyɛ doo" apparently also means "France's politics are weak"...

To me this equates to some sort of negative propaganda mission or at least vandalism on wikidata and I really think this should not be tolerated and should be banned permanently asap... @Din-nani1 has been doing this for weeks.. These actions, jokes or politically motivated statements are not acceptable in my opinion. i leave it up to you... i think this stopped immediately! Kind regards User:RSAmusiclover RSAmusiclover (talk) 19:32, 9 January 2022 (UTC)

P.s. I really have zero interest in a QS war whatsoever. I simply noticed vandalism and I don't have the tools as a user to stop this. Talking about it with users who are clearly vandalising wikidata seemed rather silly, so I reported it here and started to try and erase their actions. I'll leave that up to the administrators in future because, as i said, i don't have the tools (or the time) to do this effectively. Just keep watching the amount of statements this user User:Din-nani1 is adding by the hour... RSAmusiclover (talk) 19:36, 9 January 2022 (UTC)

p.p.s. I first came across this user doing batch #72763 which added "South Africa kpiɛrikpiɛrita ŋun nyɛ doo" to 1500 South African profiles, translating to "South Africa is no exception" in IGBO language and added under dagbani like all the other batches... RSAmusiclover (talk) 19:47, 9 January 2022 (UTC)

Report concerning user 64.124.47.51

• 64.124.47.51 (talk • contribs • deleted contribs • logs • filter log • block user • block log • SUL (for IP: GUC))
• Reasons: vandalism in Mohamed Abdullahi Mohamed (Q558575) Stang 18:26, 6 January 2022 (UTC)

 Done IP blocked for 3 months and item semi-protected for 24h. I wonder if this is a return of Mwasoge (talk • contribs • deleted contribs • logs • filter log • block user • block log • SUL (for IP: GUC)). Bovlb (talk) 18:40, 6 January 2022 (UTC)

• Mohamed Abdullahi Mohamed (Q558575) is now being vandalised from 209.133.102.164, so I suspect that at least we'll need a longer semi-protection period on that one again. --Oravrattas (talk) 11:41, 8 January 2022 (UTC)

 Done IP blocked for a day, semi-protection for two weeks. --Ameisenigel (talk) 12:40, 8 January 2022 (UTC)

I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Ameisenigel (talk) 12:40, 8 January 2022 (UTC)

Please block User:Worldm99

The account bulk adds P172 statements to Wikidata despite being requested to provide references. --- Jura 20:42, 6 January 2022 (UTC)

Blocked until they confirm that the batch is stopped; further discussion regarding the issue on their user talk page, please. —MisterSynergy (talk) 22:21, 6 January 2022 (UTC)

Report concerning user 68.100.184.226

68.100.184.226 (talk • contribs • deleted contribs • logs • filter log • block user • block log • SUL (for IP: GUC))

IP sock of Slowking4 (who was indef-blocked over two years ago for socking), as determined by similar behaviors like mass creating items of academic award recipients through a similar method with no gender statement and (oftentimes) Property:P973 statements without the required Property:P407 qualifier (Slowking4: [5]; IP: [6] [7]), and mass creation of Florence Nightingale Medal recipient items, a topic they had listed for creation on a thread on the sockmaster account's talk page. ミラP@Miraclepine 02:21, 7 January 2022 (UTC)

Banning IP address

Hi, Kindly I want to apply for banning this IP 185.166.25.1, as it has vandalism edits in below: https://www.wikidata.org/wiki/Special:Contributions/185.166.25.1 Ravan (talk) 11:52, 7 January 2022 (UTC)

Declined for the block, as the last edit was some time ago, but I  semiprotected the item for two weeks as it was edited disruptively from multiple IPs (and an account). Martin Urbanec (talk) 16:47, 7 January 2022 (UTC)

I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Ameisenigel (talk) 12:42, 8 January 2022 (UTC)

Report concerning User:77.13.233.80

77.13.233.80 (talk • contribs • deleted contribs • logs • filter log • block user • block log • SUL (for IP: GUC)) — Reasons: This IP user made a personal attack on another user by saying they should not be trusted and comparing them to the seller of a Ponzi scheme.[8] On being asked to read Wikidata:Assume good faith and remove the comparison,[9] the IP user declined to read the policy and pretended that they have not said anything bad about another user.[10] From Hill To Shore (talk) 20:55, 7 January 2022 (UTC)

This is a well-known globally blocked user. They have access to several large IP ranges, so blocks will not be very effective. I suggest to simply ignore their comments, or to leave a comment that meta:Requests for comment/Global ban for Tobias Conradi applies for the IP user. —MisterSynergy (talk) 21:19, 7 January 2022 (UTC)

"This IP user made a personal attack on another user by saying they should not be trusted" - that is a false claim by User:From Hill To Shore 77.13.233.80 21:24, 7 January 2022 (UTC)

"and comparing them to the seller of a Ponzi scheme." - that is a false claim by User:From Hill To Shore 77.13.233.80 21:24, 7 January 2022 (UTC)

"the IP user declined to read the policy" - that is a false claim by User:From Hill To Shore 77.13.233.80 21:20, 7 January 2022 (UTC)

"pretended that they have not said anything bad about another user" - that is a false claim by User:From Hill To Shore 77.13.233.80 21:20, 7 January 2022 (UTC)

Four false claims. Should User:From Hill To Shore maybe read

• https://en.wikipedia.org/wiki/Wikipedia:Citing_sources
• https://en.wikipedia.org/wiki/Help:Referencing_for_beginners

77.13.233.80 21:24, 7 January 2022 (UTC)

 Done, blocked for a week by Mahir256--Ymblanter (talk) 22:14, 7 January 2022 (UTC)

I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Ameisenigel (talk) 12:43, 8 January 2022 (UTC)

Report concerning User:2600:387:8:7::/64

2600:387:8:7::/64 (talk • contribs • deleted contribs • logs • filter log • block user • block log • SUL (for IP: GUC)) — Reasons: Vandalism, block evasion of 2600:1700:3720:3770::/64. – LiberatorG (talk) 23:27, 7 January 2022 (UTC)

 Done --Ameisenigel (talk) 07:36, 8 January 2022 (UTC)

I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Ameisenigel (talk) 07:36, 8 January 2022 (UTC)

Protected item

Could someone please mention Jean-Baptiste de Lamarck (Q82122)'s, Auguste de Lamarck (Q110470983)? Unfortunately I can't do it by myself, since the item is protected. Thanks in advance, 92.184.98.172 08:50, 8 January 2022 (UTC)

Report concerning User:VirguloMane

VirguloMane (talk • contribs • deleted contribs • logs • filter log • block user • block log • SUL (for IP: GUC)) — Reasons: nonsensical edits on various items since last week ; most are breaking previously correct external identifiers Jahl de Vautban (talk) 13:33, 8 January 2022 (UTC)

 Info This issue was discussed on User talk:VirguloMane. --Ameisenigel (talk) 10:19, 9 January 2022 (UTC)

Semi protection for Q108109345

Amugiri (Q108109345) - Vandalism persistently continued after the last semi protection expired. [11] It is a living people item. whym (talk) 01:32, 9 January 2022 (UTC)

 Done BrokenSegue (talk) 02:43, 9 January 2022 (UTC)

I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Ameisenigel (talk) 19:37, 9 January 2022 (UTC)

Report concerning User:2601:584:c500:450::/64

2601:584:c500:450::/64 (talk • contribs • deleted contribs • logs • filter log • block user • block log • SUL (for IP: GUC)) — Reasons: Vandalism since 20 December 2021. SCP-2000 (talk) 09:42, 9 January 2022 (UTC)

 Done --Ameisenigel (talk) 10:13, 9 January 2022 (UTC)

I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Ameisenigel (talk) 10:13, 9 January 2022 (UTC)

Report concerning User:110.137.192.47

110.137.192.47 (talk • contribs • deleted contribs • logs • filter log • block user • block log • SUL (for IP: GUC)) — Reasons: Repeated vandalism. – LiberatorG (talk) 13:57, 9 January 2022 (UTC)

 Done --Ameisenigel (talk) 14:17, 9 January 2022 (UTC)

I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Ameisenigel (talk) 14:17, 9 January 2022 (UTC)