Steward requests/Miscellaneous

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search
Requests and proposals Steward requests (Miscellaneous) Archives
This page is for Wikimedia wikis having no active administrators. Requests can be made here for specific administrative actions (such as page deletion) to be performed by a steward or global sysop. In other cases:
  • If the wiki does have active administrators, file the request with one of them.
  • If the wiki has an active editor community, any potentially controversial action (deletion of actual content, edit to a protected page, renaming of a protected page, etc.) should receive consensus from the wiki community before being requested here, and a link should be provided to that consensus in the request.
  • For global lock/block requests, file a request at Steward requests/Global.

To add a new request, create a new section header at the bottom of this page (but above the See also section) using the format below:

=== Very brief description of request here ===
{{Status|In progress}}
Give details about your request here. --~~~~

It is helpful if you can provide a link to the wiki (or the specific page on the wiki) in question, either in the header or in the body of your request.

When reporting cross-wiki vandalism, the following template calls can be used to link to a user's contributions across all Wikimedia content wikis (these are for logged in users and non-logged-in users, respectively):

* {{sultool|Username}}

* {{luxotool|IP.address}}

Template {{LockHide}} can also be used in appropriate cases.

To request approval of OAuth consumers please use {{oauthapprequest}} (see the documentation before using).

Old requests are archived by the date of their last comment.

Cross-wiki requests
Meta-Wiki requests


Manual requests[edit]

Please see a list of pages nominated for speedy deletion via {{Delete}} and/or the local equivalent. You can also filter by wikis whose admins are less than X or have not delete since Y.

Copyrighted works on the Esperanto Wikisource[edit]

Status:    On hold

The works of Kazimierz Bein (Kabe) are not yet in public domain. The author died in 1959. The pages should be deleted now and undeleted in 10 years. There is no active community on this wiki and there are no admins.

Pages containing copyrighted material:

Robin van der Vliet (talk) (contribs) 14:11, 31 January 2019 (UTC)

@Robin van der Vliet: As these works have been there for years (2012), they should at least have the semblance of a deletion discussion with whatever community may be there, and for at least a month so allowing suitable opportunity for comment. Though it will be a forlorn hope, please ping the contributor.  — billinghurst sDrewth 15:34, 31 January 2019 (UTC)
I informed the creator of most of those pages here, but I don't really see what we should discuss. The pages constitute a clear copyright violation. Robin van der Vliet (talk) (contribs) 15:42, 31 January 2019 (UTC)
They have been there six years, waiting through a discussion is not problematic. The community should be given the right to have that discussion. It allows a local record to exist for others to see, it educates, it informs and allows a community to be a community. It allows a local permalink to be used on any deletion, and a clear authority for people to act to delete. What is so urgent or imperative that a discussion cannot be held.  — billinghurst sDrewth 23:10, 31 January 2019 (UTC)
Also noting that some of the works have been added by Frglz (talk · contribs), so please ping them in the discussion. Thanks..  — billinghurst sDrewth 23:13, 31 January 2019 (UTC)
I also pinged them in the discussion. For me personally it's not a problem to wait, I am just accustomed to how copyvios work on Commons. When I nominate something there, it gets deleted in an instant without any discussion, that's why I was surprised when you said "at least a month". Robin van der Vliet (talk) (contribs) 02:15, 1 February 2019 (UTC)
I moved the discussion to this page, because there are a lot more copyrighted works stored on the Esperanto Wikisource than I first noticed. I linked all I could find in that new page. Robin van der Vliet (talk) (contribs) 13:34, 2 February 2019 (UTC)
Thanks. Wikisources work differently to Commons, especially in sporadic editing. I am also unsure exactly the copyright rules they apply, it may not be Commons rules. Being pre-1923 works, if eoWS are working only to US copyright alone, they will not be copyright violations. This is why the community conversation should be taking place by those who know the local rules, rather than applying another wiki's rules.  — billinghurst sDrewth 13:40, 2 February 2019 (UTC)
If they require the texts to be PD also in the first publication country, the texts should be moved do Multilingual Wikisource before deletion. Ankry (talk) 14:01, 2 February 2019 (UTC)
  • What is the status of this request? I am ready to import files to oldwikisource, but I will not do that if their deletion is not due or if it is not to be performed soon (to avoid duplication). Ankry (talk) 06:25, 6 May 2019 (UTC)
Esperanto does not have any native country. They will not be copyright violations. --Sharouser (talk) 03:20, 7 December 2019 (UTC)
That's not how copyright works. Vermont (talk) 03:25, 7 December 2019 (UTC)
Because Esperanto does not have any native country, they only require the texts to be PD in the United States --Sharouser (talk) 04:01, 7 December 2019 (UTC)
What language it's in has literally zero effect on whether it's a copyright violation. I could make my own language (or even creative random characters), write something, and if you copy it and put it onwiki it's still a copyright violation. Vermont (talk) 04:25, 7 December 2019 (UTC)
Because this problem happened in a Wikimedia project, It follows Wikimedian policy. --Sharouser (talk) 09:10, 7 December 2019 (UTC)
It is evident that you don't know Wikimedia policy or the legal rules around copyright that we abide by. The three statements you have insofar written are all false, and not based in fact. If your hope was to contribute copyright advice to this discussion, it is unnecessary for you to do so. Vermont (talk) 10:52, 7 December 2019 (UTC)
Would you mind explaining what Wikimedia policy and the legal rules around copyright that we abide by are? Because the rules the English Wikisource and English Wikipedia abide by are that any work PD in the United States is fair game, and I see no reason why the Esperanto Wikisource should be any different.--Prosfilaes (talk) 05:12, 8 December 2019 (UTC)
+1 AFAIK, any extra copyright related requirements are based on local community decision, not on WMF decision. The ToU states that the content declared as PD should be Public Domain under the law of the United States of America as well as the laws of any other countries as required by the specific Project edition. So it is up to the project to establish extra copyright rules. If I am wrong, please point me where the default copyright rules are defined. Ankry (talk) 18:00, 18 January 2020 (UTC)

Further cleanup issues related to the closure and deletion of Bulgarian Wikinews[edit]

@User:George Ho has done a lot of work looking at this, as you will see below. Because of the possibility that some content from here will be incorporated into a different Wikinews project, we are looking to finish cleaning up policy problems before making the content available, and before otherwise (effectively) deleting the wiki. By all means delete the pages that George describes that you think should be deleted. If you think some of the pages should be templated as "possible copyvios" instead, we will make a template available for that purpose. Thank you. StevenJ81 (talk) 13:11, 25 September 2019 (UTC)

It is difficult to check if they are copyvios or not. It is better to have sentence to sentence comparisons. Ruslik (talk) 17:58, 30 September 2019 (UTC)
Post the comparisons on-wiki or off-wiki? George Ho (talk) 18:51, 30 September 2019 (UTC)
On wiki. Ruslik (talk) 19:05, 2 October 2019 (UTC)
How many sentences per article may I sample without risking copyright infringement? –George Ho (talk) 20:19, 2 October 2019 (UTC)
Sampling for this purpose is not a copyvio, especially since you are directly comparing to original source. But I'm thinking this ought to go on a subpage, because it's really going to clutter this page up. @Ruslik0, what do you think? The preceding unsigned comment was added by StevenJ81 (talk • contribs) 18:57, 3 October 2019‎ (UTC)
Yes, subpage is better. Ruslik (talk) 19:07, 4 October 2019 (UTC)
It's been months, Ruslik. Must I still make sentence comparisons? Also, deleting the project was discussed. George Ho (talk) 06:02, 20 March 2020 (UTC)
These requests are moot now, I think. It is better to close them. Ruslik (talk) 20:34, 30 March 2020 (UTC)
What about the likely or most likely cases? George Ho (talk) 23:17, 30 March 2020 (UTC)

Sampling the first bundle... George Ho (talk) 06:34, 12 October 2019 (UTC)

Currently, I'm getting busy with my college work, so I may have to compare other articles at very later time. Seriously, if the stewards won't be able to detect copyvio, why not delete the whole project itself and its content? George Ho (talk) 03:07, 17 November 2019 (UTC)

Possible copyvio content at bg.wikinews[edit]

Status:    In progress

Now that bg.WN is closed/locked and that there are no admins as of date, before transferring remaining content to ru.Wikinews, I would like you to draw attention to the below list of articles that I think are likely copied from third-party sources, like BBC and CNN. The ones that I'm unsure about would be mentioned in separate subsection.

Copied from one of my subpages:

List of articles mentioned in Proposals for closing projects/Deletion of Bulgarian Wikinews:

Most likely

More likely

List of Григор Гачев's (Grigor Gachev's) remaining created articles:

Definitely / Most likely

More likely

Likely

Slightly likely

--George Ho (talk) 01:27, 25 September 2019 (UTC)

More articles seen in another revision:

Definitely / Most likely

More likely

Likely

Slightly likely

--George Ho (talk) 01:50, 26 September 2019 (UTC)

More articles taken from another revision:

Most likely

More likely

Likely

Slightly likely

  • n:bg:Тръмп ще направи опит да купи Гренландия — (detector) most of content looks similar to portions of either mediapool.bg or dnes.bg. The articles were posted on the same day, 19 August 2019. However, bg.wn article was created on 16:47 UTC; the mediapool.bg one was published on 07:28 local time (04:28 UTC), twelve hours prior; dnes.bg one, on 07:40 local time (04:40 UTC). Also, the article summarizes Danish PM's response characterizing Trump's idea of buying Greenland as "шега" (joke). The article didn't say that Danish PM used "joke" or "шега" in quotes; I think the paraphrase was POV, wasn't it?

George Ho (talk) 18:49, 28 September 2019 (UTC)

Almost forgot: the revisions from oldid 23418 to oldid 24555 should be deleted or suppressed from public view because, as noted earlier, there is the comparison table comparing one bg.wn with a BBC article. George Ho (talk) 06:29, 30 September 2019 (UTC)

Hmmm, wouldn't it be sufficient to just delete/blank the table? I'd really prefer to have the history of the village pump readily available if the closing of this project is ever discussed again. I don't think anyone is going to sue WMF (well, at least not anyone reasonable enough) for content that is available only from the edit history and then clearly without an intent to infringe the copyright (in fact, exactly with the intent to stop infringing the copyright).
— Luchesar • T/C 07:00, 30 September 2019 (UTC)

Other bg.wn content (undetermined)[edit]

Status:    In progress

Other articles mentioned at #Possible copyvio content at bg.wikinews I'm certain are likely copyvios. The ones below I'm very unsure about, so I figure that further evaluation is needed. If any one of them is copyvio, it should be deleted. One of previous requests was rejected because, at the time, bg language wasn't understood. I wonder whether the lack of understanding the language would impact this request.

Copied from one of my user subpages:

List of Григор Гачев's (Grigor Gachev's) remaining created articles:

Other articles seen at list of bg.WN articles

--George Ho (talk) 01:27, 25 September 2019 (UTC)

More articles seen in another revision:

George Ho (talk) 01:53, 26 September 2019 (UTC)

More articles taken from another revision:

  • n:bg:Рекордни пожари в Амазония — (detector) Most of one paragraph's content looks similar to some portions of either nova.bg article or the clubz.bg one. Some other areas of the bg.wn article look similar to portions of the news.bg article. Just one paragraph of the detailed bg.wn article wouldn't reach to the level of huge copyvio, but it needs rewrite. I couldn't determine whether the rest of the article infringes other sources.
    In my view this content is OK (no copyvio) --Ket (talk) 11:38, 2 October 2019 (UTC) Copied from this revision. --George Ho (talk) 00:21, 3 October 2019 (UTC)
  • n:bg:Иран задържа британски танкер (created 21 July) — the detector partially matched one paragraph and another sentence with partial content of the news.bg article (published 20 July). However, I'm not confident that just one paragraph would make the case big enough to be copyvio, but I could be wrong.
    IMHO this isn't indeed problematic in terms of copyright. That being said, I also see the typical Stanqo's style of presenting such events in a biased way—the article covers almost exclusively the Iranian POV. — Luchesar • T/C 14:33, 4 October 2019 (UTC)
  • n:bg:Почина Фидел Кастро (created 27 Nov 2016) — I can't tell whether the any of the first three paragraphs of the article were taken from the BBC article (pub. 26 Nov). However, the expression looks to brief to tell. The second paragraph erroneously claimed that Fidel Castro died at 19:00 unspecified time zone (02:00 EET / 00:00 UTC). However, according to BBC article, Fidel's brother Raul verified that Fidel's time of death was 22:29 local time (03:29 GMT/UTC). I don't know where the last paragraph originated. However, more importantly, would ru.wn accept the article containing such error about Fidel's time of death? Should it be transferred there?
  • n:bg:Цунами по крайбрежието на Япония: огромни разрушения — (detector) — looks to be translated from article by VOA Russian (old revision). VOA content has been released into public domain right away. If that's okay, then I guess my copyvio concerns would be invalid. However, VOA's content has been questioned, and VOA is deemed by some as "propaganda". If the bg.wn article didn't translate from VOA Russian, then where else?
    I agree that there is text translated from Russian based on mistakes in the text like "нефтепрерабатващия" and "източното крайбережие на Японии" - it should be "нефтопреработвателния" and "източното крайбрежие на Япония" respectively --Ket (talk) 11:49, 2 October 2019 (UTC) Copied from this revision. --George Ho (talk) 00:21, 3 October 2019 (UTC)

George Ho (talk) 18:49, 28 September 2019 (UTC)

License compatibility of one bg.wn article[edit]

Status:    In progress

The article n:bg:Научен пробив: земни скали от най-древната епоха могат да се намерят на Луната! was copied from cosmos.1.bg article, which is licensed under CC-BY-SA 2.5, though somehow the link directs to the CC-BY 2.5 license. As of now, the link to the original source is down, but I hope it works again later as it did hours ago. Just in case, here's the archive link from Wayback Machine. The CC-BY-SA wouldn't be one-way compatible with CC-BY, especially per n:en:Wikinews:Copyright. If importing the CC-BY-SA into Wikinews is not legitimate, then the bg.wn copy should be deleted. George Ho (talk) 06:36, 25 September 2019 (UTC)

First of all, IANAL. But bgwn is not unique in having content with different license than the default CC BY-SA 2.5. For instance there is such content on ruwn and having that in mind we had such content created on ukwn too (I am a part of the latter community thus "we"). In my opinion it should be fine as long as the license is explicitly mentioned. That is done by explicit "additional terms may apply" in the footer and a license template in the article. That being said, again, IANAL. --Base (talk) 19:58, 29 September 2019 (UTC)
@Base, George Ho, and Iliev: IANAL either. But if what you say is true, then all we need to do is to change the license template at the bottom of that page to reflect CC-BY-SA 2.5. (Original is back up here, and I can confirm it says CC-BY-SA 2.5, but that the link points to CC-BY 2.5 [BG].) Iliev, please confirm what I am copy-pasting from Creative Commons's website:
StevenJ81 (talk) 13:51, 4 October 2019 (UTC)
StevenJ81, probably „Криейтив Комънс – Признание-Споделяне на споделеното 2.5 България“ to be more precise—but I'm concerned exactly about this confusion between the text and the link. There are two CC BY-SA 2.5 licenses relevant to Bulgaria: an unported and a localized one. The link in cosmos.1.bg is to the localized license (but, indeed, to CC BY 2.5 BG, not to BY-SA as expected), while the text of the link itself seems to refer to the unported “CC BY-SA 2.5” (otherwise it should've been “CC BY-SA 2.5 BG”). So, if we decide that the text has precedence over the link (it makes sense to me, though, yeah, IANAL as well), we should probably change the template this way:
— Luchesar • T/C 14:15, 4 October 2019 (UTC)
So long as the source is CCBY or CCBYSA it should be acceptable on wiki projects, isn't it?13019891ahs (talk) 13:43, 15 October 2019 (UTC)

Hijacked domain and predatory spam[edit]

Status:    In progress




I came across repeated additions of blackwell-synergy.com on a small wiki only to find out that this domain has more than 5000 occurrences x-wiki. It was at one point in time a reputable journal which I believe merged with en:Wiley (publisher), however the domain was sniped and it is now a host of predatory supplement spam/scams. I don't know a reasonable way to solve this problem aside from someone creating a bot task xwiki to replace the url with an archived version (if possible) or remove it entirely. I'm not sure what protocol is here because I've never seen a domain with this heavy use hijacked. Apologies if this isn't the appropriate place to ask this, I honestly am not even sure where to begin. --Praxidicae (talk) 16:41, 22 October 2019 (UTC)

  • Cyberpower678, could you tell us if perhaps InternetArchiveBot can be of any help here? --Base (talk) 01:38, 23 October 2019 (UTC)
  • Isn't there some sort of way you can use w:en:WP:AWB to do this? --Rschen7754 05:53, 23 October 2019 (UTC)
I've been unable to find a way to use AWB on more than one project simultaneously, but I suppose we could do runs on individual projects. Vermont (talk) 10:12, 23 October 2019 (UTC)
  • In the meanwhile, it's fine to blacklist this domain globally: the publisher never needs to be linked. On the English Wikipedia, if you use citation bot, the redundant URL is automatically removed; elsewhere, where the URL is not in a template or the bot is not available, using Citoid/VisualEditor with the DOI will usually produce the correct result. InternetArchiveBot is probably the most global of the relevant bots but may need some manual tweaking for the URLs outside templates perhaps. Nemo 06:42, 23 October 2019 (UTC)
  • Started cleaning el.wiki. I'll prefer to do some by hand as in many cases I think it would be prefered to recreate the link (almost certainly in a cite template) using doi and a refgenerator as http://reftag.appspot.com/doiweb.py but this doesn't mean I think a bot solution won't be a good solution for our wikis.—Ah3kal (talk) 13:15, 23 October 2019 (UTC)
  • Another problem is that the xwiki link tool is limited to 40 projects (top projects) and many of the smaller wikis that won't appear there and COIBot link report maxes out. Beetstra is there a way we can get a full report for all projects? Praxidicae (talk) 15:49, 23 October 2019 (UTC)
    • @Praxidicae: Full report is not really going to help you, you just have to find all existing links. Running a query on it is going to take way to much time on the server and is going to be unreadable (you would get the addition diffs .. but you don't know if it is still there). --Dirk Beetstra T C (en: U, T) 16:30, 23 October 2019 (UTC)
  • I've gone ahead and created this for now so we can mark off what has been fixed. I'm hitting some of the smaller wikis just by searching alphabetically through the list of projects. Praxidicae (talk) 16:08, 23 October 2019 (UTC)
  • Did anybody raise a blacklist request? Putting a stop to more additions would be a good idea. QuiteUnusual (talk) 16:50, 23 October 2019 (UTC)
  • Since I was pinged, the domain has been blacklisted in IABot and I ran it on the wikis it is approved to run on. They should either have an archive URL attached to it now, or they should be marked as dead.—CYBERPOWER (Chat) 18:18, 23 October 2019 (UTC)
    • Sadly that doesn't do much, for instance in [1] the archived version is itself broken. I know it's not IABot's main aim and strength, but the URL should just be removed outright from the "cite journal"-like templates where the DOI is already filled. Nemo 19:46, 23 October 2019 (UTC)
    • Interestingly, some links to this domain were being marked as dead already in 2017. Maybe the squatting happened later. Nemo 20:07, 23 October 2019 (UTC)
      Nemo bis It happened on 10/20. Also relevant. Praxidicae (talk) 20:15, 23 October 2019 (UTC)
      Thanks! Nemo 20:52, 23 October 2019 (UTC)
    • I cleaned up manually on the Italian Wikipedia. Nemo 20:52, 23 October 2019 (UTC)
  • FYI, I am also manually fixing and noting at User:Praxidicae/DOI fix. Kind regards, — Tulsi Bhagat (contribs | talk) 06:37, 24 October 2019 (UTC)
  • We've now got a second hijacked domain, gaylesbiantimes.com Praxidicae (talk) 13:34, 29 October 2019 (UTC)

Praxidicae, could you summarise where we stand with this request, please? --Base (talk) 19:00, 19 April 2020 (UTC)

MediaWiki:Common.css@es.wikivoyage[edit]

Status:    In progress

The document contains two errors and several other warnings. I'd appreciate if a global interface editor with experience in CSS could take a look and assist them in fixing the issues.

Also the following code:

/* CSS for black text external links / blue text on hover */
body.ns-0 a.external,
body.ns-0 a.external:visited,
body.page-Wikivoyage_External_links a.external,
body.page-Wikivoyage_External_links a.external:visited,
body.page-Wikivoyage_talk_External_links a.external,
body.page-Wikivoyage_talk_External_links a.external:visited,
body.page-Wikivoyage_Listings a.external,
body.page-Wikivoyage_Listings a.external:visited,
body.page-Wikivoyage_talk_Listings a.external,
body.page-Wikivoyage_talk_Listings a.external:visited,
body.page-Wikivoyage_Attraction_listings a.external,
body.page-Wikivoyage_Attraction_listings a.external:visited,
body.page-Wikivoyage_talk_Attraction_listings a.external,
body.page-Wikivoyage_talk_Attraction_listings a.external:visited,
body.page-Wikivoyage_Activity_listings a.external,
body.page-Wikivoyage_Activity_listings a.external:visited,
body.page-Wikivoyage_talk_Activity_listings a.external,
body.page-Wikivoyage_talk_Activity_listings a.external:visited,
body.page-Wikivoyage_Restaurant_listings a.external,
body.page-Wikivoyage_Restaurant_listings a.external:visited,
body.page-Wikivoyage_talk_Restaurant_listings a.external,
body.page-Wikivoyage_talk_Restaurant_listings a.external:visited,
body.page-Wikivoyage_Bar_listings a.external,
body.page-Wikivoyage_Bar_listings a.external:visited,
body.page-Wikivoyage_talk_Bar_listings a.external,
body.page-Wikivoyage_talk_Bar_listings a.external:visited,
body.page-Wikivoyage_Shopping_listings a.external,
body.page-Wikivoyage_Shopping_listings a.external:visited,
body.page-Wikivoyage_talk_Shopping_listings a.external,
body.page-Wikivoyage_talk_Shopping_listings a.external:visited,
body.page-Wikivoyage_Accommodation_listings a.external,
body.page-Wikivoyage_Accommodation_listings a.external:visited,
body.page-Wikivoyage_talk_Accommodation_listings a.external,
body.page-Wikivoyage_talk_Accommodation_listings a.external:visited,
body.page-Wikivoyage_Don_t_tout a.external,
body.page-Wikivoyage_Don_t_tout a.external:visited
{
    color: black;
}
body.ns-0 a.external:hover,
body.ns-0 a.external:focus,
body.page-Wikivoyage_External_links a.external:hover,
body.page-Wikivoyage_External_links a.external:focus,
body.page-Wikivoyage_talk_External_links a.external:hover,
body.page-Wikivoyage_talk_External_links a.external:focus,
body.page-Wikivoyage_Listings a.external:hover,
body.page-Wikivoyage_Listings a.external:focus,
body.page-Wikivoyage_talk_Listings a.external:hover,
body.page-Wikivoyage_talk_Listings a.external:focus,
body.page-Wikivoyage_Attraction_listings a.external:hover,
body.page-Wikivoyage_Attraction_listings a.external:focus,
body.page-Wikivoyage_talk_Attraction_listings a.external:hover,
body.page-Wikivoyage_talk_Attraction_listings a.external:focus,
body.page-Wikivoyage_Activity_listings a.external:hover,
body.page-Wikivoyage_Activity_listings a.external:focus,
body.page-Wikivoyage_talk_Activity_listings a.external:hover,
body.page-Wikivoyage_talk_Activity_listings a.external:focus,
body.page-Wikivoyage_Shopping_listings a.external:hover,
body.page-Wikivoyage_Shopping_listings a.external:focus,
body.page-Wikivoyage_talk_Shopping_listings a.external:hover,
body.page-Wikivoyage_talk_Shopping_listings a.external:focus,
body.page-Wikivoyage_Restaurant_listings a.external:hover,
body.page-Wikivoyage_Restaurant_listings a.external:focus,
body.page-Wikivoyage_talk_Restaurant_listings a.external:hover,
body.page-Wikivoyage_talk_Restaurant_listings a.external:focus,
body.page-Wikivoyage_Bar_listings a.external:hover,
body.page-Wikivoyage_Bar_listings a.external:focus,
body.page-Wikivoyage_talk_Bar_listings a.external:hover,
body.page-Wikivoyage_talk_Bar_listings a.external:focus,
body.page-Wikivoyage_Accommodation_listings a.external:hover,
body.page-Wikivoyage_Accommodation_listings a.external:focus,
body.page-Wikivoyage_talk_Accommodation_listings a.external:hover,
body.page-Wikivoyage_talk_Accommodation_listings a.external:focus,
body.page-Wikivoyage_Don_t_tout a.external:hover,
body.page-Wikivoyage_Don_t_tout a.external:focus
{
    color: #0645ad;
}

is not needed as those pages do not exist on es.wikivoyage (I guess this was a copy-paste from en.voy) and can be removed.

Also, something strange happens to me when visiting that page that makes my PC to freeze intermitently.

Thanks for the assistance. —The preceding unsigned comment was added by MarcoAurelio (talk) 19:36, 20 December 2019 (UTC)

As this is a GS wiki and no active IAs/'crats, I'll take a look :) --WhitePhosphorus (talk) 12:35, 21 December 2019 (UTC)
@MarcoAurelio: I guess it's better to replace these Project: pages with the corresponding eswikivoyage local equivalents? --WhitePhosphorus (talk) 12:47, 21 December 2019 (UTC)
I don't think we have local equivalents of those so I feel it's safe to remove them. Thanks. —MarcoAurelio (talk) 12:54, 21 December 2019 (UTC)
I've done the removal, and reduced warnings from 130+ to 57. I'm marking this as done but feel free to double check if something can be further optimized as I only fixed 100% surely safe things. --WhitePhosphorus (talk) 15:35, 21 December 2019 (UTC)
Firstly, I agree with WhitePhosphorus that should be replaced these references to English Wikivoyage pages with the corresponding ones from Spanish Wikivoyage titles if exist, instead of deleting them all. Secondly, It's not like there is not any bureaucrat and interface admins there. There is an active bureaucrat, just there is not activity enough to use the permission, and interface admin is mostly granted ad hoc for a specific task or group of tasks. Therefore, this task could have been asked in Spanish Wikivoyage and performed there, so the best approach could have been done (replacing when possible instead of deleting them all). --Zerabat (discusión) 16:55, 21 December 2019 (UTC)
I've undid the controversial removal. Sorry for that. --WhitePhosphorus (talk) 00:14, 22 December 2019 (UTC)
Just left a message on local village pump. --WhitePhosphorus (talk) 11:05, 25 December 2019 (UTC)
@WhitePhosphorus: Any update? --Martin Urbanec (talk) 11:13, 20 March 2020 (UTC)

Potential cross-wiki hoax[edit]

Status:    In progress

This is not regular vandalism, but there is potential of a long running con, based on external information. I am asking for several pages and user accounts to be investigated as part of a potential coordinated hoax inside and outside Wikipedia. I may need a Spanish speaker and admins on several wikis (meta, commons, enwiki) for background info.

I was alerted of the following news articles, which I am going to consider as reliable:

This led me to this page en:Helen Mukoro Idisi (Wikidata), which may have to be deleted(?) as potentially being part of the hoax perpetrated by this person. Note that normally criminals (specially alleged ones) should be able to edit Wikipedia with no problems, but there is potential not only of editing articles about oneself, but also being used as part of a con with criminal intent. IMPORTANT: I am not saying this definitely happened, but I need someone to help me research if there is a hoax going on on Commons, meta and enwiki (maybe eswiki too?). From that page I found 2 suspicious accounts (please check global contribs): Aeccspain and HELEN MUKORO, the last one assumes to be the person mentioned in the article above, and has a user bio with data that has been accused by the police as false. The 2 accounts should be checked, as well as potential other editors of en:Helen Mukoro Idisi, en:Unión de Todos and other related articles which could be puppet accounts or meatpuppets of the same person. There could be lots of legitimate users there too, doing helpful edits, but it is difficult to separate them without check user tools and a deeper research, which hopefully someone here can help with. It is also difficult to separate fact from fiction (some facts, like election data, seem correct). --Jynus (talk) 09:58, 3 January 2020 (UTC)

@Jynus: I will suggest to go to the relevant village pump or start deletion discussions or quick deletion requests. Stewards and Global sysops are not involve in determining hoaxes. I suggest this to be locally handled. For sock-puppetry, it will be best to file an SPI or follow local procedures, more detail on Checkuser policy. --Camouflaged Mirage (talk) 10:19, 3 January 2020 (UTC)

Copyvio and other issues at siwiki[edit]

Status:    In progress

Hello. Can someone have a look at si:Wikipedia:Village pump (miscellaneous)#Admin access please? As I have been doing on other projects, I'd like to help out with media files on siwiki. I have clearly identified longstanding mass copyvio/licensing issues, and can also understand the language up to a certain extent. But I find the response there (from the only admin) quite peculiar and troubling.

The Sinhala Wikipedia has no bureaucrats, and only 1 active admin. The other two admins should probably be removed due to inactivity, but that's not why I am here. The most active user (if not the only active user), is also the admin themselves.

I'm willing to let this go and focus on other non-siwiki work, but that latest response is not a good sign, and also a sign that other potential admins may have been shooed away in the past. Appreciate if someone knowledgeable in cross-wiki policies can comment on this situation please? Rehman 10:39, 31 March 2020 (UTC)

The bulk of the vios are from one user, though there are a LOT of them. I would think that our global copyright policy supersedes any sort of local policy. Praxidicae (talk) 13:55, 31 March 2020 (UTC)
It actually appears to have been a group of students, see also this users uploads which include stock images that are subject to copyright and even has the watermarks... Praxidicae (talk) 14:01, 31 March 2020 (UTC)
Thanks for the reply, Praxidicae. I agree. Is that admin's reasoning valid though - can they stop someone (i.e. me) from going ahead, singlehandedly? And should such comments be tolerated at all from the sole admin of a project? To me IMHO, the last comment sounded like someone who wants to run a private project. Rehman 14:04, 31 March 2020 (UTC)
I mean, no. A single admin can't stop any person from requesting rights but I think they make a good point and you probably shouldn't. It's a GS wiki and deletions can be handled that way, as well as through their admins. Praxidicae (talk) 14:12, 31 March 2020 (UTC)
Alright, I will not push, in that case. For arguement sake though, considering that there are barely any active users there, a ton of bad files, and almost zero probability that the only admin can handle all that mess. What do we do in such a situation, when the only admin (and probably the only editor) comments against someone offering to help? For the sake of our brand reputation, we cannot let it run as a private wiki, can we? Rehman 14:35, 31 March 2020 (UTC)
I don't think encouraging non-SI speaking editors to seek adminship is the solution here. We also have capable global sysops who can assist should it be needed. SI has managed pretty well so far. Praxidicae (talk) 14:39, 31 March 2020 (UTC)
Okay. Just to clarify though, I do speak Sinhala, and currently live in Sri Lanka. I also am the founder of Wikimedia Community User Group Sri Lanka. That being said, I also need to state that SI has not been managing that well - the bulk of the bad files dates back to 2008 (that's over a decade ago). Rehman 14:45, 31 March 2020 (UTC)
Perhaps I should clarify. The issue appears to also be a large amount of improperly licensed non free files. If you're a speaker of the language, you should create discussions about those files. There's no need for adminship for that and NFF isn't something that should be nuked without conversation imo. If you want to become an admin there, follow their RFA procedure because stewards cannot grant admin rights in local communities without a consensus there. Praxidicae (talk) 14:48, 31 March 2020 (UTC)
Rehman maybe another solution here is to start creating the right licensing templates? It looks like a lot of their NFF uploads (you can see in the file list and user logs) were uploaded as NFF via enwiki templates that don't exist on siwiki. You seem to be pretty good in that area, can they be imported? Praxidicae (talk) 14:57, 31 March 2020 (UTC)
(ec) Not being rude, but the RFA there is a copy of the enwiki RFA (si:WP:RFA), created by the same admin in 2010, and never used since. That is the only reason I posted at their VP - for better visibility (but that too has barely any visitors). I'm not trying to argue, Praxidicae. I just think this is not good for the health of our brand. What I exposed was just the tip of the iceberg from a single category. With the political situation of Sri Lanka, we're lucky those files are just junk and not something offensive/sensitive. Else a ban from the government would not have been too far away. I see that two volunteers from here has now commented there. Hopefully the message is passed, and things will be sorted. I'm just trying to help. Rehman 14:59, 31 March 2020 (UTC)
Sure. I'm commenting from work. I will have a deeper look soon as soon as I'm done for the day. Cheers, Rehman 15:00, 31 March 2020 (UTC)
Yes, I think I can fix at least the most used license types. Rehman 07:18, 1 April 2020 (UTC)
@Rehman:, There is an active admin on the wiki who is willing to act on the pages/files if you tag them, you can make the request for specific administrative actions to the admin there. This page is for requesting specific administrative actions on wikis with no active administrators, is there anything else you need help with here?-BRP ever 08:02, 11 April 2020 (UTC)
We're talking of hundreds/thousands of files here. I'm sorry, but I'm not interested in inflating this task literally two-fold when I already clearly showed him/her a stash of bad files to start with. This user didn't allow me to help by blocking the sysop process single-handedly (for a baseless reason, FYI), and is also not interested in cleaning the mountain of copyvios themselves. The project is a mess and literally run like a private wiki due to the odd situation we have here, and sadly no one seems to be able to do anything because there is no policy or guideline covering this situation. The sole admin there is clearly not working in good faith, and I'm sure that is already clear by now. Rehman 13:25, 11 April 2020 (UTC)
For transparency: Steward_requests/Permissions/2020-04#Rehman@siwiki. Rehman 06:25, 14 April 2020 (UTC)

MediaWiki:Common@diqwikipedia[edit]

Status:    In progress

Hi, We have some problem w:diq:MediaWiki:Common.css and w:diq:MediaWiki:Common.js. They are not work correct. Can you changes copy to en.wikipedia.org, and paste to diq.wikipedia.org?n Xorasan talkcontribs 12:48, 28 April 2020 (UTC)

Xorasan: Do you want the whole code to be copied? Will that be useful? Esteban16 (talk) 16:17, 28 April 2020 (UTC)
yes exactly, because another code doesn't work on pagê and template. We need try. Xorasan talkcontribs 03:48, 30 April 2020 (UTC)
Copying any code into other projects can cause even more problems. If you have the current script problem you have to describe it so that someone can fix it.-𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 11:37, 2 May 2020 (UTC)
@Xorasan: --Esteban16 (talk) 21:37, 6 May 2020 (UTC)
@Esteban16 and WikiBayer: we have common.css talk page example code and common.js talk page example code, you can paste and fix it. Xorasan (talk) 11:22, 7 May 2020 (UTC)
Seems that there are a lot of scripts that are turned on. I wonder whether they would be better as gadgets, and on by default, rather than forced common javascript. Definitely makes problem solving issues a lot easier.  — billinghurst sDrewth 06:35, 19 May 2020 (UTC)

Harassment : Global request for protection of talk pages[edit]

Status:    In progress

Hi, Excuse me for my bad english. Since 2 years, I have been harassed on all the projects of the foundation, you will find here the details User:Lomita/Harassment. Do you have a possibility to protect my pages? or do a filter?

I allow myself to @Billinghurst: with whom I have already had email exchanges in the past Thank you for all you can do for me.

Have a nice day --Lomita (talk) 09:17, 30 April 2020 (UTC)

@Lomita: The global abuse filter that I wrote essentially does a protection of your user and user talk pages, excluding frwiki. That filter only applies to global AF wikis, and that is not universal. To see which wikis to which this does not apply, you need to consult this list of large wikis, and can scratch out four—metawiki, wikidatawiki, frwiki and enwikisource—that opted into global filters. At these other wikis, you are going to need to request protection of both your user and user talk pages, as each has a community that manages that aspect of their editing.

As a helper, I have done cebwiki for you, and you have never logged into mgwiktionary, so nothing to do there, and enwiki has been done previously, which leaves 30+ remaining. The place to ask on these wikis I would suggest would be their admin noticeboards, see Project:Administrators' noticeboard (Q4580256) for lists and links.  — billinghurst sDrewth 00:07, 1 May 2020 (UTC)

As just a side note, can we remember this for Community Wishlist Survey 2021? --Rschen7754 19:08, 14 May 2020 (UTC)

Lomita, can we consider this request done? --Base (talk) 01:32, 28 May 2020 (UTC)

Presumed LTA pushing small wikis to 1K[edit]

Status:    In progress

Same old story. Rotating roster of IP addresses, useless ministubs created, stopping once the wiki has reached 1K. I won't bother linking to the individual IP addresses, but here's Special:NewPages for each affected wiki:

- dcljr

Oops. That last one should have been om:Special:RecentChanges, since the editing was adding useless links to already existing pages, not creating new ones. - dcljr (talk) 04:49, 18 May 2020 (UTC)

Thanks Dcljr.

Did a cleanup at chrWP and added a url to the local spam-blacklist with autoconfirmed to inhibit some of the edits. Blocking these ranges at those wikis, we will need to do some broader checks.

  • 2001:5b0:46cb:1338:0:0/64
  • 31.210.91.0/24
  • 193.182.144.0/24

Done a fly-by clean upon the other wikis. Will have to see what we may need to do for abuse filters. <face pull> Happy to take suggestions for filters as we can now better target wikis by language or by type as required.  — billinghurst sDrewth 06:14, 18 May 2020 (UTC)

Marking as Yes check.svg Done for the general cleanup. X mark.svg Not done for broader checks of IP addresses.  — billinghurst sDrewth 06:20, 18 May 2020 (UTC)

Reopening, as every wiki listed is back up to 1K (actually, at omwiki nothing was done but blocking at omwiki — to be clear, I'm asking for the May 18th edits made by IPs on that wiki to be mass-reverted, assuming someone agrees that they are useless) with similar editing done by IPs, some immediately undoing the deletions by billinghurst and others with just an equivalent amount of page creation. Looks like this will need ongoing attention. - dcljr (talk) 01:13, 19 May 2020 (UTC) [To clarify the intended meaning, insertions and deletions were made to this comment by dcljr (talk) 23:41, 19 May 2020 (UTC).]

I've deleted them for now but I don't think it is appropriate to close this section unless we wither come up with a more permanent way to fix these or discern that it is impossible. Best, Vermont (talk) 01:22, 19 May 2020 (UTC)
  • Comment Comment reverts are a little more complex as ideally we would not want to kill RC, so we need to bot them. Pywikibot can be set to manage those reverting edits, though to get bot rights is a little more complex, especially as crosswiki global bots are not for reverting. We need a new paradigm, either consensus on how we will handle, and one that is ticked off by stewards OR we just do it noisily and to hell with RCs.
    Need stewards comment on what they will do as they can do personal or bot rights management judiciously, against what they want managed by others.  — billinghurst sDrewth 06:32, 19 May 2020 (UTC)

Adding to this list

  • bcl: where there has been activity on 31.210.91.0/24 and some out of the range of RC
  • sm: as above range and 2600:1700:1e0:6b20:0:0/64

 — billinghurst sDrewth 07:08, 19 May 2020 (UTC)


MediaWiki:Vector.css@trwikisource[edit]

Status:    Not done

Could you please add the s:MediaWiki:Vector.css code to the s:tr: MediaWiki:Vector.csspage please ? The Interwiki option does not work while using Vector. --Satirdan kahraman (talk) 20:50, 24 May 2020 (UTC)

@Satirdan kahraman:What do you mean with "The Interwiki option"? Do you mean interwikilinks? There is no code on the linked page that has anything to do with the Interwiki links.--𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 16:52, 26 May 2020 (UTC)

@WikiBayer: Yes, I mean interwikilins. "In other languages" option on left side. --Satirdan kahraman (talk) 16:59, 26 May 2020 (UTC)

This is not due to this CSS file--𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬

@WikiBayer:, This option does not shows itself when using the Vector theme. Thats why you have to transfer the css codes from the english page(s:MediaWiki:Vector.css to Turkish. (s:tr: MediaWiki:Vector.css)

What do you try to resolve? I can see interwiki links at s:tr:Anasayfa and I have the vector skin. Stryn (talk) 18:08, 26 May 2020 (UTC)
@Satirdan kahraman:It is not a code related to the Interwiki links. Feel free to convince yourself and test the code in your personal vector.css--𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 18:13, 26 May 2020 (UTC)

Satirdan kahraman, I think you are experiencing phab:T252800. You have to wait until the ticket is resolved and deployed in trwikisource. --Base (talk) 06:44, 27 May 2020 (UTC)

OAuth permissions[edit]

Symbol comment vote.svg Preferably permission requests should be submitted using the form from Special:OAuthConsumerRegistration.

After submitting this form, you will receive a token that your application will use to identify itself to MediaWiki. An OAuth administrator will need to approve your application before it can be authorized by other users. It is possible to request approval using {{oauthapprequest}}, please create a sub-section to this part.

A few recommendations and remarks:

  • Try to use as few grants as possible. Avoid grants that are not actually needed now.
  • Versions are of the form "major.minor.release" (the last two being optional) and increase as grant changes are needed.
  • Please provide a public RSA key (in PEM format) if possible; otherwise a (less secure) secret token will have to be used.
  • Use the JSON restrictions field to limit access of this consumer to IP addresses in those CIDR ranges.
  • You can use a project ID to restrict the consumer to a single project on this site (use "*" for all projects).
  • The email address provided must match that of your account (which must have been confirmed).


See also[edit]