Wikidata

Wikidata:Administrators' noticeboard/Archive/2019/01

< Wikidata:Administrators' noticeboard‎ | Archive‎ | 2019

Old Canadian vandal is back

Hi. An anonymous and interwiki vandal located in Canada who has been reported many times here is now back with the IP 184.147.29.17 (talk • contribs • logs). I'm not sure what to do about the other projects. Is there a steward in the house? (Ping @NicoScribe:). Montgomery (talk) 20:31, 2 January 2019 (UTC)

The account is globally blocked. Bencemac (talk) 16:20, 3 January 2019 (UTC)
This section was archived on a request by: Bencemac (talk) 16:20, 3 January 2019 (UTC)

Ludovico Einaudi

Some anon egregiously vandalized Q83182. [1] I have reverted the change but I am not sure how vandalism is dealt with on wikidata beyond that. Hrodvarsson (talk) 04:47, 3 January 2019 (UTC)

@Hrodvarsson: I am watching the item. Bencemac (talk) 16:18, 3 January 2019 (UTC)
This section was archived on a request by: Bencemac (talk) 16:18, 3 January 2019 (UTC)

Вандализм

@Ymblanter: кандидат на блокировку? Kalendar (talk) 19:27, 3 January 2019 (UTC)

  Done, 31h--Ymblanter (talk) 19:30, 3 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 19:45, 3 January 2019 (UTC)

Protection request for Q22080762

Requesting protection for Chaturbate (Q22080762), as it attracts vandalism and edits to official website (P856) adding affiliate links. Trivialist (talk) 02:51, 1 January 2019 (UTC)

  Done 1 week —MisterSynergy (talk) 08:22, 1 January 2019 (UTC)

Nonsense pages by Special:Contributions/187.145.48.108

IP is creating nonsense pages. Esteban16 (talk) 04:17, 2 January 2019 (UTC)

  Done Deleted and blocked the /24 subnet for a week. Mahir256 (talk) 04:27, 2 January 2019 (UTC)

Merge

Please merge Armand Bory (Q60332350) with Armand Bory (Q16025422). This is a duplicate. 2A01:CB1D:80FC:DA00:8873:2DDF:5EE5:CF39 14:05, 2 January 2019 (UTC)

There's also a duplicate there: Édouard Flouest (Q55772930) and Édouard Flouest (Q57246278). 2A01:CB1D:80FC:DA00:8873:2DDF:5EE5:CF39 14:37, 2 January 2019 (UTC)
  Merged --Lymantria (talk) 15:58, 2 January 2019 (UTC)

Vandalism by User K.K.'s FBI-ALT

New user account. Of 13 edits, 12 were obvious vandalism (meanwhile reverted). Special:Contributions/K.K.'s_FBI-ALT
1. Issue warning to user ?
2. (Temporarily ?) Block account ?
--Archie02 (talk) 17:08, 2 January 2019 (UTC)

I warned them. --Pasleim (talk) 17:57, 2 January 2019 (UTC)

user lock

Hello, I hope you are well. I request your help to block the user Rcrc37 since he has been doing bandalico on the page Arturo Nunez Jimenez (Q5707383) can check the history so that they see what he has been placing. Thank you. regards

  Done Andreasm háblame / just talk to me 03:52, 3 January 2019 (UTC)

Вандализм

@Ymblanter: кандидат на блокировку Kalendar (talk) 09:34, 9 January 2019 (UTC)

I went ahead and warned the user here. I'll watch them.
Я послал человеку предупреждение diff. Я буду смотреть их
·addshore· talk to me! 09:41, 9 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 19:44, 9 January 2019 (UTC)

Badge for Brownsville, Texas (Wikivoyage)

I tried to add a badge next to the Wikivoyage section that appears on the Wikipedia sidebar for Brownsville, Texas. When I tried to change the badge, it told me local Wikipedias require consensus. Can this be updated? The Wikivoyage article meets this requirement (currently a guide article). De88 (talk) 08:59, 4 January 2019 (UTC)

  Done --Pasleim (talk) 09:26, 4 January 2019 (UTC)

Request for protection of Q60032851 and Q28229322

Someone from IP is trying over and over to switch pl.wiki sitelinks between these two items. Maybe the lowest protection for about a month? Wostr (talk) 19:51, 4 January 2019 (UTC)

  Done —MisterSynergy (talk) 20:31, 4 January 2019 (UTC)

Вандализм

@Ymblanter: кандидат на блокировку. Kalendar (talk) 19:29, 10 January 2019 (UTC)

  Done--Ymblanter (talk) 19:31, 10 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 19:37, 10 January 2019 (UTC)

Вандализм

@Ymblanter: абсолютный кандидат на блокировку. Kalendar (talk) 19:33, 10 January 2019 (UTC)

This section was archived on a request by: -- Kalendar (talk) 19:37, 10 January 2019 (UTC)

Unblocking Pi bot

Please see User_talk:Mike_Peel#Item_creation_based_on_Wikimedia_Commons_categories? about Pi bot (talk • contribs • logs). @Multichill: seems to have gone offline, perhaps someone else could have a look and unblock the bot please? Thanks. Mike Peel (talk) 17:02, 5 January 2019 (UTC)

  Done —MisterSynergy (talk) 17:19, 5 January 2019 (UTC)
Thanks. Discussion about this is now at Wikidata:Project_chat#Creating_new_items_for_humans_based_on_Commons_categories. Thanks. Mike Peel (talk) 11:11, 6 January 2019 (UTC)

Pepita Jiménez

The item Bride to Be (Q7166313) may was about Pepita Jiménez, a novel written and published by Juan Valera in 1874, and should be recovered and then merged into Pepita Jiménez (Q5562244). Queryzo (talk) 07:35, 6 January 2019 (UTC)

Q7166313 is about a 1975 film, see [2]. Should it still be recovered? (It had lots of identifiers, in fact) —MisterSynergy (talk) 08:13, 6 January 2019 (UTC)
...these identifiers being Swedish Film Database film ID (P2334) "51912", AllMovie title ID (P1562) "v156578", FilmAffinity film ID (P480) "469076", elFilm film ID (P3143) "71101", ČSFD film ID (P2529) "122502", OFDb film ID (P3138) "132463", and Kinopoisk film ID (P2603) "98142". Mahir256 (talk) 09:24, 6 January 2019 (UTC)
Oh, perfect, then it should be merged with Bride to Be (Q48672383). Queryzo (talk) 10:09, 6 January 2019 (UTC)
  Done —MisterSynergy (talk) 10:16, 6 January 2019 (UTC)

Semi-protection

Could an administrator semi-protect Javier Hernández (Q165125) for about a year? Almost all of the edits since September consist of the addition or removal of vandalism. Thanks, Jc86035 (talk) 13:14, 7 January 2019 (UTC)

  Done by MisterSynergy. Mahir256 (talk) 15:25, 7 January 2019 (UTC)

Вандализм

@Ymblanter: Neckulin Kalendar (talk) 19:06, 12 January 2019 (UTC)

  Done, 31h--Ymblanter (talk) 19:10, 12 January 2019 (UTC)
@Ymblanter: за эти же вандальные правки в Русской Википедии вандал заблокирован бессрочно. Весь его глобальный вклад откачен. Kalendar (talk) 20:01, 13 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 20:01, 13 January 2019 (UTC)

Advertising

Please indefinitely block User:Drums_Akthas for unambiguous self-promotion, if that's a thing that's usually done for spammers. Thanks, Jc86035 (talk) 13:01, 7 January 2019 (UTC)

This probably doesn't warrant an indef-block yet; if this user ends up changing or creating a lot more items, or if there is cross-wiki spam involved with this user, then an indef-block will most likely be necessary. Mahir256 (talk) 15:25, 7 January 2019 (UTC)
@Mahir256: Well, the user did have all of their edits (i.e. w:en:Drums Akthas and 2×w:en:User:Drums Akthas) deleted on enwiki in March and in November last year (non-notable/spam) and all of their uploads deleted on Commons in November (out of scope). Jc86035 (talk) 08:47, 8 January 2019 (UTC)
Where was User:Drums Akthas notified of this discussion? Their talk page is still a red link. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:11, 8 January 2019 (UTC)

Q6988775

Neil J. Walsh (Q6988775) can someone restore the entry please, just because deleted from English Wikipedia, does not mean he needs to be deleted from Wikidata. see: https://webcache.googleusercontent.com/search?q=cache:mhZJPBOSoqUJ:https://en.wikipedia.org/wiki/Neil_J._Walsh+&cd=4&hl=en&ct=clnk&gl=us --RAN (talk) 22:40, 7 January 2019 (UTC)

@Richard Arthur Norton (1958- ): Done, but please appreciably expand this item or it may be deleted again. Mahir256 (talk) 05:55, 8 January 2019 (UTC)


San Salvador (Q3110)

Protection needed: Please someone semi-protect it. Kind regards, — TBhagat (contribs | talk) 15:59, 8 January 2019 (UTC)

  Done 1 month semi. Lymantria (talk) 18:11, 8 January 2019 (UTC)

Jeu Wikipedia

Bonjour, J'aimerai élaborer un jeu en collaboration avec Wikipedia, le principe du jeu serait de naviguer entre les pages de wikipedia jusqu'à un mot. Merci pour votre réponse,

Cordialement,

Franck Morata.

Bonjour Franck, je crois que vous n'êtes pas à la bonne place pour discuter de cela. Peut-être devriez-vous poster votre message sur le bistro. Pamputt (talk) 18:54, 9 January 2019 (UTC)

Vandalism 87.41.92.168

Mass removal of wikilinks by 87.41.92.168 (belongs to schools.edu.ie as per RIPE) for mostly kids shows. InMontreal (talk) 14:11, 9 January 2019 (UTC)

Blocked for a few days. -- Ajraddatz (talk) 17:50, 9 January 2019 (UTC)

Вандализм

@Ymblanter: Markeloffnoname Вандал в РуВики (заблокирован бессрочно) и Викиданных Kalendar (talk) 05:22, 15 January 2019 (UTC)

  Done--Ymblanter (talk) 06:32, 15 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 19:47, 15 January 2019 (UTC)

Blood_pressure

I fail to add french language connection (https://fr.wikipedia.org/wiki/Pression_artérielle) to English page https://en.wikipedia.org/wiki/Blood_pressure and vice versa.

Why?

Kindly help  – The preceding unsigned comment was added by Eric herbelin (talk • contribs).

The two article are about slightly different topics. The French article is about the arterial blood pressure while the English article is more general about arterial, venous and pulmonary pressure. Thus the sitelinks are located on different items. --Pasleim (talk) 13:54, 10 January 2019 (UTC)

Cross-wiki vandal IP 184.147.29.17

184.147.29.17 Massive vandalism currently here in WD, but the IP also vandalises lots of wikipedias. Grüße vom Sänger ♫ (talk) 01:07, 11 January 2019 (UTC)

Blocked for 3 days. Pamputt (talk) 06:29, 11 January 2019 (UTC)
3 days seem to be quite short for someone like this. Grüße vom Sänger ♫ (talk) 11:33, 11 January 2019 (UTC)
The point is I think this IP is dynamic (this is what I understand from the Meta discussion). If so, blocking longer is useless and may block a non-vandal IP. If the discussion on Meta leads to a global block, we do not need to block longer Pamputt (talk) 12:26, 11 January 2019 (UTC)

Vandalism in Q12383130

Q12383130 has been subject of attacks in gl.wiki and commons, i've reverted twice in Q12383130 due to this. Banjo (talk) 12:13, 11 January 2019 (UTC)

Reverted once more. Vandal user is 193.144.97.85 Banjo (talk) 12:14, 11 January 2019 (UTC)

  Done Protected for two weeks Andreasm háblame / just talk to me 21:35, 11 January 2019 (UTC)

Block request

Hi, could someone stop 190.110.211.138 who's vandalising several articles ? Many thanks --Do not follow (talk) 17:41, 11 January 2019 (UTC)

  Done, though probably too late.--Ymblanter (talk) 21:58, 11 January 2019 (UTC)

Semi-protection…

… For Q58833335 (because vandalism). Greetings, --Vercelas (quaestiones?) 21:13, 11 January 2019 (UTC)

  Done —MisterSynergy (talk) 21:36, 11 January 2019 (UTC)

Reporting abuse and offensive word

I am trying to remove an offensive word from the San Leucio del Sannio (Q55959). Revision history of "San Leucio del Sannio" (Q55959) reports that on 19 December 2018‎ someone modified "comune italiano" in "comune di merda" that is offensive for the people living there. The description does not appear in the page when it is visited from a PC, however ti appears by mobile. I modified the description, unfortunately the mobile page appears unchanged. Maybe, there is some tag setting I am unable to find and correct.  – The preceding unsigned comment was added by 93.40.225.183 (talk • contribs) at 08:37, 12 January 2019‎ (UTC).

The modification of the description is sufficient, the rest is a caching issue. I have checked this article in the (Android) app and on the mobile page, and I cannot see the vandalism any longer. —MisterSynergy (talk) 09:18, 12 January 2019 (UTC)

Block request

Hi, could you please stop 2001:BB6:8D59:D558:F55B:6508:531B:F376 who is deleting correct content. Many thanks --Do not follow (talk) 19:21, 12 January 2019 (UTC)

  Done Thanks! Andreasm háblame / just talk to me 19:24, 12 January 2019 (UTC)

Block request

Hi, could someone please stop 2601:18D:4700:949F:1832:3C3E:EBCB:A465 who is deleting and editing correct content. Regards - Premeditated (talk) 22:33, 12 January 2019 (UTC)

  Done Thanks, Andreasm háblame / just talk to me 00:42, 13 January 2019 (UTC)

Вандализм

@Ymblanter: Категория Эн. "Такой хоккей нам не нужен". Kalendar (talk) 04:51, 18 January 2019 (UTC)

  Done--Ymblanter (talk) 06:55, 18 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 09:18, 18 January 2019 (UTC)

Q47453522

Please, remove (hide) the edit and undo it. This is not a website, but an insult to one of the Wikipedia editors. --Ksc~ruwiki (talk) 15:53, 8 January 2019 (UTC)

  Done by Putnik —MisterSynergy (talk) 06:17, 13 January 2019 (UTC)

Block request

Hi, 64.114.197.89 has been vandalising since December the 3rd. He might use some rest, now. Many thanks in advance --Do not follow (talk) 21:22, 8 January 2019 (UTC)

  Done by Lymantria —MisterSynergy (talk) 06:17, 13 January 2019 (UTC)

Q58853694

Self-promotion item created by long-term abuser Alex9777777 (also known as Pechkurov Aleksej). --jdx Re: 19:12, 11 January 2019 (UTC)

We can not do anything until the Belarusian sitelink gets deleted.--Ymblanter (talk) 21:56, 11 January 2019 (UTC)
It has been already deleted. Also please note associated item Q60541526. --jdx Re: 22:56, 12 January 2019 (UTC)
  Done —MisterSynergy (talk) 06:21, 13 January 2019 (UTC)

User constantly adding wrong "instance of"

Hi, some months ago i noticed this kind of edition in which the user Prcondo added wrong "instances of" properties to humans (for example, adding the occupation there). I left a notice in the user page telling him that this kind of edition is wrong and if he could correct previous editions. He ingnored my msg and continued editing without correcting several entities with these problems. After a month i left him another msg to ask him again if he could please correct these problems and i was ignored again. Moreover even when he knows this editions are wrong, he continued doing them for example here, here, here, here and dozens of other entities. I call your attention in this issue and i hope you can persuade him to stop somehow.--Zeroth (talk) 14:53, 4 January 2019 (UTC)

Reminds me of Ovagner (talk • contribs • logs), which I was also not able to communicate with. Sjoerd de Bruin (talk) 19:32, 4 January 2019 (UTC)
Pinging the admins again. The user Prcondo sent me a mail stating that adding "instance of=athlete" to a person si not wrong. So, please can anyone look into this?.--Zeroth (talk) 00:52, 15 January 2019 (UTC)

I left a final warning on his talk page. Let's hope for the best. Anyway, I'll keep an eye on his edits. Andreasm háblame / just talk to me 01:11, 15 January 2019 (UTC)

Protection request for Q28377590

Long history of changes of pl.description. TERYT Registry (National Register of Territorial Land Apportionment Journal of the Central Statistical Office) has this as "Brzezówka (0652174) przysiółek" (hamlet (Q4379239) = part of a village) not as a "wieś" (village of Poland (Q3558970)). Request for lowest protection for about a month. Wostr (talk) 14:57, 13 January 2019 (UTC)

  Done semiprotected for a month. Lymantria (talk) 15:55, 14 January 2019 (UTC)

Вандализм

@Ymblanter: Serg777 tr. Подобные хоккеисты забивают только в свои ворота. Kalendar (talk) 05:04, 18 January 2019 (UTC)

  Done--Ymblanter (talk) 06:55, 18 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 19:06, 20 January 2019 (UTC)

Вандализм

@Ymblanter: Roman Larionovskii. Kalendar (talk) 19:09, 20 January 2019 (UTC)

  Done--Ymblanter (talk) 19:12, 20 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 20:10, 20 January 2019 (UTC)

Вандализм

@Ymblanter: 2A00:1FA0:C26E:7981:0:2B:A584:E601. Kalendar (talk) 19:12, 20 January 2019 (UTC)

  Done, 1 week--Ymblanter (talk) 19:13, 20 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 20:10, 20 January 2019 (UTC)

Вандализм

@Ymblanter: 178.35.89.68. Kalendar (talk) 20:07, 20 January 2019 (UTC)

  Done, 1 week--Ymblanter (talk) 20:10, 20 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 20:10, 20 January 2019 (UTC)

Вандализм

@Ymblanter: 46.211.150.178. Kalendar (talk) 20:08, 20 January 2019 (UTC)

  Done, 31h--Ymblanter (talk) 20:11, 20 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 20:13, 20 January 2019 (UTC)

Protection request for Q4423260

Please semi-protect Fuji Taiseki-ji Kenshōkai (Q4423260). Several IPs change the description in Japanese to "日本のカルト教団、過激組織" (Japanese cult faction, extremist). --Afaz (talk) 07:18, 15 January 2019 (UTC)

  Done —MisterSynergy (talk) 07:28, 15 January 2019 (UTC)

Вандализм

@Ymblanter: Гросс Нилсен. Вандалит также в РуВики (запрос подан). Kalendar (talk) 10:37, 21 January 2019 (UTC)

  Done--Ymblanter (talk) 10:40, 21 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 10:47, 21 January 2019 (UTC)

Вандализм

@Ymblanter: 46.149.50.243 Kalendar (talk) 10:39, 21 January 2019 (UTC)

  Done, 31h--Ymblanter (talk) 10:41, 21 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 10:47, 21 January 2019 (UTC)

Protection request for Q184935

Hi, Can you Semi-protect Q184935 for vandalism, we have 20 ip modification in 3 day. — eru [Talk] [french wiki] 17:56, 16 January 2019 (UTC)

  Done for a month. Mahir256 (talk) 20:59, 16 January 2019 (UTC)

User talk:198.237.49.220

Hello.This page is subversive.Please delete and protect it.Thanks David (talk) 18:18, 16 January 2019 (UTC)

  Done Blocked by MisterSynergy and page deleted and creation-protected by myself. Mahir256 (talk) 20:57, 16 January 2019 (UTC)

User Yigalmitt

This user is making lots of bad merges in the wikidata distributed game for several days now, does not react to User_talk:Yigalmitt and should be blocked for the time being.--Masegand (talk) 17:51, 12 January 2019 (UTC)

I reverted at least one of their merges; on the other hand at least one I saw was good, so not sure here... ArthurPSmith (talk) 18:15, 12 January 2019 (UTC)
I have blocked the user for three days hoping that after that time he could help clean up the mess he’s done. Unfortunately, after a quick glance (I’m on a mobile), I’ve got the impression that most merges are wrong, so it would be best to just revert them all. And maybe start thinking what can be done to prevent this type of situation. Andreasm háblame / just talk to me 19:12, 12 January 2019 (UTC)
Forgot to mention. In at least one merge, this weird thing happened. The enwiki sitelink was left behind because the destination item already had an enwiki sitelink, so the merge should have been prevented. I vaguely remember this being mentioned before, and maybe even a phabricator ticket. Anyone with better memory? Andreasm háblame / just talk to me 19:17, 12 January 2019 (UTC)
Yes, the same was true on one merge that I reverted - there were 4 or 5 sitelinks that were left behind, so it was clearly NOT a legitimate merge candidate in the first place. So a bug in the "distributed game" or whatever this person was using - @Magnus Manske: do you know about this issue? ArthurPSmith (talk) 22:00, 12 January 2019 (UTC)
@Masegand, ArthurPSmith, Andreasmperu: I have reverted all of their 145 mergers without individual checks whether they were okay or not. Most were obviously not, but some might have been okay. The user was not able to revert their mess by themselves. —MisterSynergy (talk) 09:55, 17 January 2019 (UTC)

quickstatements server issues?

I'm not sure if this is the right place to point out issues on quickstatements tool server. Since 2 days it is a nightmare to working with quickstatements. In the best case it'll be very slow and take "hours" to get changes up 'n' running and sometimes nothing happen, can't log in or get misc error messages like server errors, bad gateway or similar helpful hints. Possibly it'll be on my enviroment only.--Derzno (talk) 09:35, 15 January 2019 (UTC)

I confirm same problems (since 2-3 days), so it is not problem with your enviroment.--Jklamo (talk) 09:39, 15 January 2019 (UTC)
This twitter post by Magnus may be related: https://twitter.com/MagnusManske/status/1084777585828077570 ArthurPSmith (talk) 14:25, 15 January 2019 (UTC)
@Magnus Manske: there seem to still be problems? Are other tools affected? ArthurPSmith (talk) 19:29, 15 January 2019 (UTC)
@Lucas Werkmeister (WMDE): Lexeme forms was really slow for me just now too. OAuth problems of some sort? ArthurPSmith (talk) 19:35, 15 January 2019 (UTC)
I don't think it's anything I do with the tool. Is it browser mode or batch mode that's slow? Or both? --Magnus Manske (talk) 21:45, 15 January 2019 (UTC)
Browser mode. I've been doing about 20-200 commands at a time. Off and on it's just sort of frozen - right now I am waiting on a Quickstatments browser window with 36 commands, of which it's completed only 1, and the little circle's been turning round and round for a few minutes now with no progress... ? ArthurPSmith (talk) 01:31, 16 January 2019 (UTC)
@ArthurPSmith: I recently migrated the tool from the Stretch Bastion to the Trusty Bastion (compare wikitech:News/Toolforge Trusty deprecation), though I’m not sure if that even makes a difference when the tool itself is running on Kubernetes. Please let me know if the problem persists and I can bring it up with the Wikimedia Cloud Services folks. --Lucas Werkmeister (talk) 10:43, 16 January 2019 (UTC)
@Lucas Werkmeister: The lexeme-forms problem was very brief, it's been fine since then. Quickstatements still seems to have issues though. ArthurPSmith (talk) 18:21, 16 January 2019 (UTC)
The reason (for problems with tools like PetScan, Harvest Templates, QuickStatements, ...) might be a Replication Lag during the last days. --M2k~dewiki (talk) 22:12, 15 January 2019 (UTC)
Had some problems a day ago, but now the browser mode is working without any problems again. --Kam Solusar (talk) 00:51, 16 January 2019 (UTC)

So I just ran 10 edits from QuickStatements in browser more on the Sandbox item. Went smoothly. Maybe clear browser cache, and let me know if it gets stuck again. Ideally, turn on the network log in your bowser, have a look at the last result when it gets stuck, and let me know. --Magnus Manske (talk) 09:21, 16 January 2019 (UTC)

@Magnus Manske:, I'd tried it with firefox, opera, google and IE. On all browsers same result, I can't log in. --Derzno (talk) 15:35, 16 January 2019 (UTC)
@Magnus Manske: It was working for me for a while (off and on) - when I turned on the network monitor it was taking about 8 seconds per command. However, now I'm getting 500 server errors just going to the Quickstatements page! ArthurPSmith (talk) 16:39, 17 January 2019 (UTC)
And now Quickstatemtns is working (as of a few minutes ago) but lexeme-forms has gotten very slow (1+ minute response time to load a page). General tool server problems? ArthurPSmith (talk) 18:28, 17 January 2019 (UTC)
Sometimes it's working not stable. I had some batches which were stucked and came with no error message --Derzno (talk) 18:33, 17 January 2019 (UTC)

Pokedex number PfD

Similar to the discussion on P:P364 above, would an uninvolved administrator be able to make a decision for Wikidata:Properties_for_deletion#Pokédex_number_（P1112）_+_Pokémon_browser_number_（P1685? The discussion seems to have exhausted editors' interest and there isn't an overwhelming consensus. A closing decision would be appreciated. Deryck Chan (talk) 11:24, 16 January 2019 (UTC)

  Done --Pasleim (talk) 14:28, 17 January 2019 (UTC)

Вандализм

@Ymblanter: 185.120.89.196. Kalendar (talk) 18:59, 22 January 2019 (UTC)

  Done, 31h--Ymblanter (talk) 20:00, 22 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 06:06, 23 January 2019 (UTC)

Edit war around P364

Block https://www.wikidata.org/wiki/User:Jura1

He undoes my edits without discussion! --- Amihan27 (talk) 07:33, 8 January 2019 (UTC)

What is wrong with https://www.wikidata.org/w/index.php?title=Q6910927&diff=prev&oldid=830049197. Why is Jura1 allowed to undo it? --- Amihan27 (talk) 07:36, 8 January 2019 (UTC)

@Amihan27: have you attempted to contact Jura1 about this first? He isn't actively editing at this moment, so we will not block him without discussion either. @Jura1: It seems like a lot of your edits are not justified; for example in [3], you restored P364, which is deprecated in favor of P407. Please stop those scripted edits and explain your rationale here or at Wikidata:Project chat. Personally, I think that page is more appropriate for discussion about the content other than that related to administrator actions, which are not going to occur at this particular moment.--Jasper Deng (talk) 08:01, 8 January 2019 (UTC)
Perhaps both parties need to just stop until we can figure out what is going on. For the reference of others Wikidata:Administrators'_noticeboard/Archive/2018/12#Please_stop_batches_and_block_account ·addshore· talk to me! 09:53, 8 January 2019 (UTC)
@Amihan27: and @Jura1: so that they actually see this. ·addshore· talk to me! 10:06, 8 January 2019 (UTC)
Next we need to decide on how to move forward from here. We need to figure out what all possible options are, what has already been discussed and compile it somewhere for more than just the people involved ot review and discuss. ·addshore· talk to me! 11:49, 8 January 2019 (UTC)

Break

So discussion at Wikidata:Administrators'_noticeboard/Archive/2018/12#Please_stop_batches_and_block_account kind of fizzled out, and then the edit waring started again.

The discussion at Wikidata:Properties_for_deletion#language_of_work_or_name_(P407)_and_original_language_of_work_(P364) ended up in a section called FINAL_VOTE:_Suggested_closure_reasons, and after reading all of the unarchived content there I feel I could go and close that discussion for removing all usages except for films and renaming the property. Then we have a clear state that further discussions etc can try to move forward from, but the generally consensus regarding the properties at this point in time would be clear.

I have to admit that looking at Wikidata:WikiProject_Movies/Properties I find it slightly confusing when it comes to this language topic, I think that is partly due to the mix of modeling between the tv series and films both of which are listed on the same page and covered by the same wiki project.

I'll come and look at this section again in the morning before moving forward with anything. Please do not restart any edit warring.

·addshore· talk to me! 00:26, 9 January 2019 (UTC)

I forgot to ping anyone so @Amihan27: and @Jura1: so that you see this most recent comment in your notifications ·addshore· talk to me! 00:37, 9 January 2019 (UTC)

If this is all about original language of film or TV show (P364) vs language of work or name (P407), does that need to be sorted out first? Is there anybody besides Jura advocating to retain P364? ArthurPSmith (talk) 18:49, 9 January 2019 (UTC)
Looking at Wikidata:Properties_for_deletion#language_of_work_or_name_(P407)_and_original_language_of_work_(P364) the people in the discussion generally decided to keep it around for now just for films and probably revisit it at a later time. I'd be pro archiving that discussion with that conclusion and then revisiting at a later time / not on the RFD. ·addshore· talk to me! 19:46, 9 January 2019 (UTC)
@Liuxinyu970226, Pasleim, Snipre, ArthurPSmith, PKM: notify people who participated in the vote. 67.215.13.233 08:19, 10 January 2019 (UTC)
Just delete P364, no need to concern how Jura1 said. --Liuxinyu970226 (talk) 11:17, 10 January 2019 (UTC)
Proceed as suggested (keep P364 and rename for films). - PKM (talk) 19:39, 10 January 2019 (UTC)
Keeping P364 is just a source for a mess but as I don't take care of movies, I can live with that property if the label is changed to specify its use only for movie and if the description clearly states that it can be used only in items about movies or series. Snipre (talk) 21:40, 10 January 2019 (UTC)

I'm happy to run my script to migrate / deprecate the relevant statements, whichever outcome we decide on. Deryck Chan (talk) 15:23, 11 January 2019 (UTC)

I'm going to leave this open over the weekend and then close this and the RFD from ages ago on Monday. ·addshore· talk to me! 15:28, 11 January 2019 (UTC)

I'd love if we could finally solve this, but I have to ask: have all potential fringe cases where both statements would be needed actually been solved? Cases like editions/translations that we can't connect to the original work because we don't know which specific edition/translation they are based on. Or cases where we only know that a work is based on an unknown older text in another language, but nothing more that could be used to create an item for that original work (probably only applies to some very old historic texts). I've asked this question in the last discussion here, but got no answer. I'd hate if this becomes another case where such changes are made before all use cases have been worked out and the few people who have to deal with such cases are left on their own to figure out what to do now. --Kam Solusar (talk) 19:16, 11 January 2019 (UTC)

This is the administrator's noticeboard, where users publish requests and administrators solve them; unlike the project chat, requests for deletion or property talk pages, this isn't a place for editors to express their wishes or to discuss Wikidata's schemas and conventions. It's a reminder in case you want your contributions, which are valuable, to have an impact, and also a petition for us not to digress so that this thread, whose matter is an edit war, can be closed soon. Anyway, thank you all for your efforts to improve this area, including Amihan27 and Jura1, and thanks to Addshore for pushing this thread forward. --abián 21:45, 11 January 2019 (UTC)

I just made and edit to the original RFD closing the whole greater section. We should relabel the property and leave it for films / movies now. If someone wants to change this there should be more discussion at a different venue. Regarding the actual reason for the start of this section, if either user starts making edits that go against this general consensus before further discussion happens and different consensus is reached then I will block them... @Amihan27: and @Jura1: ·addshore· talk to me! 08:19, 14 January 2019 (UTC) ·addshore· talk to me! 08:19, 14 January 2019 (UTC)

@Addshore: What about TV series? --- Amihan27 (talk) 09:47, 14 January 2019 (UTC)
Sorry, my wording was / is "Consensus to merge, excluding usage on "television series" and "films" items. The property should be relabeled to reflect the tighter scope." ·addshore· talk to me! 11:38, 14 January 2019 (UTC)
@Addshore: A related dispute occurred between EncycloPetey and me as to whether your closure approved renaming P:P407. I understood it that both properties should be renamed as discussed in the PfD, but EncycloPetey seems to think that a PfD could not mandate the renaming of a property. Can you clarify your decision on this matter? Deryck Chan (talk) 23:12, 15 January 2019 (UTC)
The closing "consensus" vote says nothing at all about a rename of any property; it merely advocates for deletion of a property in most of its usages. A deletion discussion (lasting a year) about one property is not the appropriate place to put a discussion about renaming a different high-profile property in widespread use by multiple Wikiprojects. And a rename to generic "language" instead of the consensus-established "language of work or name" will lead to problems of confusion with similarly-named properties rather than solve them. If the property is to be renamed, a single focused discussion should address that issue, with interested parties notified.
"The property should be relabeled" in the closing statement presumably refers to the remaining usages of the property that was to be deleted, and not a different property. --EncycloPetey (talk) 23:23, 15 January 2019 (UTC)
As EncycloPetey says, my sentence was talking about the property with remaining usages from the PfD and no other properties, so P364. Sorry, I could have been a bit clearer with the sentence. P364 has, as far as I can see also already have its label changed (I haven't checked all languages). ·addshore· talk to me! 15:30, 16 January 2019 (UTC)
Okay, thanks. Deryck Chan (talk) 16:43, 16 January 2019 (UTC)

I have migrated all existing uses of original language of film or TV show (P364) except those in the class audiovisual work (Q2431196) to language of work or name (P407); there were 295 migrations. Deryck Chan (talk) 19:17, 18 January 2019 (UTC)

User:Divyansh kumar Srivastava

User:Divyansh kumar Srivastava keeps creating unnotable items, supposedly for himself. Q60525929 and Q60525061 were already deleted, now he created it again (Q60615994, Q60615373). I request admin action, namely deletion and either block or warning of the user. Steak (talk) 19:58, 16 January 2019 (UTC)

User seems to be globally locked, items are deleted. Bovlb (talk) 00:50, 19 January 2019 (UTC)

Вандализм

@Ymblanter: 213.151.4.196 Kalendar (talk) 06:07, 23 January 2019 (UTC)

  Done, 31h--Ymblanter (talk) 06:48, 23 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 05:44, 24 January 2019 (UTC)

Вандализм

@Ymblanter: 213.59.151.232 Kalendar (talk) 05:45, 24 January 2019 (UTC)

  Done--Ymblanter (talk) 06:29, 24 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 17:39, 24 January 2019 (UTC)

IP 93.34.90.40

Hi,

This visitor seems to have had a lot of fun since the 17th of January by modifying the Italian descriptions (ex : Mary Stuart = Stuart ignioranti). Can one of you take a look, please? See 93.34.90.40 and also maybe 95.74.96.128. Thanks, --BeatrixBelibaste (talk) 06:04, 19 January 2019 (UTC)

  Done IP 93.34.90.40 is blocked for a month. Lymantria (talk) 07:53, 19 January 2019 (UTC)

Jura1 - vandalism to BBLD ID using rollback and other kind of BBLD vandalism

User:Jura1

  • mass-vandalised BBLD IDs (P2580) using rollback
  • vandalised the page Property:P2580 directly
  • vandalised the talk page
  • tried to get person items deleted when they were connected with the BBLD (but that was turned down)

He further managed to have IP edits to the property amd statements involving the property blocked, despite the fact that IPs were the most knowledgeable about the BBLD IDs.

The more than 6 months of harrassement of IPs and other users that wanted to fix his fake information insertations affected Wikidata, dewiki, ruwiki and other projects.

The fake information insertion has been taken up by the BBLD itself and is documented in Wikipedia.

Is that the only story of fake information insertion by that user? See his 2006 creation "descriptive item used as unit (Q22302160)" and the connected items like human, aircraft etc. and judge yourself.

78.54.224.108 15:48, 19 January 2019 (UTC)

Jura1 - rollback - repair deletion of valid statements

https://www.wikidata.org/w/index.php?title=Q3843596&diff=830181579&oldid=829806869

If the statements were valid, why did Jura1 delete them?

I reverted, but can someone check? 78.54.224.108 16:03, 19 January 2019 (UTC)

83.49.71.128

IP is vandalizing items. Esteban16 (talk) 17:19, 19 January 2019 (UTC)

  Done, 31 h--Ymblanter (talk) 19:40, 19 January 2019 (UTC)

Вандализм

@Ymblanter: 95.153.132.5. Kalendar (talk) 17:40, 24 January 2019 (UTC)

  Done--Ymblanter (talk) 20:10, 24 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 08:38, 25 January 2019 (UTC)

Вандализм

@Ymblanter: Король храп. Kalendar (talk) 18:06, 24 January 2019 (UTC)

  Done--Ymblanter (talk) 20:10, 24 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 08:39, 25 January 2019 (UTC)

Вандализм

@Ymblanter: Weirdointhesewers. Kalendar (talk) 18:10, 24 January 2019 (UTC)

  Done--Ymblanter (talk) 20:10, 24 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 08:39, 25 January 2019 (UTC)

Вандализм

@Ymblanter: 2A00:1FA0:C6B3:3330:AD59:2D5B:3156:2B5C. Kalendar (talk) 18:12, 24 January 2019 (UTC)

  Done--Ymblanter (talk) 20:10, 24 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 08:39, 25 January 2019 (UTC)

Вандализм

@Ymblanter: 188.186.196.90. Kalendar (talk) 18:24, 24 January 2019 (UTC)

  Done--Ymblanter (talk) 20:10, 24 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 08:39, 25 January 2019 (UTC)

Вандализм

@Ymblanter: 176.59.132.41 Kalendar (talk) 08:40, 25 January 2019 (UTC)

  Done--Ymblanter (talk) 08:52, 25 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 09:17, 25 January 2019 (UTC)

Вандализм

@Ymblanter: 213.87.139.202 Kalendar (talk) 08:44, 25 January 2019 (UTC)

  Done--Ymblanter (talk) 08:53, 25 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 09:18, 25 January 2019 (UTC)

Wikimedia Foundation (Q180)

Protection needed: Please semi-protect it. Kind regards, — TBhagat (contribs | talk) 12:01, 20 January 2019 (UTC)

  Done, for one month. --Okkn (talk) 12:09, 20 January 2019 (UTC)

Lexeme:L123

Please have an admin to delete this page and restore its non-recent versions. see phab:T214774.--GZWDer (talk) 22:02, 26 January 2019 (UTC)

Interesting problem. I deleted the page, but when I got an internal error when I tried to restore it without the page-breaking revision. I've restored the whole page with the redirecting edit, hopefully a dev can sort this out. -- Ajraddatz (talk) 22:11, 26 January 2019 (UTC)
Now I successfully reverted an very old version. So this can be closed now. I will trying to reproduce the issue in Test Wikidata.--GZWDer (talk) 22:29, 26 January 2019 (UTC)
This section was archived on a request by: --GZWDer (talk) 22:29, 26 January 2019 (UTC)

SlingWikiBot

This user seems to replace precise dates with vague ones. Is this advantageous?--117.136.38.140 15:07, 18 January 2019 (UTC)

Can you list some diffs here for closer evaluation? The operator tries to undo their own edits from past weeks, as there was valid criticism how they replaced *sourced* vague dates with more precise ones which were not found in the original sources. @Anders-sandholm: FYI. —MisterSynergy (talk) 15:53, 18 January 2019 (UTC)
Thanks for pinging me MisterSynergy. Not sure I have much to add here. I made the original edits (from vague to precise) because I assumed a more precise value would be better - even when Wikipedia was the source. I fully respect the strong wish to have things verifiable with high quality sources and hence I am - as requested - rolling back edits that were made to values that already had non-wikipedia sources associated. For dates that either didn't have any sources or only had Wikipedia as source, I am keeping the precise dates. --Anders-sandholm (talk) 08:30, 21 January 2019 (UTC)

Vandalism by Festivalmoss

The user is excessively vandalizing items. --Esteban16 (talk) 22:33, 20 January 2019 (UTC)

Festivalmoss has been warned. Pamputt (talk) 08:54, 21 January 2019 (UTC)

Semi-protection for "RM" (Q20514446) and "Jin" (Q24276424)

Hello,
Could you semi-protect RM (Q20514446) and Kim Seok-jin (Q24276424), due to frequent vandalism from various IP addresses?
They have been semi-protected already, between December 2017 and December 2018.
Regards --NicoScribe (talk) 18:50, 21 January 2019 (UTC)

  Done--Ymblanter (talk) 19:32, 21 January 2019 (UTC)

Protection for Q55649583

Hi, could you protect Alexandre Benalla (Q55649583) due to frequent vandalism? Thanks! Lofhi (talk) 20:37, 21 January 2019 (UTC)

  Done for a month. Low vandalism, but since a bunch of vandalism goes undetected here I am willing to be a bit overzealous in protection. -- Ajraddatz (talk) 18:50, 22 January 2019 (UTC)

Special:Contributions/172.16.1.252

This is a bot that does not log in.--GZWDer (talk) 21:01, 21 January 2019 (UTC)

In addition, it created some non notable items like Q60775880.--GZWDer (talk) 21:19, 21 January 2019 (UTC)

blocked 172.16.1.252

I got a report that a bot on Labs is malfunctioning and was editing while logged out. Under the Bot policy, it states "Bots should not edit while logged out, and can use the AssertEdit to ensure that." Therefore I have blocked it for 24 hours. Feel free to unblock if the operator is identified or extend if it is not identified and activity continues after block expire. — regards, Revi 15:18, 22 January 2019 (UTC)

Found the above topic after saving. Extending to 1 week. — regards, Revi 15:20, 22 January 2019 (UTC)
I suspect this may be YiFeiBot and have contacted the operator at User talk:YiFeiBot#editing anonymously. --Lucas Werkmeister (talk) 15:22, 22 January 2019 (UTC)
I was wrong, according to IRC (#wikimedia-cloud) it was actually Ladsgroup’s Dexbot. Sorry for the confusion. --Lucas Werkmeister (talk) 17:10, 22 January 2019 (UTC)

Protection for Q26690130

The item is frequently vandalized. It does not receive "high" amount of vandalism but I consider that a semi-protection for a while would be useful. Esteban16 (talk) 15:26, 22 January 2019 (UTC)

The item has been protected for a few months by Mahir256. -- Ajraddatz (talk) 18:48, 22 January 2019 (UTC)

User talk:Trijnstel

All recent edits are vandalism. This should be protected for a long time.--GZWDer (talk) 22:03, 22 January 2019 (UTC)

  Done semi'd for a year. Mahir256 (talk) 22:04, 22 January 2019 (UTC)

Harassment, probably someone's sock from English Wiki

Someone created a brand new account just to leave me this note;[4]

  • "Really? Why did you take Louis Aragon's name, Behnam?? You are nothing like him. Additionally, your life isn't worth living. Who would want to live a life like yours, scumbag? Go back to doing dirty laundry work, you ugly excuse of an animal."

Its probably a sock of LTA Lagoo sab.[5]

- LouisAragon (talk) 22:17, 22 January 2019 (UTC)

Indef-blocked here. Mahir256 (talk) 22:21, 22 January 2019 (UTC)

Вандализм

@Ymblanter: 2a00:1fa0:823d:e3a2:a4eb:27f4:26e8:25f5. Kalendar (talk) 19:23, 26 January 2019 (UTC)

  Done--Ymblanter (talk) 20:03, 26 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 08:00, 28 January 2019 (UTC)

Вандализм

@Ymblanter: KorLayOfficial Kalendar (talk) 08:00, 28 January 2019 (UTC)

  Done--Ymblanter (talk) 08:02, 28 January 2019 (UTC)
@Ymblanter: он же 176.226.153.73 Kalendar (talk) 08:04, 28 January 2019 (UTC)
  Done, also protected the page--Ymblanter (talk) 08:12, 28 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 08:55, 28 January 2019 (UTC)

Вандализм

@Ymblanter: Иван Ровный Kalendar (talk) 12:25, 28 January 2019 (UTC)

  Done--Ymblanter (talk) 12:27, 28 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 20:14, 28 January 2019 (UTC)

Request for undeletion (Turkish MPs)

Q6022056, Q17431581, Q20476984, Q6082358, Q21526084, and Q17431036 have all been deleted recently. I don't think I created any of these, but all of them were Members of the Turkish Assembly. I'm presuming they were each originally linked to articles (likely on trwiki) that have since been deleted, leaving them with no other references. If they can be reinstated I can find suitable references for each. Thanks. --Oravrattas (talk) 09:56, 23 January 2019 (UTC)

@Oravrattas: Is there any particular reason (e.g. external catalogs or wikipages that link to those items) why you want to undelete those items rather than create new items? Deryck Chan (talk) 10:25, 23 January 2019 (UTC)
  Done; all restored. —MisterSynergy (talk) 11:04, 23 January 2019 (UTC)
@Deryck Chan: Yes, they were all linked in an external catalog, but also I was unable to recreate them as they had been, as I had no way of knowing what other data was on them. MisterSynergy, thanks for reinstating. I'll find references for them now. --Oravrattas (talk) 11:18, 23 January 2019 (UTC)

Napoleon (Q517)

Protection needed: Please semi-protect it. Kind regards, — TBhagat (contribs | talk) 16:44, 24 January 2019 (UTC)

I don't see why protection is needed. It isn't vandalised that often by IP's. Mbch331 (talk) 17:47, 24 January 2019 (UTC)

Vandalism

Please block 190.15.92.146 (talk • contribs • logs). 50+ vandalism edits this morning. --Kam Solusar (talk) 08:51, 28 January 2019 (UTC)

  Done, 31h--Ymblanter (talk) 12:29, 28 January 2019 (UTC)
Thanks! --Kam Solusar (talk) 12:20, 30 January 2019 (UTC)
This section was archived on a request by: Kam Solusar (talk) 12:20, 30 January 2019 (UTC)

Вандализм

@Ymblanter: Parokonnyi.andrii Kalendar (talk) 05:28, 30 January 2019 (UTC)

  Done--Ymblanter (talk) 20:10, 30 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 20:10, 30 January 2019 (UTC)

Вандализм

@Ymblanter: Олжас Нұралы. Kalendar (talk) 20:08, 30 January 2019 (UTC)

  Done--Ymblanter (talk) 20:11, 30 January 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 20:12, 30 January 2019 (UTC)

Q15833607, Q18015594, Q15920546

Protect please this element by the consensus version--Unikalinho (talk) 09:46, 24 January 2019 (UTC)

  Done for 1 week. Shmurak, Rausch and Unikalinho please talk not to start edit warring anymore. Pamputt (talk) 10:42, 24 January 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 13:54, 31 January 2019 (UTC)

Merge

Please, could you merge Gustave Cabanès (Q56546052) with Gustave Cabanès (Q21506787)? This is a duplicate. 109.9.71.223 14:46, 24 January 2019 (UTC)

  Done Pamputt (talk) 15:02, 24 January 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 13:54, 31 January 2019 (UTC)

Protection for Q16214688

Q16214688 needs some protection. It's under vandalism due Venezuelan political crisis. Montgomery (talk) 19:04, 25 January 2019 (UTC)

  Done —MisterSynergy (talk) 19:46, 25 January 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 13:54, 31 January 2019 (UTC)

Vandalism

The last hours an anonymous IP is making changes regarding population facts in Pyli Municipality (Q2266175) and Pyli (Q15088667). This comes as a follow-up of similar vandalisms in the Greek Wikipedia articles of these items ([6] & [7]).--Texniths (talk) 10:55, 26 January 2019 (UTC)

  Done I’ve protected Pyli (Q15088667), and I’m keeping an eye on Pyli Municipality (Q2266175) in case there’s more vandalism. Thanks! Andreasm háblame / just talk to me 18:29, 26 January 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 13:54, 31 January 2019 (UTC)

Semi-protection for Q165257

Please semi-protect Lope de Vega (Q165257) - frequent IP vandalism, popular theme.--Jklamo (talk) 01:59, 27 January 2019 (UTC)

  Done Andreasm háblame / just talk to me 05:10, 27 January 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 13:54, 31 January 2019 (UTC)

Block for 126.67.222.121

Please block 126.67.222.121 (talk • contribs • logs). This IP vandalizes descriptions of items. --本日晴天 (talk) 03:14, 27 January 2019 (UTC)

  Done Blocked for 1 month. Lymantria (talk) 07:44, 27 January 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 13:54, 31 January 2019 (UTC)

Semi-protection for "Park Chan-yeol" (Q7137681)

Hello,
Could you semi-protect Park Chan-yeol (Q7137681), due to frequent vandalism from various IP addresses?
Regards --NicoScribe (talk) 10:36, 27 January 2019 (UTC)

  Done; starting with 3 months … —MisterSynergy (talk) 10:39, 27 January 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 13:54, 31 January 2019 (UTC)

Block request

Hi, can you block 79.155.55.28 or semi-protect Q123041 ? Many thanks. --Do not follow (talk) 12:10, 28 January 2019 (UTC)

  Done, 31h. Pls ping me if they continue to vandalize the item from another IP.--Ymblanter (talk) 12:31, 28 January 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 13:54, 31 January 2019 (UTC)

Block request

Hi, 195.221.62.1 has been vandalising Q926 for months, and other items too. A block for a significant time would be helpful. Thanks. --Do not follow (talk) 15:46, 28 January 2019 (UTC)

  Done Semi'd the item and blocked the /24 subnet for a month. Mahir256 (talk) 17:40, 28 January 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 13:54, 31 January 2019 (UTC)

IPBE request for User:tagishsimon

Hi tagishsimon, is caught by a steward's IP block, he has requested for IPBE block exemption, any opportunity we could expedite that? special:userrights/tagishsimon On tagishsimon's behalf, thanks.  — billinghurst sDrewth 08:07, 29 January 2019 (UTC)

Please ask global IP block exempt here. We can grant it locally, but I will work only here. Ping me if you still need the local right. Bencemac (talk) 08:11, 29 January 2019 (UTC)
@Bencemac: I have fixed enWP and Meta as a workaround, we need WD now. We will tackle stewards when they are around.  — billinghurst sDrewth 08:16, 29 January 2019 (UTC)
  Done. Bencemac (talk) 08:23, 29 January 2019 (UTC)
Yay. You're a star, Bencemac. Thank you. (Ditto billinghurst). --Tagishsimon (talk) 08:24, 29 January 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 13:54, 31 January 2019 (UTC)

Block request

Hi, please block 50.201.213.206 : more than a month of vandalism. Thanks. --—d—n—f (talk) 15:01, 29 January 2019 (UTC)

Already   Done by Mahir256--Ymblanter (talk) 20:24, 29 January 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 13:54, 31 January 2019 (UTC)

Protection for Q30513835

A lot of IPs have been changing the data of the item, claiming that he is musician. This has happened since October 2018, and I think a protection would be useful. Esteban16 (talk) 04:43, 31 January 2019 (UTC)

  Done Let's try a week first. Mahir256 (talk) 04:47, 31 January 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 13:54, 31 January 2019 (UTC)

Semi-protection for Q5284

Please semi-protect Bill Gates (Q5284) - frequent IP vandalism, popular theme, living person.--Jklamo (talk) 08:55, 31 January 2019 (UTC)

  Done —MisterSynergy (talk) 09:37, 31 January 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 13:54, 31 January 2019 (UTC)

Property:P2580 and Property talk:P2580

Please indef. semi-protect the above. After the previous protection expired, the problem IPs returned. --- Jura 11:44, 26 January 2019 (UTC)

Semi'ed both, but let's start with one year first. Mahir256 (talk) 18:42, 26 January 2019 (UTC)

Semi-protection for Q9458

Please semi-protect Muhammad (Q9458) - frequent IP vandalism, popular theme.--Jklamo (talk) 23:53, 31 January 2019 (UTC)

  Done semi-protected for 1 year. Pamputt (talk) 07:03, 1 February 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 11:10, 1 February 2019 (UTC)

Please undelete

Please restore the lexemes mentioned at Wikidata:Requests_for_deletions/Archive/2019/01/13#Graphemes_in_Lexemes. These entities were speedily deleted over New Year holidays while people were asked to comment on it on the lexeme project chat, preventing users to actually review them and comment on them. --- Jura 07:18, 27 January 2019 (UTC)

Double Coordinates using QS

My recent upload on Quickstatements (#quickstatements; #temporary_batch_1548573119179), produced a few duplicates. Is there a quick way of finding these? Example: Partishow. I've checked c. 30 by hand, all coordinates are correct, and this duplication of coordinates / map is the only issue I'm aware of. Isn't over-ridng the old staement a better way of doing this, as is default with most statements? Llywelyn2000 (talk) 08:08, 27 January 2019 (UTC)

This looks really good! Thanks Jura, I'll dig deeper into it asap! Llywelyn2000 (talk) 09:32, 27 January 2019 (UTC)
All villages in Powys done. I'll add a link to this query on cywiki so that the community can keep an eye and filter for all of Wales. Thanks Jura - always a great help! Llywelyn2000 (talk) 17:35, 27 January 2019 (UTC)

Steward election nominations closing soon

Hello everyone! The 2019 steward elections are currently in the nomination phase, with a day left before nominations close. We don't have many candidates so far. If you're interested, have experience working on multiple wikis, or have experience with advanced permissions here then please consider helping out. Some general information on what stewards are and what they do can be found at the Meta page. I'm also happy to answer any questions relating to the election or the role. -- Ajraddatz (talk) 18:48, 27 January 2019 (UTC)

Modifications on Q3333484

Hi, can you have a look at these modifications ? This user tried to erase the content of an article on fr.wp and redirect it to another. I see the item has been recently protected. Thanks. --Do not follow (talk) 17:38, 28 January 2019 (UTC)

Block

Please, block User:Profire128. Vandal account. Stanglavine (talk) 22:04, 31 January 2019 (UTC)

I will not do it (maybe another admin will do). My point is this account only did 2 edits (that are vandalism). Let us see whether he continues before blocking (he will probably not come back). Pamputt (talk) 07:02, 1 February 2019 (UTC)

Protection of thousand of items

@Abián: My watchlist was flooded today with protection logs with the description “High risk, one of the 3000 most used Wikidata Items on Wikimedia projects”. I checked and thousand of items had been protected by Abián. So I’m wondering if I miss something. Was an agreement reached about this subject somewhere? Andreasm háblame / just talk to me 18:23, 26 January 2019 (UTC)

Hi, Andreasmperu. These actions are based on an investigation carried out by Wikidata's development team (thanks!) whose documentation is linked from all the protection summaries and available here. Contrary to what the numbers suggest, I haven't protected more than 3,000 (~0,005%) Items so that we can all check the results of this measure without preventing potentially valuable edits. I didn't assign myself the flood flag so that users were aware of this issue, I thought they wouldn't be so many Items as to cause a problem for anyone; if that was your case, my apologies, :-( I should definitely consider using the flag next time. Thanks for caring and, if you have any other doubts, feel free to ask again! --abián 19:30, 26 January 2019 (UTC)
So no prior discussion/consensus before undertaking this task then? I understand the good intentions, but performing such a big task without asking for feedback doesn’t seem right for a collaborative project. Not using a flood flag is merely inconvenient, my real concern was to know if this was a personal (not community) decision, which seems to be the case. Andreasm háblame / just talk to me 20:37, 26 January 2019 (UTC)
+1; I see several items from my watchlist being indefinitely protected right now, but most of them have never seen any vandalism. Of course I do see and understand the intention as well, but I think we should discuss first (RfC?) where to draw a line. The page protection policy allows that “for high-use pages (such as the main page and the community portal) it [page protection] can be done without such [vandalism or spam] history”, but this is rather vague and has not been used in mainspace in larger numbers until now to my knowledge. I’d also be interested in the metrics used for the determination of “the 3000 most used Wikidata Items on Wikimedia projects”. —MisterSynergy (talk) 20:47, 26 January 2019 (UTC)
They range from the most used Item, used on 6,329,731 different pages on Wikimedia projects, to the 3000th most used Item, used on 3228 different pages on Wikimedia projects. Before semi-protecting I've made sure with these numbers and a manual review that the potential damage of vandalism on any of these Items is very high while the potential contribution of non-confirmed users, taking into account some samples of edit histories and the degree of completeness of the content, isn't very significant. Nonetheless, if most people thought this measure is negative for Wikimedia projects (I don't think so), the protections can be reverted; I always edit with the idea that everything I contribute can be undone if convenient... and neither one action nor the other is a bad thing. :-) --abián 21:40, 26 January 2019 (UTC)
You can check the usage of an item easily in its page information (link is in the sidebar of each item). When looking at the page information on a Wikipedia article you will see which items it gets data from. The list Goran generated is based on that. --Lydia Pintscher (WMDE) (talk) 11:59, 27 January 2019 (UTC)
@GoranSMilovanovic, Lydia Pintscher (WMDE): as those present in the Phabricator task to which David linked. Mahir256 (talk) 20:58, 26 January 2019 (UTC)
I don't care about the flood flag, but such a large mass protection like this should have been discussed onwiki. --Rschen7754 21:38, 26 January 2019 (UTC)
Notified the community. --Succu (talk) 21:51, 26 January 2019 (UTC)
Looks like User:Abián has a problem with community input. --Succu (talk) 22:04, 26 January 2019 (UTC)
@Abián: good intentions, but you should have discussed this before mass protecting such large number of items. Multichill (talk) 22:06, 26 January 2019 (UTC)
Large mass semi-protection for these items has many pros (the vandalisms probably outnumber by far the good edits in most of them), but I think that it would be better to discuss in a RfC which items do we want to preventively protect (maybe also items having less uses than these, or maybe the contrary) and in any case it would be better having, in the future, some automatic semi-protection when the number of uses raises above a certain number (which can be 1 million uses or some thousands uses, it depends on the RfC). --Epìdosis 22:13, 26 January 2019 (UTC)
Until a RfC is done the protection should be removed! --Succu (talk) 22:19, 26 January 2019 (UTC)
Agreed that discussion should have happened before such a large action. I personally prefer to only protect items if there is a history of vandalism, but I also know that a lot of vandalism goes undetected here. There might be a balance in this situation, but we should discuss that. -- Ajraddatz (talk) 22:27, 26 January 2019 (UTC)
  • Please unprotect. WMDE usually doesn't take any editorial decisions of that type. --- Jura 05:46, 27 January 2019 (UTC)
    • We don't and we haven't in this case. We provided a list of highly-used items so editors can work on protecting them as they see fit. This has been requested many times. Abian is one of the people who deeply cares about the integrity of our content and sees the fallout of when we fall short of the expectations of the other Wikimedia projects. Maybe there should have been more discussion but let's please not forget the good intentions behind it. --Lydia Pintscher (WMDE) (talk) 11:59, 27 January 2019 (UTC)
As vandalism at Wikidata, just like Commons, may immediately affect a large number of Wikipedias I very much welcome these protections. --Denniss (talk) 10:12, 27 January 2019 (UTC)
  • These protections are good thing. Automatic edit description is bad, however ((разн. | история) . . д Inkscape (Q7918); 18:11 . . Abián (обсуждение | вклад) (Protected "Q7918": High risk, one of the 3000 most used Wikidata Items on Wikimedia projects ([Edit=Allow only autoconfirmed users] (indefinite)))). It is not about where vandalism was happened, it is about where it can make a lot of harm. — Vort (talk) 11:56, 27 January 2019 (UTC)
  • @Abián: Please undo the protections. The are not in line with existing policy. I don't have a firm opinion about whether or not to protected items this way, but it's not something that should happen without a community decision. ChristianKl ❪✉❫ 13:20, 27 January 2019 (UTC)
    • Reverting also requires decision. It is better not to hurry, I think. Also vandals are now notified about where they can concentrate their efforts. — Vort (talk) 14:24, 27 January 2019 (UTC)
      • The most used items are fairly well-watched anyways. If vandalism occurs, we can still protect them individually until there is consensus for a mass-protection approach. —MisterSynergy (talk) 14:38, 27 January 2019 (UTC)
        • Vandalism triggers update for thousands (or maybe even millions) of pages in Wikipedias. And fast reversion here does not mean fast reversion at wikis. In search engines vandalism may live even longer. — Vort (talk) 14:48, 27 January 2019 (UTC)
      • We used to have a problem with vandalism on other entities, but solved it without locking out all active Wikipedians in rare languages but hardly contributing to Wikidata. Oddly contributors at some Wikipedia (eswiki) are hardly receptive when you tell them to fix vandalism issues on their side. Maybe "deeply cares" is slightly exaggerated. --- Jura 15:25, 27 January 2019 (UTC)
  • These should not have been protected, and should certainly not have been protected without prior discussion. The protection should be removed. --Yair rand (talk) 21:17, 27 January 2019 (UTC)
  • 3000 is a very small number and I can understand why Abian failed to notify the community, however, notification should indeed have happened. We definitely should keep these protections - the items are used hundreds of times in Wikimedia projects - but let's discuss a more systematic approach for the future.--Vojtěch Dostál (talk) 11:57, 28 January 2019 (UTC)
  • If we decide that protecting the most used entities is a good idea, then perhaps we should think about automating this? ·addshore· talk to me! 13:45, 28 January 2019 (UTC)
I perfectly agree about automating, as I said above. And it should also be fixed the problem just reported here by ArthurPSmith (if it has not been already). But we need a RfC about how many of the most used items should this automating include. --Epìdosis 20:27, 29 January 2019 (UTC)
Yes please. This has helped a lot to reduce vandalism that has a significant (and negative) impact within the Wikimedia projects. Thank you @Abián: - please develop this further to be more automated! Thanks. Mike Peel (talk) 22:14, 29 January 2019 (UTC)
Are you saying you are noticing a sizeable reduction in vandalism when you patrol after this change? ChristianKl ❪✉❫ 17:14, 31 January 2019 (UTC)
@ChristianKl: The amount of Wikidata vandalism I spot through enwp or commons has decreased a lot. E.g., at items like George (Q15921732), Catholicism (Q1841) and others, which is a good thing. That was mostly coming from IPs to the English labels of highly-visible items. Mike Peel (talk) 09:30, 1 February 2019 (UTC)
  • Will this block updating sitelinks for page moves (for non-autoconfirmed wikidata users) or has that bug been fixed? ArthurPSmith (talk) 15:02, 28 January 2019 (UTC)
  • Protecting most used Wikidata items is a very good idea. Vandalism has a very bad influence on Wikidata reputation within the Wikimedia projects. The benefit of anonymous IP addresses editing in these popular items is negligible, while their vandalism has direct negative impact.--Jklamo (talk) 22:32, 29 January 2019 (UTC)
    The review procedure on some wikis (dewiki: all articles, enwiki: some pages such as Sasha Grey) is nicer than semi-protect, resolving an {{edit request}} is more work for all involved parties. –84.46.53.126 07:46, 30 January 2019 (UTC)
    This doesn't only block anonymous adresses. It also blocks Wikipedian's without an established Wikidata history who see an error that passes through from fixing that error. ChristianKl ❪✉❫ 17:14, 31 January 2019 (UTC)
    50 edits threshold is very easy to reach on Wikidata and there are 99,99 % of items, that are not protected. Even for Wikipedians it is good to familiarize with Wikidata rules and customs before editing high visible items. Also note that these items are above average quality with low probability of errors.--Jklamo (talk) 10:20, 4 February 2019 (UTC)

So could someone with some experience open a RfC about protecting most-used items (yes or not? if yes, how many and using which criteria? protecting manually or automatically? with edit-review or not?) It would be better to continue the discussion there. --Epìdosis 12:43, 4 February 2019 (UTC)

I can go for an initial draft, which should be the first step of the RfC. This initial draft should be completed and improved by other editors. When editors who want to get involved in this consider that the draft already presents enough data, including all the relevant pros and cons of each option, and that the page is well structured, then we'll actually be able to launch the RfC. What do you think? --abián 13:02, 4 February 2019 (UTC)
  Support --Epìdosis 15:05, 4 February 2019 (UTC)
Here's the draft. You can left comments on the content or structure of the RfC on the talk page. Thanks in advance! --abián 20:22, 5 February 2019 (UTC)
Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Administrators%27_noticeboard/Archive/2019/01&oldid=857140263"