Wikidata:Administrators' noticeboard/Archive/2019/06

From Wikidata
Jump to navigation Jump to search

Вандализм

@Ymblanter: 176.59.49.16. Kalendar (talk) 18:13, 1 June 2019 (UTC)

Нет смысла, динамический айпи, одна правка, едва ли сюда вернется.--Ymblanter (talk) 18:24, 1 June 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 18:25, 1 June 2019 (UTC)

Создание многочисленных страниц, не связанных с разделами Викимедиа

@Ymblanter: посмотрите вклады 1, 2, 3 участников, создающих страницы Викиданных, не связанных с разделами Викимедиа. Тематика страницы - некий маршал ашроев и уйма его родственников. Kalendar (talk) 18:25, 1 June 2019 (UTC)

✓ Done, всё удалил--Ymblanter (talk) 18:40, 1 June 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 18:56, 1 June 2019 (UTC)

Merge

Please merge conseil de prud'hommes de Nîmes (Q60575715) with conseil de prud'hommes de Nîmes (Q61197198). This is a duplicate. 92.184.102.189 19:07, 1 June 2019 (UTC)

✓ Done Esteban16 (talk) 23:27, 1 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 07:12, 4 June 2019 (UTC)

GirlsAskGuys reverting

At Q5564598 the link to the deleted wp:en article is repeatedly reinserted by an IP. Sandstein (talk) 08:36, 2 June 2019 (UTC)

✓ Item deleted by Bencemac. Esteban16 (talk) 16:11, 3 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 07:12, 4 June 2019 (UTC)

Eduardo Pondal (Q867025)

please semi-protect this item again--DiMon2711 12:40, 2 June 2019 (UTC)

✓ Semi-protected for a month. Esteban16 (talk) 16:10, 3 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 07:12, 4 June 2019 (UTC)

146.200.48.198

146.200.48.198 vandalism--DiMon2711 15:21, 2 June 2019 (UTC)

✓ Done Jianhui67 talk★contribs 15:24, 2 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 07:12, 4 June 2019 (UTC)

Deletion of P6270) (P6270))

There seems to be a consenus for deleting P6270 (P6270) in https://www.wikidata.org/wiki/Wikidata:Properties_for_deletion#Boobpedia_article_%28P6270%29. Given my own involvement in the discussion, I won't do the deletion myself, but I would be glad if another admin would go ahead with it. ChristianKl ❪✉❫ 21:31, 2 June 2019 (UTC)

✓ Done − Pintoch (talk) 13:32, 4 June 2019 (UTC)
This section was archived on a request by: Pintoch (talk) 13:32, 4 June 2019 (UTC)

Semi-protection for Q301

Please semi-protect El Greco (Q301) - popular theme, persistent IP vandalism from various IP addresses. --Jklamo (talk) 22:53, 2 June 2019 (UTC)

✓ Done by Mahir256 - semi-protected for a year. Bovlb (talk) 18:30, 3 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 07:12, 4 June 2019 (UTC)

193.39.159.73

193.39.159.73 vandalism--DiMon2711 14:39, 3 June 2019 (UTC)

✓ Done Blocked for 3 months and other past contributions reviewed and reverted. Bovlb (talk) 18:35, 3 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 07:12, 4 June 2019 (UTC)

Burj Khalifa (Q12495)

please semi-protect this item forever or for a very long time as a popular item and excessive vandalism--DiMon2711 14:41, 3 June 2019 (UTC)

✓ Done Semi-protected for 3 months. Bovlb (talk) 18:26, 3 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 07:12, 4 June 2019 (UTC)

neo soul (Q268253)

excessive vandalism today. Please semi-protect this item--DiMon2711 14:43, 3 June 2019 (UTC)

✓ Done Semi-protected for a week. Bovlb (talk) 18:26, 3 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 07:12, 4 June 2019 (UTC)

181.47.81.176

please semi-protect this item--DiMon2711 19:02, 3 June 2019 (UTC)

✓ Done Juan Larrea (Q2790355) semi-protected, and 181.47.81.176 (talk • contribs • logs) blocked. Bovlb (talk) 19:12, 3 June 2019 (UTC)
@Bovlb: thanks! Sorry, I unsuccessfully copied. I meant Winston Vallenilla (Q16214688). Regards, DiMon2711 19:32, 3 June 2019 (UTC)
✓ Done again - semi-protected for three months. Bovlb (talk) 19:50, 3 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 07:12, 4 June 2019 (UTC)

Ashley Grace (Q58640952)

please semi-protect this item forever--DiMon2711 10:43, 4 June 2019 (UTC)

✓ Done, for 6 months--Ymblanter (talk) 10:57, 4 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 12:28, 4 June 2019 (UTC)

193.62.43.121 and 193.62.43.122

please block 193.62.43.121 and 193.62.43.122--DiMon2711 10:45, 4 June 2019 (UTC)

@Ymblanter:--DiMon2711 10:47, 4 June 2019 (UTC)
✓ Done, also protected the page for 2 weeks--Ymblanter (talk) 10:56, 4 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 12:28, 4 June 2019 (UTC)

Joy Huerta (Q20653742)

please semi-protect tgis item forever--DiMon2711 10:49, 4 June 2019 (UTC)

✓ Done for 6 months--Ymblanter (talk) 10:59, 4 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 12:28, 4 June 2019 (UTC)

Please semi-protect "Birsa Munda Airport"

disruptive editing in:

Please see Wikidata:Administrators' noticeboard/Archive/2019/04#Ramesmurmu214 for a previous discussion about the same issue. The disruptive editing still continues, namely the addition of informal erroneous names as official titles and, more problematic, the removal or changing of links to valid articles in sister projects. @Ramjit Tudu: kindly offered to talk with the user, but there has been no change in the behaviour or any attempts to use talkpage discussion as requested multiple times.

Pinging involved users from the previous discussion: @Rameshmurmu899:, @David Biddulph:, @Mahir256: GermanJoe (talk) 08:07, 1 June 2019 (UTC)

47.19.206.66

47.19.206.66 excessive vandalism--DiMon2711 13:29, 4 June 2019 (UTC)

✓ Done for 1 day. Rafael (stanglavine) msg 16:19, 4 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 03:00, 8 June 2019 (UTC)

AD7777GFDU

AD7777GFDU vandalism-only account--DiMon2711 13:47, 4 June 2019 (UTC)

✓ Done indefinite. Rafael (stanglavine) msg 16:19, 4 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 03:00, 8 June 2019 (UTC)

Bouazo Patrick Cyrille

Bouazo Patrick Cyrille vandalism-only account--DiMon2711 13:50, 4 June 2019 (UTC)

 Not done Hmm. They have made one main-space edit, bringing an item into line with the French Wikipedia (and out of line with the English). References are thin. I see no reason not to assume good faith here. Cheers, Bovlb (talk) 16:39, 4 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 03:00, 8 June 2019 (UTC)

Kikilia (Q61870334)

please semi-protect this item--DiMon2711 11:35, 5 June 2019 (UTC)

 Not done These seem to be good faith efforts to add a Russian-language description, unfortunately in the English field. I have added an English label and description, and welcomed the three IP users with a note about using the correct language. Bovlb (talk) 16:00, 5 June 2019 (UTC)
On a related note, I was surprised that I could find no user-talk template for explaining language-specificity in descriptions. It would be helpful to have a clear, multi-lingual explanation for this case. Bovlb (talk) 16:17, 5 June 2019 (UTC)
@Bovlb: Russian is my native language and I assure you that edits by anonims was uncorrect and I would revert edits even if he put it to Russian fields--DiMon2711 18:54, 5 June 2019 (UTC)
@Dimon2711: Well, maybe you're right, although I see a lot of weird "good faith" stuff in the description field. Either way, there's been no IP activity on this item for the last day, so I think protection is moot at this point. You may like to add a Russian description for this item. Cheers, Bovlb (talk) 15:53, 6 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 03:00, 8 June 2019 (UTC)

Edit war

There is an edit war at cattle (Q830) cattle (Q4767951). There is some discussion at talk:Q4767951, but unfortunately edit war is already running.--Jklamo (talk) 15:26, 5 June 2019 (UTC)

✓ Done Hopefully a week of full protection will allow the participants to concentrate on discussion. (Undoubtedly I froze it on the wrong version.) Bovlb (talk) 16:11, 5 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 03:00, 8 June 2019 (UTC)

Request for blocking Hveard1ryder

Hveard1ryder for being a vandalism-user. Thx for notifying me when you've done it. OT38 (talk) 20:21, 5 June 2019 (UTC)

@OT38: ✓ Done. Thank you! --abián 21:15, 5 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 03:00, 8 June 2019 (UTC)

Block needed

Spam or promotional purposes WhoIsClayJames and HTHAZE. Regards, ZI Jony (Talk) 00:17, 7 June 2019 (UTC)

Mahir256 alao 190.46.216.9. Regards, ZI Jony (Talk) 00:23, 7 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 03:00, 8 June 2019 (UTC)

Request page protection for Twice (Q20645861)

Hello, could Twice (Q20645861) please be semi protected? there has been some vandalism going on for 2 days now. Sadly it seems to be becoming a trend to vandalize kpop related pages recently... --Redalert2fan (talk) 09:47, 7 June 2019 (UTC)

✓ Done for one week. Rafael (stanglavine) msg 13:54, 7 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 03:00, 8 June 2019 (UTC)

190.46.137.91

190.46.137.91 Vandalism on pages related to my request above. --Redalert2fan (talk) 16:04, 7 June 2019 (UTC)

 Not done It stoped yesterday, 20:05. Block now is not necessary. Rafael (stanglavine) msg 16:07, 7 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 03:00, 8 June 2019 (UTC)

User Fabiojrsouza

Fabiojrsouza is doing vandalisation and need a block. Looks like other wikis has had problems see pt.wikipedia.org - Salgo60 (talk) 04:58, 2 June 2019 (UTC)

Salgo60I believe you are making a mistake by asking for my blocking. If you check my edit history, you'll find it to be a good record. In addition, if you read carefully the content of the page whose link posted (performing the translation into your language), you will see that the editor who sent the message to me apologized and explained (after I asked him about the reason for the message) that there was a because the warning was intended for another user. Also, I explained my issues in the message you sent me, so there is no need in the blocking, in my opinion and I ask that the wikidata administrators take this into account. (I already know that I do not know English, so I'm using a translator).Fabiojrsouza (talk) 05:14, 2 June 2019 (UTC)
Fabiojrsouza see comment - Salgo60 (talk) 05:19, 2 June 2019 (UTC)

User:Der Wolf im Wald

This user recently changed many data items to use images made by himself. Not all of them are better quality than the existing ones. I do not deny he has many good images but the forcible use of them smells like a conflict of interest. Plus he seems to make money out of incorrect usage of his images by 3rd party users. --Denniss (talk) 15:13, 2 June 2019 (UTC)

Whereas I share your sentiment, you probably should talk to them first.--Ymblanter (talk) 19:45, 3 June 2019 (UTC)

Вандализм

@Ymblanter: 2A00:1370:8131:19B5:6CED:A4DF:F6E2:C31F. Kalendar (talk) 19:37, 10 June 2019 (UTC)

✓ Done--Ymblanter (talk) 19:41, 10 June 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 19:47, 10 June 2019 (UTC)

Вандализм

@Ymblanter: 2.134.198.130. Kalendar (talk) 19:39, 10 June 2019 (UTC)

Защитил страницу--Ymblanter (talk) 19:43, 10 June 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 19:48, 10 June 2019 (UTC)

Q9687

fi:Liikenneonnettomuus should be linked with en:Traffic collision ecc., but the item is protected. -Ochs (talk) 20:16, 10 June 2019 (UTC)

@Ochs: Done - see [1] --DannyS712 (talk) 20:49, 10 June 2019 (UTC)
This section was archived on a request by: DannyS712 (talk) 20:49, 10 June 2019 (UTC)

Вандализм

@Ymblanter: 77.182.217.3 Kalendar (talk) 11:37, 11 June 2019 (UTC)

Слишком поздно--Ymblanter (talk) 11:39, 11 June 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 19:00, 11 June 2019 (UTC)

91.253.222.78

91.253.222.78 vandalism--DiMon2711 09:20, 8 June 2019 (UTC)

This one is probably gone, no evidence this could be a static IP.--Ymblanter (talk) 18:48, 8 June 2019 (UTC)
This section was archived on a request by: DannyS712 (talk) 20:14, 12 June 2019 (UTC)

Feder3234

Feder3234 vandalism-only account--DiMon2711 16:58, 8 June 2019 (UTC)

✓ Done--Ymblanter (talk) 19:00, 8 June 2019 (UTC)
This section was archived on a request by: DannyS712 (talk) 20:14, 12 June 2019 (UTC)

Pastry War (Q856168)

please semi-protect this item for a long time--DiMon2711 05:52, 11 June 2019 (UTC)

✓ DoneSemi-protected for 1 month. Pamputt (talk) 06:41, 11 June 2019 (UTC)
This section was archived on a request by: DannyS712 (talk) 20:14, 12 June 2019 (UTC)

62.219.247.103 declares a lot of people death, please block

Template:Lg is acting strongly against our conduct for living people, as can be seen here. Please block this IP (again). Thanks in advance, RonnieV (talk) 06:52, 11 June 2019 (UTC)

✓ Done by Jasper Deng--Ymblanter (talk) 11:40, 11 June 2019 (UTC)
This section was archived on a request by: DannyS712 (talk) 20:14, 12 June 2019 (UTC)

Pyli (Q15088667)

Once more anonymous users are repeatedly changing the population facts in Pyli (Q15088667), increasing the population in a non-stated number.--Texniths (talk) 16:19, 11 June 2019 (UTC)

✓ Done Semi-protected for 3 months. Rafael (stanglavine) msg 16:51, 11 June 2019 (UTC)
This section was archived on a request by: DannyS712 (talk) 20:14, 12 June 2019 (UTC)

Semi-protection for Q214204

Please semi-protect Eden Hazard (Q214204) - heavy IP vandalism from various IP addresses, (temporarily very) popular theme, living person. --Jklamo (talk) 13:37, 12 June 2019 (UTC)

✓ Done semi-protected for 2 weeks. Rafael (stanglavine) msg 13:57, 12 June 2019 (UTC)
This section was archived on a request by: DannyS712 (talk) 20:14, 12 June 2019 (UTC)

Property ready for approval

Hey. Ive been involved in a property proposal which has been marked as ready for nearly a month. I know there seems to be a bit of a backlog, but would someone be willing to check it over and approve if appropriate? It would be really useful for some data i'm working on. Many thanks! Jason.nlw (talk) 06:14, 5 June 2019 (UTC) WikiProject Properties has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. please look on the properties ready for creation 8 are current backlogs. Regards, ZI Jony (Talk) 02:38, 8 June 2019 (UTC)

Semi-protection

Persistent vandalism from several IPs. Please, semi-protect The Boy in the Striped Pyjamas (Q322156). —Vercelas talk 19:59, 12 June 2019 (UTC)

✓ Done, for a month--Ymblanter (talk) 20:43, 12 June 2019 (UTC)
This section was archived on a request by: DannyS712 (talk) 09:40, 13 June 2019 (UTC)

Вандализм

@Ymblanter: 85.115.248.207. Kalendar (talk) 18:57, 13 June 2019 (UTC)

Блокировать уже поздно, а правку я скрыл.--Ymblanter (talk) 19:04, 13 June 2019 (UTC)
This section was archived on a request by: -- Kalendar (talk) 19:14, 13 June 2019 (UTC)

Mariano (Q568979)

Persistent vandalism from various IPs. It seems that the page needs some protection. — Mike Novikoff 16:55, 7 June 2019 (UTC)

✓ Done for one week. Rafael (stanglavine) msg 17:03, 7 June 2019 (UTC)

---

Ash Crow
Dereckson
Harmonia Amanda
Hsarrazin
Jura
Чаховіч Уладзіслаў
Joxemai
Place Clichy
Branthecan
Azertus
Jon Harald Søby
PKM
Pmt
Sight Contamination
MaksOttoVonStirlitz
BeatrixBelibaste
Moebeus
Dcflyer
Looniverse
Aya Reyad
Infovarius
Tris T7
Klaas 'Z4us' van B. V
Deborahjay
Bruno Biondi
ZI Jony
Laddo
Da Dapper Don
Data Gamer
Luca favorido
The Sir of Data Analytics
Skim
E4024
JhowieNitnek
Envlh
Susanna Giaccai
Epìdosis
Aluxosm
Dnshitobu
Ruky Wunpini
Balû
★Trekker

Notified participants of WikiProject Names

  • It's always possible to add interesting things to these items, but new contributors/IPs don't necessarily figure out how easily and might not actually be interested in that. Still, I'm opposed to general protection of a large number of items. What do other participants of WikiProject Names think?
The suggested edit filter just needs an administrator to set it up. Usually I ask Matěj_Suchánek. I think it could be made to work just for changing labels or descriptions on such items. --- Jura 10:58, 8 June 2019 (UTC)

RfD needs you

Dear fellow administrators, please check Wikidata:Requests for deletions and express your opinions/close some sections. Currently, we have 72 open deletion requests and many of them are open since months. I ask your help especially for two requests asked by subjects via OTRS (just search my name); please help to close them. Thanks in advance! Bencemac (talk) 16:08, 10 June 2019 (UTC)

Homo habilis (Q101373)

please semi-protect this item as excessive vandalism and very popular--DiMon2711 22:34, 11 June 2019 (UTC)

Protection does not seem justified. There were only three vandalism reverts in the past 2 months and there are a lot of other edits too. Therefore this is  Not done for now.--Jasper Deng (talk) 22:55, 11 June 2019 (UTC)

can not add w:zh:Template:Infobox periodic table group/footer into Q15060928

I can not add w:zh:Template:Infobox periodic table group/footer into Q15060928, and w:zh:Template:Infobox periodic table group/header can not add into Q15075201, too. Does I need a higher permission? how to requests for permissions?-- 宇帆（talk·留言·歡迎簽到R₁R₂NKC） 17:12, 11 June 2019 (UTC)

User:A2569875: You couldn't add the first page into Q15060928 because of a filter that prevents adding non-notable subpages. It wasn't the case, though. As of the last item, I didn't find any record on the abuse log. I have added them now. Esteban16 (talk) 21:27, 11 June 2019 (UTC)
ok, thanks. -- 宇帆（talk·留言·歡迎簽到R₁R₂NKC） 03:53, 12 June 2019 (UTC)

please revert and block vandal

User:EylonGvirtzer123 has "killed off" several Israeli politicians in clear vandalism. Please stop him. DGtal (talk) 06:25, 13 June 2019 (UTC)

Mass vandalism across many items (adding date of death to living persons, categorizing animals as human, etc.). They've also vandalized hewiki articles, for which they've been blocked there under several account names. Given the items they've been targeting in wikidata, it's probably 62.219.247.103, which was blocked 2 days ago for the same. Dovno (talk) 06:31, 13 June 2019 (UTC)
@Ymblanter:--DiMon2711 06:42, 13 June 2019 (UTC)
✓ Done with an indef block --MisterSynergy (talk) 07:00, 13 June 2019 (UTC)

77.203.225.184

77.203.225.184 plwase block him (her) for 1 week--DiMon2711 08:24, 13 June 2019 (UTC)

✓ Done--Ymblanter (talk) 19:52, 13 June 2019 (UTC)

Asderser

Asderser vandalism-only account--DiMon2711 10:30, 15 June 2019 (UTC)

✓ Done Esteban16 (talk) 01:52, 16 June 2019 (UTC)

Twice (Q20645861)

please semi-protect this item again--DiMon2711 10:00, 16 June 2019 (UTC)

✓ Done--Ymblanter (talk) 19:34, 16 June 2019 (UTC)

P2264

Can someone do rev deletions and block the ip range. Thanks. --- Jura 16:18, 17 June 2019 (UTC)

✓ Done, thanks. MisterSynergy (talk) 16:28, 17 June 2019 (UTC)

202.67.36.1 and Gimbalpapua

Special:Contributions/202.67.36.1 and Gimbalpapua (possibly the same person, I wouldn’t know) have vandalized given name, male given name, and some other items. —Galaktos (talk) 19:45, 17 June 2019 (UTC)

✓ Done 24h and indefinite, respectively. Rafael (stanglavine) msg 01:57, 18 June 2019 (UTC)

Block of User:StarDust92

Yesterday he made 634 edits and deletions only. I was aware of it because of this one. This user should be blocked immediately and his edits should be reverted if it wasn't done so far. -- MovieFex (talk) 12:43, 11 June 2019 (UTC)

Maybe account has been compromised. I sent a message to the user and I blocked the account as a precaution. Let's wait for the answer. Rafael (stanglavine) msg 17:11, 11 June 2019 (UTC)
Beginner mistakes (justified by email). Unlocked and warning. I think this is all. Rafael (stanglavine) msg 11:00, 12 June 2019 (UTC)
@Stanglavine: He might have edited here the first time with his account but this guy is no beginner (634 edits within 5 hours) and he has been warned in Italian wiki several times. -- MovieFex (talk) 19:50, 12 June 2019 (UTC)
@MovieFex: The editing structure of wikidata makes it easy to do many edits in a short time. He was warned, said he missed, issues were rollbacked and he was unblocked. If he continues with this behavior, he will be blocked again. For now, I think he can learn from the mistakes and have a new chance to edit, so I see no reason to keep blocked. Maybe other editors think differently, but that's my point of view. Rafael (stanglavine) msg 11:46, 13 June 2019 (UTC)

Report vandalism

Special:Contributions/113.0.64.191. --Xiplus (talk) 13:29, 13 June 2019 (UTC)

Thanks, but most likely this is an isolated outburst from a dynamical IP. I think we can wait whether they return--Ymblanter (talk) 19:53, 13 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 14:48, 19 June 2019 (UTC)

Dolyn

Last week several edit wars ([2],[3], [4]) were started by user:Grenck, who took barely part in discussing the relevant issue. Since then he was globally locked for "cross-wiki abuse". Two days after this lock a user:Dolyn became active here, who involved himself in two of these same edit wars, and who also reverts rather than discussing. This user also has ruwiki as his homewiki and also is blocked there. - Brya (talk) 03:22, 14 June 2019 (UTC)

Has been globally locked, as well. - Brya (talk) 03:40, 15 June 2019 (UTC)
Part of a set of (at least) some two dozen accounts at Wikidata. A user obsessed with redirects, and connections. - Brya (talk) 08:29, 15 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 14:48, 19 June 2019 (UTC)

60.153.111.160

60.153.111.160 vandalism --Afaz (talk) 11:33, 14 June 2019 (UTC)

I have warned the IP. Esteban16 (talk) 01:54, 16 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 14:48, 19 June 2019 (UTC)

Vandalism from Special:Contributions/113.0.64.0/24

Two IPs from this range keep changing English descriptions to Chinese and adding nonsense symbols. Please block them for a period of time.--Tigerzeng (talk) 06:10, 15 June 2019 (UTC)

I blocked for 3 days, if they continue with the same action, please report here again. Stryn (talk) 07:35, 15 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 14:48, 19 June 2019 (UTC)

85.31.138.194

Vandalism of the 85.31.138.194. --Vanbasten 23 (talk) 10:43, 17 June 2019 (UTC)

 Not done No more need. Rafael (stanglavine) msg 14:02, 19 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 14:48, 19 June 2019 (UTC)

Dbazesjmirffs

Vandalism at user talk page. This should be the same as the other accounts at that same page - see history. -★- PlyrStar93 →Message me. 🖉← 22:13, 17 June 2019 (UTC)

✓ Checked Accounts globally locked. Rafael (stanglavine) msg 01:49, 18 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 14:48, 19 June 2019 (UTC)

31.200.10.99

31.200.10.99 repeatedly asking user to translate Azerbaijani-related article to another language. A sockpuppet based on fawiki:

I suggest a longer block for months. Hddty. (talk) 06:24, 18 June 2019 (UTC)

✓ Done Blocked the /24 subnet for 6 months, as other IPs in that range besides the one titling this section have displayed the same behavior. (Other administrators are welcome to reduce the range and length of this block if they can find other ways to deal with this spam.) Mahir256 (talk) 12:59, 18 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 14:48, 19 June 2019 (UTC)

Latest Rameshmurmu sock

Rameshmurmu1684 obvious sock, evading global blocks on Rameshmurmu899, Rameshmurmu214, and elsewhere. --David Biddulph (talk) 12:32, 18 June 2019 (UTC)

✓ Done Indef'd, locked the page to only administrators, and blocked two IP ranges with the same pattern of behavior. (Other administrators are welcome to reduce these measures if they find other ways to prevent the recurrence of this vandalism.) Mahir256 (talk) 12:54, 18 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 14:48, 19 June 2019 (UTC)

190.121.10.89

190.121.10.89 vandalism -LiberatorG (talk) 15:19, 18 June 2019 (UTC)

✓ Done, blocked for 31h--Ymblanter (talk) 18:43, 18 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 14:48, 19 June 2019 (UTC)

Update formatter URL of Property:P3136

Hi, all. I would like to request the change of the value of the formatter URL of elCinema person ID (P3136). Current value is:

http://www.elcinema.com/person/$1/

Requested value:

https://elcinema.com/person/$1/ (http --> https and remove www)

This is because (at least from my location) links to elcinema.com using this property are not working. For example, see Ala Mursi (Q12227559), current link using this property http://www.elcinema.com/person/1007377/ is not working while https://elcinema.com/person/1007377/ works perfectly. Also, as you already know, there is an ongoing effort on Wikimedia wikis to use HTTPS links whenever possible, see m:HTTPS. --Meno25 (talk) 17:25, 18 June 2019 (UTC)

This section was archived on a request by: Regards, ZI Jony (Talk) 14:48, 19 June 2019 (UTC)

2601:8C1:4000:1BD:A177:617F:2274:9C66

2601:8C1:4000:1BD:A177:617F:2274:9C66 persistent vandalism after final warning -LiberatorG (talk) 03:25, 19 June 2019 (UTC)

✓ Done --Rschen7754 03:28, 19 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 14:48, 19 June 2019 (UTC)

User talk:CambridgeBayWeather

IP vandalism at this user talk page. — Mike Novikoff 19:50, 19 June 2019 (UTC)

✓ Done, taken care of--Ymblanter (talk) 20:26, 20 June 2019 (UTC)
This section was archived on a request by: — Mike Novikoff 21:20, 20 June 2019 (UTC)

Doggodoggos

This new account appears to be vandalism-only, doesn't it? — Mike Novikoff 00:30, 21 June 2019 (UTC)

Indeffed by Jasper Deng, thanks. — Mike Novikoff 00:50, 21 June 2019 (UTC)
This section was archived on a request by: — Mike Novikoff 00:50, 21 June 2019 (UTC)

Semi-protection for Q2763

Please semi-protect The Holocaust (Q2763) - persistent IP vandalism from various IP addresses, popular and sensitive theme. --Jklamo (talk) 08:05, 21 June 2019 (UTC)

✓ Done --MisterSynergy (talk) 08:14, 21 June 2019 (UTC)

Peter Dinklage (Q310937)

Please semi-protect this item--DiMon2711 09:34, 21 June 2019 (UTC)

200.16.89.251

200.16.89.251 (talk • contribs • logs) - all the edits over the past few weeks seem to be vandalism Andrew Gray (talk) 18:34, 21 June 2019 (UTC)

✓ Done, blocked for a month--Ymblanter (talk) 19:01, 21 June 2019 (UTC)

72.70.37.196

72.70.37.196 user has 2 warnings and continued vandalism. Please block him--DiMon2711 19:11, 21 June 2019 (UTC)

✓ Done, 1 week--Ymblanter (talk) 20:29, 21 June 2019 (UTC)

72.70.37.196

Please block 72.70.37.196. Regards, ZI Jony (Talk) 19:12, 21 June 2019 (UTC)

✓ Done, 1 week--Ymblanter (talk) 20:29, 21 June 2019 (UTC)

200.29.165.239

Please block 200.29.165.239. Regards, ZI Jony (Talk) 19:44, 21 June 2019 (UTC)

✓ Done, blocked for 3 days, though the block will probably have zero effect.--Ymblanter (talk) 20:31, 21 June 2019 (UTC)

Jamieswann

Please block Jamieswann. Regards, ZI Jony (Talk) 19:57, 21 June 2019 (UTC)

✓ Done here and on Commons. Multichill (talk) 23:31, 21 June 2019 (UTC)

About the user Ka3boul ...vrai

Hello,
Could you explain to the user Ka3boul ...vrai (talk • contribs • logs) that it is incorrect to :

  • write Arabic text in French description (like that)
  • write strange descriptions (like that)
  • ignore the messages in their talk page

Regards --NicoScribe (talk) 17:27, 21 June 2019 (UTC)

@Mahir256, NicoScribe: ✓ Done--باسم (talk) 20:24, 21 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 14:16, 22 June 2019 (UTC)

Ngomajorguropsdg2030

Please block Ngomajorguropsdg2030 for vandalism.   — Jeff G. ツ please ping or talk to me 03:06, 22 June 2019 (UTC)

✓ Done Multichill (talk) 09:29, 22 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 14:16, 22 June 2019 (UTC)

Help at Q47485839

Hello. I could use some assistance at Q47485839. The topic has been a problem article in en:wikipedia one year ago. We had conflict of interest, a sock farm, and ultimately the consensus was that the topic was non-notable. Now a similar problem is surfacing on Wikidata. Some IP is generally being hostile and vandalizing my user page. I am not so experienced at Wikidata, so I would really appreciate if somebody could take a look at the item and the behavior or editors around it. Thank you. Ariadacapo (talk) 06:14, 22 June 2019 (UTC)

Convenience link: Q47485839 --DannyS712 (talk) 08:09, 22 June 2019 (UTC)
✓ Done Blocked the ip and protected the item. Multichill (talk) 09:28, 22 June 2019 (UTC)
Thank you! -- Ariadacapo (talk) 16:25, 22 June 2019 (UTC)


Ariadacapo - Wikidata and Wikipedia are two different projects. There's no 'workaround' (to quote you in Q47485839 Discussion) involved in adding new and verified references to substantiate claims for a given attribute. Having a look at the deletion entry and article revision history only reinforces evidence of vandalism demonstrating multiple solid citations - entire paragraphs of references that were targeted and removed - just prior to nominating the articles for deletion.

Fortunately the revision history is mirrored elsewhere on the web, so this can't be completely hidden from plain sight. Your targeting of independent references demonstrates rampant vandalism, both now and when these references were removed prior to opening the discussion. The same goes for the associated organizations, which were likewise targeted with entire paragraphs of references removed in one fell swoop. Deleted references below Bobof2000 (talk) 19:22, 22 June 2019 (UTC)


Deleted references

Print Biographies

Press and Awards

Film Documentaries

External links

Association of Spaceflight Professsionals

An entire paragraph of references removed just prior to deletion discussion:

The organization has been featured in Nature,[1][2] Discover,[3][4] Time Magazine,[5] Popular Science,[6] New Scientist,[7][8] Aviation Week and Space Technology,[9] Space.com,[10], Discovery News,[11], the Sydney Morning Herald,[12] KurzweilAI,[13] PCMag,[14] Digital Trends,[15] in books on next-generation technologies and the emerging spaceflight industry,[16][17][18][19] in radio interviews on the future of spaceflight[20][21] including The Space Show[22][23][24] and NPR Morning Edition,[25] and received extensive international press coverage following the announcement of its first funded flight contract.[26][10][11][5][6][27][12][25] The corps publishes its own newsletter featuring in-depth interviews with NASA astronauts and prominent spaceflight industry insiders.[28][29][30][31][32][33][34]
Deleted references
  1. ↑ "Astronauts for Hire featured in the journal Nature," accessed December 27, 2011.
  2. ↑ "Commercial space flight: Scientists in space." Katharine Sanderson. Nature 476, 477–478 (01 August 2011).
  3. ↑ "Astronauts for Hire in Discover Magazine," July 2011. Accessed December 27, 2011.
  4. ↑ "Big Idea: We're Looking for a Few Good Astronauts." Discover Magazine. Andrew Grant. Tuesday, July 19, 2011.
  5. ↑ 5.0 5.1 "One Giant Leap For Mankind: First Beer Brewed For Space," Time Magazine, by Josh Sanburn. September 28, 2010.
  6. ↑ 6.0 6.1 "First Beer Brewed For Drinking in Space Will Undergo Testing in Low-Gravity Pub," Popular Science, by Julie Beck. Sept 30, 2010.
  7. ↑ "Astronauts for Hire Member featured in New Scientist Magazine" accessed December 27, 2011.
  8. ↑ "Aiming for the stars." Becky Oskin. New Scientist 2841, November 30, 2011.
  9. ↑ "Jumping-Off Point" originally "Space Startups Have a Head of Steam." Aviation Week & Space Technology, by Frank Morring, Oct 3, 2011.
  10. ↑ 10.0 10.1 "Space Beer Headed for Zero Gravity Bar," SPACE.com, by Denise Chow (reprinted by MSNBC). September 27, 2010.
  11. ↑ 11.0 11.1 "On Tap: Space Beer Testing," Discovery News, by Irene Klotz. September 28, 2010.
  12. ↑ 12.0 12.1 "Beam me up Shhhcotty ... the Aussie space beer with zero gravity." Sydney Morning Herald, by Asher Moses. Oct 1,2010.
  13. ↑ Astronaut scientists for hire open new research frontier in space Kurzweil, Ray (March 11,2011) Kurzweil Artificial Intelligence Network
  14. ↑ NASA, Astronauts for Hire Team Up for Recruitment Webinar. Poeter, Damon (09 Dec 2011).
  15. ↑ "NASA vs. the free market: Which is better for American space dominance?", "Digital Trends.com," accessed August 28, 2016.
  16. ↑ Flat World Navigation: Collaboration and Networking in the Global Digital Economy. McDonald, Kim Chandler. Kogan Page Publishers. IABN: 9780749473945.
  17. ↑ Astronauts For Hire: The Emergence of a Commercial Astronaut Corps. Seedhouse, Erik. 2012. Springer, Boston, Springer Praxis Books, pp. 29–41]
  18. ↑ Suborbital. Seedhouse, Erik. 2014. Springer, Boston. Springer Praxis Books.
  19. ↑ Emerging Space Markets. Tkatchova, Stella (2018). Springer Praxis Books.
  20. ↑ State of the Union: Live two-hour radio interview with NASA-trained quantum astronaut Christopher Altman Quantum Astronaut: Coeherence and Quantum Technology.
  21. ↑ State of the Future | Live two-hour radio interview with NASA-trained Quantum Astronaut Christopher Altman. Dr Future Show.
  22. ↑ The Space Show: Dr Jason Reimuller. Multiple featured broadcasts.
  23. ↑ The Space Show: Brian Shiro. Multiple featured broadcasts.
  24. ↑ The Space Show: Dr Erik Seedhouse. Multiple featured broadcasts.
  25. ↑ 25.0 25.1 "Down-Under Brewers Work On Space Beer," NPR Morning Edition, host Steve Inskeep. Oct 1, 2010.
  26. ↑ "Press Release:Astronauts4Hire selected for Historic Microgravity Research Flight", "Astronauts for Hire Website", accessed December 19, 2010.
  27. ↑ "Space Tourists Will Get Their Own Special Space Beer," Discover Magazine, by Jennifer Welsh (reprinted by CBS News). Sept 30, 2010.
  28. ↑ A4H Newsletter Issue 1, Jan 2012. A4H Members Complete Suborbital Scientist Training.
  29. ↑ The A4H Newsletter Issue 2, Second quarter 2012. A4H makes High-Impact presence at Suborbital Research Conference.
  30. ↑ The A4H Newsletter Issue 3, Third quarter 2012. A4H Completes Second Microgravity Research Job.
  31. ↑ The A4H Newsletter Issue 4, Spring 2013. A4H, The Video: Venturing Ahead to Commercial Spaceflight.
  32. ↑ The A4H Newsletter Issue 5, Fall 2013. Cloud Gazing from Suborbital Space. A4H Member Leads Upper Atmosphere Experiment.
  33. ↑ The A4H Newsletter Issue 6, Summer 2014. Space Oddities: How Bacteria’s Strange Behavior in Space Can Benefit Humanity.
  34. ↑ The A4H Newsletter Issue 7, Fall 2015. Alive and Well in Space: FAA’s Dr. Melchor Antuñano on Medicine and Commercial Space

Tau Zero Foundation

An entire paragraph of references removed just prior to deletion discussion:

The foundation has been covered in press and publications including The New York Times,[1] Scientific American[2], Discover Magazine,[3] ABC News,[4] NBC News,[5] Fortune,[6] Forbes,[7][8][9][10][11] The Space Show,[12][13] Phys.org,[14] Centauri Dreams,[15] Seeker.com,[16] Popular Science,[17] Space.com,[18][19][20][21][22][23][24][25] Jezebel.com,[26] BigThink,[27] Futurism,[28][29] Next Big Future,[30][31][32] h+ Magazine,[33] Wired,[34] The Guardian,[35] China Daily,[36] Slate[37] and Spiegel.[38]
Deleted references
  1. ↑ Overbyte, Dennis. “Offering Funds, U.S. Agency Dreams of Sending Humans to Stars”. nytimes.com 11 Aug 2011. New York Times.
  2. ↑ Apert, Mark. Warp Drive Research Key to Interstellar Travel. scientificamerican.com 23 Apr 2014. Scientific American.
  3. ↑ Where's My Warp Drive? | DiscoverMagazine.com
  4. ↑ Interstellar travel and the asteroid mining entrepreneurs
  5. ↑ NASA's Warp Drive? Starship Enterprise Makes a Virtual Splash - NBC News
  6. ↑ Cool Technologies to Look Forward to After VR
  7. ↑ How NASA Might Push Aerospace's Next Big Propulsion Breakthrough
  8. ↑ Lessons On Designing An Interstellar Probe
  9. ↑ Interstellar Defense Network Might Avert Real-Life 'Independence Day'
  10. ↑ Leaving Earth: Former NASA Rocket Scientist On The Politics Of Going Interstellar
  11. ↑ Seven Sci-Fi Scenarios For Interstellar Space Travel That Could Happen In This Century
  12. ↑ This Week On The Space Show | International Space Fellowship
  13. ↑ Here Is the Future of Interstellar Spacecraft
  14. ↑ Project Lyra, a mission to chase down that interstellar asteroid
  15. ↑ NASA Grant Award to Tau Zero Foundation
  16. ↑ Sizing Up the Daedalus Interstellar Spacecraft: Slide Show
  17. ↑ We Won't Have Enough Power For Interstellar Travel Until At Least 2211, According to New Calculations
  18. ↑ David, Leonard. “Futuristic Interstellar Space Probe Idea Revisited” space.com. 7 May 2010. Space.
  19. ↑ Does Humanity's Destiny Lie in Interstellar Space Travel? (Op-Ed)
  20. ↑ Incredible Technology: How to Make Interstellar Spaceflight a Reality
  21. ↑ Lasers Could Blast Tiny Spacecraft to the Stars
  22. ↑ NASA's 100-Year Starship Project Sets Sights on Interstellar Travel
  23. ↑ Boldly Go? Can Humanity Afford ‘Star Trek’-Like Space Exploration?
  24. ↑ Chasing Wormholes: The Hunt for Tunnels in Space-Time
  25. ↑ Futuristic Interstellar Space Probe Idea Revisited
  26. ↑ Aliens Real*
  27. ↑ Project Icarus: An Interstellar Mission
  28. ↑ A Quick Rundown of the Alcubierre "Warp Drive"
  29. ↑ What Is the Alcubierre "Warp" Drive?
  30. ↑ Space Experts Review EMDrive and give recommendations at Centauri Dreams | NextBigFuture.com
  31. ↑ Foxconn heading to nearly fully automated factories | NextBigFuture.com
  32. ↑ Icarus Interstellar has the X-Physics Propulsion & Power Project (XP4) and Mark Rademaker's visuals of based on the technical work of Sonny White | NextBigFuture.com
  33. ↑ All About Space Travel, Time Travel, Quantum Tunneling & Zero-G Sex - h+
  34. ↑ New Book: Warp Speed, Maybe
  35. ↑ As we begin to think of exoplanets as real worlds we could visit, we will want to go | Sarah Scoles
  36. ↑ Next stop, Alpha Centauri|Sunday Life|chinadaily.com.cn
  37. ↑ Slate: The 40-Year Itch
  38. ↑ Interstellare Reise: Pentagon plant
Ah, this is exactly what I was talking about. Someone taking their pet topics to Wikidata after they were not kept on Wikipedia. Ariadacapo (talk) 20:18, 22 June 2019 (UTC)

Merge

Please merge Emmanuel Théaulon (Q64777242) with Emmanuel Théaulon (Q2733401). This is a duplicate. 86.227.91.237 19:57, 22 June 2019 (UTC)

✓ Done --DannyS712 (talk) 20:00, 22 June 2019 (UTC)
Thank you! 86.227.91.237 20:08, 22 June 2019 (UTC)

Edoderoobot edit rate

https://www.wikidata.org/wiki/User:Edoderoobot currently edits with speed of 230+ edits/minute. Can anything be done about this? Smalyshev (WMF) (talk) 18:00, 14 June 2019 (UTC)

Maxlag is fine. Does this bot in particular create strain somewhere else, e.g. at the WDQS updates? If so, I would stop the bot. —MisterSynergy (talk) 18:05, 14 June 2019 (UTC)
Yes, it does create strain. If it's possible to reduce the edit rate, it'd be fine. Smalyshev (WMF) (talk) 18:54, 14 June 2019 (UTC)
  • As it's probably one of the most useful bots around, I wonder why even this one couldn't operate. Are Wikidata capacities so much strained? --- Jura 18:09, 14 June 2019 (UTC)
It could operate, but can it operate not at hundreds of edits per minute? Smalyshev (WMF) (talk) 18:54, 14 June 2019 (UTC)
Looking at the stats for descriptions in "nl", it still has some 20,000,000 edits to do: User:Pasleim/Language statistics for items.
At a rate of 200 per minutes, that would still be >2 months non-stop. --- Jura 19:12, 14 June 2019 (UTC)
Descriptions of limited quality. --Succu (talk) 19:17, 14 June 2019 (UTC)
  • Personally, I find them useful despite being in Dutch. Imagine people trying to type the same on a mobile phone instead. --- Jura 19:24, 14 June 2019 (UTC)
We all wish to have more edit capacities, but we do not have them now and we thus need to make sure that existing server power is available to all users. High WDQS lags as we experience right now (~5 hrs) lead to followup problems which we want to avoid. I thus blocked the bot as an emergency measure, and explicitly not due to a policy violation; they can continue (at a lower rate such as ~60/min while WDQS lag is high) as soon as the operator shows up. —MisterSynergy (talk) 19:35, 14 June 2019 (UTC)
What is wrong with Dutch, and what is wrong with the quality? Edoderoo (talk) 19:44, 14 June 2019 (UTC)
An old one. Normally future bot actions should not override existing labels and/or descriptions. Hence "updates" become more complicate. In my opinion bots should check their actions against at least one secondary source. Only my POV. --Succu (talk) 21:13, 14 June 2019 (UTC)
My bot is using all the available info on the items, which is on this run often only two properties (plus the same simple description in English). That you want a secondary source for my descriptions is for your account. BTW, I checked earlier tonight what your bot is adding (because of the quality complaint). Didn't see a lot of meaning to adding FishBase as a source for the FishBase-ID myself, and don't see the secondary-ness in that either. But now I learned that the rules seems to be tighter for me then for yourself. All animals are equal ... but ... the Dutch animals should shut the .... up, that's what is left on my mind after tonight. If I was being paid for this job this would be the day I would resign. Edoderoo (talk) 22:45, 14 June 2019 (UTC)

@Smalyshev (WMF): can you please push phab:T221774 a little? That should add the WDQS lag to the maxlag parameter, thus all bots which respect the bot policy would automatically slow down as soon as the Query Servers are overloaded. It would be easier to block users then, as there would be a clear policy violation. Many bot operators do not know about the WDQS lag problem. —MisterSynergy (talk) 19:39, 14 June 2019 (UTC)

The question of scalability of Wikidata is really the subject here. The bot run by Edo has been running for forever and its value should not be considered because it is beside the point. Wikidata is increasingly popular, there have been changes that impact queries negatively and even that is beside the point. The question is are we able to double, triple the amount of edits and the amount of queries and in what timeframe. What if that happens in half the time expected? Scientists are taking notice of Wikidata and they DO want their papers included. Are we ready for that. The notion that it is not in the budget is stupid given that this could be foreseen. Given how our income exceeds our expenses, there is room for a solution that will take a serious investment. THAT is appropriate given what we aim to be about. Thanks, GerardM (talk) 08:50, 16 June 2019 (UTC)

Is anybody aware of a previous discussion about

I feel hard-coded standard descriptions are very bad design. --Marsupium (talk) 16:28, 21 June 2019 (UTC)

The design currently is: users edit a manual description in their language and after that the description is shown in the mobile app and the description is shown in the search results on xx-wiki. The AutoDesc.js is not doing that, is it? Edoderoo (talk) 16:58, 21 June 2019 (UTC)
@Edoderoo: Yes, I think you are right that, at the moment, hard-coded descriptions are the only working ones in most contexts. I'm curious if there has been any discussion to change that, that's why I was asking. --Marsupium (talk) 19:29, 22 June 2019 (UTC)
To be honest, I'm more concerned about the silly datamodel of Wikipedia. I understand how the design flaws are there for historical reasons, but especially the missing link red links to Wikidata (read: red links link to a title, and no one knows what will appear under that title later on) are a serious source for errors. Edoderoo (talk) 19:34, 22 June 2019 (UTC)
Agree, this seems to be another independent problem tho. Just a note: There is en:Template:Interlanguage link#Link to Reasonator and Wikidata which you probably know anyway, and it's not much used I think. --Marsupium (talk) 20:57, 22 June 2019 (UTC)
It is hard for a template to know if a subject is notable enough for an article. Where I am active, those are the only red links accepted. But I wonder another thing. If I see an article being deleted on xx-wiki. Can I in any simple way see which item it used to be connected to? Sextvå.tvånoll.ettsjunoll.sjufyra (talk) 06:34, 24 June 2019 (UTC)
This follow-up discussion does not require admin attention. I thus recommend to move all comments starting at Marsupium's contribution of June 21 to Wikidata:Project chat. --MisterSynergy (talk) 06:54, 24 June 2019 (UTC)

Deletion of a picture

User Nicola is deleting a picture here because she asked for speedy deletion on commons (without any good reason but her own teste). I reverted this as vandalism and she re-reverted[5]. Please stop this behavior. --Mirer (talk) 17:20, 24 June 2019 (UTC)

Nothing to do, as the image in question was deleted at Commons meanwhile. Please ping @Nicola here while reporting her on this page. —MisterSynergy (talk) 17:55, 24 June 2019 (UTC)

Forbidden from Wikidata query script

Apologies if this is not the right place for this. I have been running a script that requests properties from an entity, one at a time. There are 1.7M of them in the queue. I've processed 171641 of them so far. However, the other day I discovered that my script, and other similar scripts, are returning 403 Forbidden. Did I exceed a rate limit? I haven't been able to find any published limits except in the Mediawiki etiquette guide (which indicates I'd be fine). As I said, the requests were not concurrent, they processed at maybe a few per second. They were from this same IP, 163.182.128.18. Thanks for any insights!

Probably a recent (unannounced) enforcement of WDQS Query limits. --Succu (talk) 19:19, 19 June 2019 (UTC)

Sockpuppet investigation: single-purpose account Juanriselsid

Antecedents: On March 6 Montserrat del Toro López testified as a witness in an important trial in Spain; the same day she suffered harassment on social networks by opponents to her testimony. The harassment included the publication on Twitter of her postal address and other personal dates, including a picture of her. Someone created a single-purpose account named Juanriselsid, uploaded that picture to Wikimedia Commons and linked it to the Wikidata profile of Montserrat del Toro López, so that it appeared at the article about her in Catalan Wikipedia. Shortly after, the image was deleted because the license was under suspicion. The witness MDTL denounced the harassment suffered in the social networks and a court investigates it.(1) (2)

Current situation: A month ago the user Daaioo removed all the information from the article in Catalan Wikipedia referring to the harassment in social networks suffered by MTDL and to the publication of her picture in WP:CA. He and I entered into a war of editions about the relevancy of these informations, and finally he achieved from an administrator to block the edition of the article for three months, so that currently it does not show any information about the facts. I suspect that Daaioo created the sock-puppet Juanriselsid. If this is true, Daaioo would have committed two infractions to Wikipedia rules: 1) to create a sockpuppet user to publish a picture in order to cause moral damage to a person; and 2) to edit Catalan Wikipedia removing the information about the publication of the picture, not for editorial reasons, but for hiding his involvement in the harassment. I have asked him twice about it but he refuses to answer the question.

Request: I request a checkuser to say if the user Daaioo created the single-purpose sockpuppet account Juanriselsaid. Thank you. --Pompilos (talk) 21:21, 19 June 2019 (UTC)

We do not have local checkusers. You would need to either ask a steward or wait until one shows up here, we have quite a few of them who are also active on Wikidata.--Ymblanter (talk) 20:28, 20 June 2019 (UTC)
Stewards conventionally do not run CheckUser on their own home wiki, even if it doesn't have local CheckUsers, unless they are themselves appointed to that role. Thus @Pompilos: please go to m:SRCU to request CheckUser.--Jasper Deng (talk) 20:29, 20 June 2019 (UTC)
@Ymblanter: @Jasper Deng: It is my first checkuser request. Ill ask it at m:SRCU. Thank you very much for your help. --Pompilos (talk) 20:51, 20 June 2019 (UTC)

User:LennBr

Give this guy a break to get familar with merging policies. He wants to merge disambiguation pages with different disambiguation, e.g. [6]. And revert his changes. -- MovieFex (talk) 15:34, 21 June 2019 (UTC)
@MovieFex: I was trying to connect a german-disambiguation that highlights the same topic as the heat-wave-disambiguation. Altough I understand the point MovieFex is trying to make, the argument, the spelling must be same, in order to connect wikipedia-sites from different languages, is absurd. --LennBr (talk) 15:45, 21 June 2019 (UTC)
@Admin: I try to discuss this with the person itself, because in this case - its obvious that we both have a point. It is a case-to-case decision how to merge sites from wiki-sections. As sometimes - in this case - the german section has two disambiguation-pages (for example: one with the exact same spelling, and one translated) that highlights the same topics, as one english-disambiguation-page.--LennBr (talk) 16:06, 21 June 2019 (UTC)

Disambiguation , Begriffsklärung (in German) and so on, this always means the same. This guy merges items with similar meanings or translations, and this is wrong. So his edits have to be reverted and give him a break, to get familar with the rules and policies. -- MovieFex (talk) 16:27, 21 June 2019 (UTC)

Вандализм

@Ymblanter: 176.122.61.89 (+подан запрос на вандализм в РуВики). Kalendar (talk) 18:42, 21 June 2019 (UTC)

Уже поздно, скорее всего, динамический айпи.--Ymblanter (talk) 19:02, 21 June 2019 (UTC)

Block 32.212.85.152

Hello,
Could you block 32.212.85.152, who is vandalizing Genevieve Padalecki (Q242647) since 21 November 2018, after warnings on their talk page?
Regards --NicoScribe (talk) 17:19, 22 June 2019 (UTC)

✓ Done seems to be going on for quite some time so a long block of 6 months. Multichill (talk) 20:38, 22 June 2019 (UTC)

Sock of long-term abuse いせちか again

Block needed. Page protections may be considered if appropriate, since this editor tends to repeatedly vandalize the same pages. -★- PlyrStar93 →Message me. 🖉← 14:09, 25 June 2019 (UTC)

✓ Done--Ymblanter (talk) 20:17, 25 June 2019 (UTC)

block needed

82.47.146.237 (talk • contribs • logs) - all edits are vandalism to item descriptions, a wave in March/April and now started up again Andrew Gray (talk) 19:21, 26 June 2019 (UTC)

✓ Done —MisterSynergy (talk) 19:32, 26 June 2019 (UTC)

Q19917979

Vandalism by 85.140.0.0/15. Хоббит (talk) 19:39, 26 June 2019 (UTC)

✓ Done, protected for a week--Ymblanter (talk) 20:31, 26 June 2019 (UTC)

BergerTeam

Please block BergerTeam, promotion only. Regards, ZI Jony (Talk) 17:37, 22 June 2019 (UTC)

 Not done @ZI Jony: you didn't even leave the user a message explaining what Wikidata is about. Please do that first and if that doesn't work, come back here. Multichill (talk) 20:40, 22 June 2019 (UTC)
At least we know from 17 references Q64768550 = human (Q5). Funny: Q64769819 --Succu (talk) 20:59, 22 June 2019 (UTC) PS: @BergerTeam: --Succu (talk) 21:34, 22 June 2019 (UTC)
Only promotion Q64772291 - @Multichill. --Succu (talk) 21:39, 22 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 10:16, 28 June 2019 (UTC)

anon user making a lot of computer device edits

I just ran across 2620:0:1000:3216:5413:4AF0:7532:8655 who has been making over 1000 edits this past month mostly in the area of computer peripheral equipment. Some of them look ok, but I had to revert a few I noticed. A lot of the edits are flagged in red by ORES (for whatever that's worth). Can we engage somebody with some expertise in this topic to review this anon editor? This seems like a lot of work to be done without creating an account... ArthurPSmith (talk) 16:53, 25 June 2019 (UTC)

This IP address is apparently registered to Google, according to [7]. I suggest to welcome them on their talk page, and suggest to create an account as this makes lots of things easier—for them as well as for us. Nobody's going to check 1000+ edits… —MisterSynergy (talk) 18:09, 25 June 2019 (UTC)
Ok, added a note. The reverts I did were probably from a simple misunderstanding, the other things I looked at seemed fine to me. ArthurPSmith (talk) 19:47, 25 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 10:16, 28 June 2019 (UTC)

Marion Ruggieri

Hello,

The Marion Ruggieri wikipedia/wikidata page makes a constant mistake : the accent on the "e". It's impossible for two reasons : - her name father have not. - Ruggieri is an italian name, and there is no accent in italian. Could you modify ? thx, MM

I did it. Pamputt (talk) 06:20, 27 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 10:19, 28 June 2019 (UTC)

PC permission

Hello admins, could one of you remove my property creator permission? I have not exercised it recently and I am a bit tired being pinged about such. :) --Izno (talk) 12:27, 27 June 2019 (UTC)

✓ Done. Thanks for your efforts! --MisterSynergy (talk) 12:31, 27 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 10:16, 28 June 2019 (UTC)

Merge

Please merge Edmond Verdier-Havart (Q61410036) with Edmond Verdier-Havart (Q50362205) (duplicate). 92.184.101.146 06:38, 28 June 2019 (UTC).

✓ Done Regards, ZI Jony (Talk) 10:18, 28 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 10:18, 28 June 2019 (UTC)

Merge

Hello. François Dadre (Q64786516) is a duplicate of François Dadre (Q62055518). 86.227.91.237 16:27, 23 June 2019 (UTC)

✓ Redirected. Regards, ZI Jony (Talk) 18:23, 29 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 18:23, 29 June 2019 (UTC)

Bob Singleton

Ever since February there has been an editor who keeps creating duplicate items of Bob Singleton (Q28101393), and some other composers. At the moment I'm counting 50+ items about Bob Singleton, and that doesn't include the ones that have already been merged.

Here are some of the involved IP addresses:

Would it be possible to:

  • delete all duplicated Bob Singletons that only contain labels, descriptions and P31=Q5, and/or
  • prevent creation of new Bob Singletons at least until we have sorted out the ones we already have?

--Shinnin (talk) 20:39, 23 June 2019 (UTC)

I was looking for other IPs with a similar edit pattern and came across 98.18.169.90 and 98.21.18.185. They are related to a globally locked user Maddy3851155. This might be a case of a user evading a block. --Shinnin (talk) 22:30, 23 June 2019 (UTC)

Vandal

Prostoflexer (talk • contribs • logs). 2 edits: 1 in Russian Wikipedia (vandalism - blocked), 1 in Wikidata (vandalism: abuse in Russian description). Should be blocked. --Ksc~ruwiki (talk) 17:16, 29 June 2019 (UTC)

I have warned the user, for one vandalism block is not necessary. Regards, ZI Jony (Talk) 18:19, 29 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 18:19, 29 June 2019 (UTC)

Duplicate

Please merge tribunal de commerce de Nîmes (Q60578258) and tribunal de commerce de Nîmes (Q61199202). 86.227.91.237 20:39, 29 June 2019 (UTC)

✓ Done --DannyS712 (talk) 20:48, 29 June 2019 (UTC)

Remove revision containing IP address

I did two revisions of Q260725 (971340180 and undo of 971340180) while accidentally not being logged in. Since I don't want my IP address to be publicly available, I request those revisions to be removed / linked to my account instead if my ip.

Regards, Jrpie (talk) 00:28, 30 June 2019 (UTC)

@Jrpie: ✓ Done, relevant page for the future. Bencemac (talk) 09:44, 30 June 2019 (UTC)


Thank you for removing the IP-address. However there still is a reference to it in the description of revision 971340589 saying "Undo revision 971340180 by ... "

--Jrpie (talk) 14:12, 30 June 2019 (UTC)

✓ Done Esteban16 (talk) 15:28, 30 June 2019 (UTC)

Protect for Q5666812

Please semi-protect Don Alfonso (Q5666812) again. IPs change birth year many times. --本日晴天 (talk) 08:41, 30 June 2019 (UTC)

✓ Done, plus added to my watchlist. Bencemac (talk) 09:39, 30 June 2019 (UTC)

pushing musical group rouge

Can somebody please look at this edit, https://www.wikidata.org/w/index.php?title=Q181791&diff=prev&oldid=971508327 ?? I cannot restore it. A person User:Paty245 was pushing a brazilian musical group. I restored it as far as possible, but perhaps an administrator can restore everything (and possibly block this user, who also harmed NL Wikipedia). Ellywa (talk) 08:44, 30 June 2019 (UTC)

✓ Done. You have restored the item. The user's target was Rouge (Q63343125). Esteban16 (talk) 15:33, 30 June 2019 (UTC)
thanks, Ellywa (talk) 17:05, 30 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 19:04, 30 June 2019 (UTC)

213.57.158.32

Please block 213.57.158.32. Regards, ZI Jony (Talk) 19:04, 30 June 2019 (UTC)

✓ Done, for a week--Ymblanter (talk) 20:16, 30 June 2019 (UTC)
This section was archived on a request by: Regards, ZI Jony (Talk) 20:54, 30 June 2019 (UTC)

Wikidata:Requests for comment/semi-protection to prevent vandalism on most used Items

This has closed with a "consensus to semi-protect all items used by 500 Wikimedia pages or more". Has this been implemented already, or if not, how do we do it? --Rschen7754 18:27, 24 June 2019 (UTC)

  • I guess we need a team of people doing edits on behalf of users that are now blocked out as well as a convenient way to request them.
@Ivanhercaz, Nicereddy, MarioFinale, Kristbaum, -jem-: as some of the rare supporters of the measure, how do you plan to go about it? --- Jura 18:44, 24 June 2019 (UTC)
  • This is not yet implemented but Abián worked previously on this problem and might have a script which could do it automatically. @Abián: --Pasleim (talk) 11:26, 25 June 2019 (UTC)
    • User:Abián is the only one with an evaluation script to determine items which need protection due to this RfC. I think it would be valuable to share that script, as we can otherwise not really enforce the outcome.
      Jura probably wanted to discuss another problem. Now that much more important items are (going to be) protected, we need a mechanism similar as {{Edit request}} which we effectively use for fully protected pages only. Here, semi-protection is used, thus non-admins would be able to help solving edit requests by non-autoconfirmed users as well. I suggest to make a new template + category for edit requests of semi-protected items. We are going to see whether the community can keep the backlog reasonably small. --MisterSynergy (talk) 11:42, 25 June 2019 (UTC)
    • I sadly don't have a script to find out the number of uses of the Items, but that's something the development team can probably do from time to time. We could write a basic script that periodically reads the list of Items reported by the team and semi-protects them. Pinging Lydia Pintscher in case she can tell us what's in her hands. I also think it's convenient to establish more effective methods so as not to lose feedback on semi-protected Items, so maybe MisterSynergy's proposal could be combined or adapted with something like the inclusion of the same pencil icons that appear on unprotected Items but with the text "feedback" instead of "edit". --abián 15:16, 25 June 2019 (UTC)

Release jobs once performance has normalised

I understand that jobs may be restrained when performance is as abysmal as it increasingly is. However, once performance is normalised jobs like these with the status "running" no longer run they do not get a slice of the action. I do rely on these jobs to finish. They are standard jobs run in a standard environment. There is imho no reason to put them/keep them in limbo.

I have made one observation: it is always the same wdqs004 and wdqs005 that are underperforming.. What is different in these systems? Thanks, GerardM (talk) 04:58, 24 June 2019 (UTC)

Given the lack of responsiveness, I have escalated this issue to the mailing list. Thanks, GerardM (talk) 06:31, 26 June 2019 (UTC)
@GerardM: I don’t understand what this is doing on the administrators’ noticeboard. What do you expect the Wikidata admins to do? They don’t maintain SourceMD, and they don’t maintain the query service either. --Galaktos (talk) 06:51, 26 June 2019 (UTC)
I am given to understand that they put the brakes on jobs. What does not happen is that they release those same jobs at a later, opportune time. I raised it on the chat, then on the administrators' noticeboard and now on the mail. Thanks, GerardM (talk) 08:13, 26 June 2019 (UTC)

Let me give some insight: admins can use "block" and "unblock" here, but that's it. Whether or not a tool/bot continues after unblock, and how exactly this happens depends entirely on the tool. A good tool/bot realizes that it cannot save anymore after the account has been blocked, and reacts appropriately (either "re-try with much lower load until it works again", "stop editing completely", or whatever).
I have to mention that blocks due to server performance reasons happen occasionally, but that is still a rather rare phenomenon. Basically one of the following has to happen:

  • Maxlag parameter is ignored (i.e. a violation of the bot policy); this is barely a problem these days and happens usually when self-written bot frameworks are used that do not implement maxlag properly; a block might come without a warning as this is a clear policy violation
  • Batch results in "bad data", whatever this exactly means; these days this could happen due to outdated query results, i.e. when WDQS lag is high and the tool/bot operator does not take notice of it. I would warn the user before issueing a block, and there usually would be a complaint by at least one other user on this noticeboard.
  • A panicking WMDE or WMF technician asks for the block of a particular user that uses too many server resources and increases server strain thereby. This could sometimes happen accidentally due to a job with special characteristics (for example "editing lots of extraordinarily big items" or "editing lots of items with extraordinarily lots of sitelinks", and so on). Currently there is also the possibility that bot accounts that edit *really fast* (100+ edits per min) while WDQS lag is high which may lead to blocks as not all bot operators are aware of this problem, and bots cannot see it (easily) as well. Non-bots are limited to 90/min anyways and should usually not experience this situation. Whether or not there is a warning depends on the situation entirely.

Also mind that at least the second and third bullet point do not require an explicit policy violation; in those cases, blocks are issued to protect the project from damage, and to make sure that limited server capacities are fairly shared among all users.
All of that is very subjective of course, but I hope it helps a bit. Otherwise feel free to ask... --MisterSynergy (talk) 09:52, 26 June 2019 (UTC)

Well, that does not apply imho. The jobs I run are all the same. Some of them are held some of them don't. The ones that are held, check the time of their last action, do not process do not complete. There is nothing there that has anything to do with the general way of working. The processes involved have been recently tuned and they are an essential part of the processes that enable us to know about science.
What I am looking for is a mechanism where I can release them in the absence of those who put these jobs on hold. Thanks, GerardM (talk) 05:17, 27 June 2019 (UTC)
I am happy to report that a bug has been identified and patched. The SourceMD software is processing again. Thanks, GerardM (talk) 13:10, 28 June 2019 (UTC)

Should we have a Property Creators' noticeboard?

There are currently 68 properties stated as "ready" under Category:Properties ready for creation. I have been doing as many as I can, but it takes me about 10 minutes for each one and I just don't have the time to even keep up with new ones getting added. We have lots of property creators, but I think we need to engage one another better. Some of the ones that are marked as "ready" I'm really not sure on and it would be nice to discuss with other creators what to do. Can we create a "property creators' noticeboard" like this one for admins? Would it be useful? ArthurPSmith (talk) 20:33, 19 June 2019 (UTC)

marked as ready - So what? Most of our external id properties are created "on the fly" without real discussion. --Succu (talk) 20:48, 19 June 2019 (UTC)
That's a good example, that property doesn't look ready to me given the opposing comments that have really not been addressed there. So I think it would be useful for property creators to discuss policy on such things among themselves. I'm not sure how your "without real discussion" relates to this though, but in general that also is a general issue that I think should be discussed among property creators. ArthurPSmith (talk) 13:45, 20 June 2019 (UTC)
  • It might be preferable to create properties directly if you are an administrator or a property creator and you think they are ready for creation (unless you proposed it yourself). Personally, I don't bother re-reviewing proposals when another property creator has done so.
    As it can take me up to an hour to complete a property creation, personally I consider it a waste of time to do so if the property wont be used afterwards. I feel I should have closed the proposal as stale instead.
    If someone plans to use a property that could be created now, feel free to ping me. BTW I usually don't create properties with external-id datatype. For these, you might want to use "described at URL" until someone else creates it. --- Jura 06:17, 20 June 2019 (UTC)
And I'd be interested to hear why it can take up to an hour - that seems excessive but you must be doing something extra there that might be useful for other property creators to know about and do... if we had a place to discuss it amongst ourselves wouldn't that be helpful?? Also of course the issue of usage is a concern. But external-id datatype properties are often heavily used, especially if there is a mix-n-match catalog or bot working on them. ArthurPSmith (talk) 13:47, 20 June 2019 (UTC)
I wonder if we should relax the expectation that the creator does the full initial setup of the property page. It would be much quicker to just judge consensus and click the button. So if the proposers and others are happy to help with the setup, this might ease the backlog. --99of9 (talk) 00:43, 21 June 2019 (UTC)
I'd oppose relaxing expectations. I think we were more relaxed in the past, which resulted to lots of poorly set up property pages. Using elevated rights in practice can sometimes be tedious, but that is not different for other jobs here as well, such as administration. --MisterSynergy (talk) 05:31, 21 June 2019 (UTC)
@MisterSynergy: That makes sense. I did come across a few poor ones while trying to dot the i's and cross the t's for all Australian properties at: Wikidata:WikiProject_Properties/Reports/Country_dashboard. Perhaps we should have a more general cleanup drive? Other countries are welcome to join in the "competition" :). --99of9 (talk) 06:23, 21 June 2019 (UTC)

Personally I think that we have a few too many noticeboards and should get rid of one or two. --Rschen7754 00:45, 21 June 2019 (UTC) WikiProject Properties has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. please look on the properties ready for creation 8 are current backlogs. I'm requesting to all Property Creators to create property's which are ready for creation, if each persons create 2/3 property's then will not be remain to create. Regards, ZI Jony (Talk) 16:56, 28 June 2019 (UTC)

Ok, doing a few now. The real solution would be to have a tool to do this easily, it would be great if someone could make that. − Pintoch (talk) 22:42, 28 June 2019 (UTC)
  • Multiple of the property like the Featured_Biographies_ID one linked above were marked as ready without really being ready. I'm a bit weary about simply calling for creating them without added scrutinity. ChristianKl ❪✉❫ 16:19, 1 July 2019 (UTC)
  • I think that there are a bunch of tasks that are manual that are involved in the property creation process that should be automated and done by bot. "Proposal discussion" should be copied over by a bot and not by a human.
All information that's required for the creation of the constraints should be in the property discussion template and a bot should automatically create the required constraints. Given that constraint are integral part of a property, discussing them in the property discussion would be an improvement on the present process.
The same goes for copying over the examples. It's manual labor that could be done effectively by a bot in 95% of the cases (the other 5% being properties with qualifiers that are more complicated). ChristianKl ❪✉❫ 16:19, 1 July 2019 (UTC)
@ZI Jony: why do you think the property should not be named "announcement date"? Additionally, our property names are generally not capitalized. Creating this with a capitalized name also seems fishy to me. Instead of marking properties like that ready and creating them it would be better to ping the involved people to see whether a consensus on the name can be found. ChristianKl ❪✉❫ 12:04, 3 July 2019 (UTC)
Changed as "announcement date". Regards, ZI Jony (Talk) 13:44, 3 July 2019 (UTC)
Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Administrators%27_noticeboard/Archive/2019/06&oldid=977457872"