Shortcut: WD:AN
Wikidata:Administrators' noticeboard
Administrators' noticeboard This is a noticeboard for matters requiring administrator attention.
|
![]() | If you are requesting the restoration of a deleted item, please be sure to explain how the item meets our notability criteria. If you are claiming that the item "can be described using serious and publicly available references", please list some of those references in your request. |
![]() |
On this page, old discussions are archived. An overview of all archives can be found at this page's archive index. The current archive is located at 2024/09. |
![]() | Attention administrators: This message is appearing because there are more than 100 open requests at Wikidata:Requests for deletions. Please consider helping with the backlog. |
Requests for deletions high ~122 open requests for deletions. |
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)
- Descriptions of limited quality. --Succu (talk) 19:17, 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)
- 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)
- It could operate, but can it operate not at hundreds of edits per minute? Smalyshev (WMF) (talk) 18:54, 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)
- BTW wouldn't User:Marcmiquel's edits on country pages have a larger impact? --- Jura 19:55, 14 June 2019 (UTC)
- As long as Stas (or any other involved WMF/WMDE technician) does not complain, I see no reasons to do anything here. —MisterSynergy (talk) 19:57, 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
- wider use of Magnus’ toollabs:wikidata-todo/autodesc.js/en:MediaWiki:Wdsearch-autodesc.js (it doesn't bloat item size and improvements to the model don't require millions of edits)?
- or discouragement of standard descriptions?
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)
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)
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)
- 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)
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)
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)
- 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)
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)
Erledigt --MisterSynergy (talk) 08:14, 21 June 2019 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. DannyS712 (talk) 23:59, 21 June 2019 (UTC) |
Please semi-protect this item--DiMon2711 09:34, 21 June 2019 (UTC)
Erledigt Multichill (talk) 15:29, 21 June 2019 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. DannyS712 (talk) 23:59, 21 June 2019 (UTC) |
Give this guy a break to get familar with merging policies. He wants to merge disambiguation pages with different disambiguation, e.g. [1]. 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)
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)
- @علاء, باسم: Can you help us out? Mahir256 (talk) 20:00, 21 June 2019 (UTC)
- @Mahir256, NicoScribe:
Erledigt--باسم (talk) 20:24, 21 June 2019 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Regards, ZI Jony (Talk) 14:16, 22 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)
Erledigt, blocked for a month--Ymblanter (talk) 19:01, 21 June 2019 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. DannyS712 (talk) 23:59, 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)
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)
Erledigt, 1 week--Ymblanter (talk) 20:29, 21 June 2019 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. DannyS712 (talk) 00:00, 22 June 2019 (UTC) |
Please block 72.70.37.196. Regards, ZI Jony (Talk) 19:12, 21 June 2019 (UTC)
Erledigt, 1 week--Ymblanter (talk) 20:29, 21 June 2019 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. DannyS712 (talk) 00:00, 22 June 2019 (UTC) |
Please block 200.29.165.239. Regards, ZI Jony (Talk) 19:44, 21 June 2019 (UTC)
Erledigt, blocked for 3 days, though the block will probably have zero effect.--Ymblanter (talk) 20:31, 21 June 2019 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. DannyS712 (talk) 00:00, 22 June 2019 (UTC) |
Please block Jamieswann. Regards, ZI Jony (Talk) 19:57, 21 June 2019 (UTC)
Erledigt here and on Commons. Multichill (talk) 23:31, 21 June 2019 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. DannyS712 (talk) 00:00, 22 June 2019 (UTC) |
Please block Ngomajorguropsdg2030 for vandalism. — Jeff G. ツ please ping or talk to me 03:06, 22 June 2019 (UTC)
Erledigt Multichill (talk) 09:29, 22 June 2019 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. 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)
Erledigt 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)
I'm just a casual observer, but here's my thoughts. If you had done the research I did, you would find, first, that Ariadacapo indicated to make comments on Talk page, but then did not respond to any comments prior to making further changes. The response from that IP address unknown user was definitely inappropriate, however it seemed to be driven by the actions of Ariadacapo because there as no discussion on Ariadacapo's part. Furthermore, Ariadacapo has indicated he's not familiar with the Wikidata project. I wonder why he has admin access in such a case when he's not familiar with how it works. Bobof2000 (talk) 19:22, 22 June 2019 (UTC)
Ariadacapo - Wikidata and Wikipedia are two different projects. There's no 'workaround' 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. Bobof2000 (talk) 19:22, 22 June 2019 (UTC)
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]
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]
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)
BergerTeam
Please block BergerTeam, promotion only. Regards, ZI Jony (Talk) 17:37, 22 June 2019 (UTC)