Jump to content

MediaWiki talk:Pageimages-denylist

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Protected edit request on 19 December 2018

[edit]

Add File:United_Kingdom_relief_location_map.jpg to the list. This default map image is used on Template:Infobox UK place and related UK location templates, which is used across thousands of articles. In some cases - I think where the actual photo of a place is squareish - the map is being chosen as the "best image" by the API (eg. https://en.wikipedia.org/w/api.php?action=query&format=xml&prop=pageimages&titles=Sherwood%20Observatory). (The map is not used on the one article it would be the best image for, United Kingdom.) Lord Belbury (talk) 09:47, 19 December 2018 (UTC)[reply]

 Donexaosflux Talk 15:37, 20 December 2018 (UTC)[reply]

Would somebody consider adding this image to the list? If one hovers over Statue of Liberty (and likely others) while logged out, this image is appearing instead of the image of the subject; in this case, it should be File:Lady Liberty under a blue sky (cropped).jpg appearing instead. Home Lander (talk) 16:54, 24 March 2020 (UTC)[reply]

In taking a look through the first 50 backlinks from the file, Chrysler Building and Shea Stadium are doing the same thing. Home Lander (talk) 16:57, 24 March 2020 (UTC)[reply]
You wouldn't get the wanted image instead in any of the three mentioned articles. You would get no image or another map. Images can only be taken from the lead in Wikipedia and mw:Extension:PageImages#Image choice says: "Any images for which the ratio is less than 0.5 will score negatively and be discarded." PrimeHunter (talk) 17:17, 24 March 2020 (UTC)[reply]
PrimeHunter, why does the correct image show when logged in then? All three of the above articles generate proper images (though Shea Stadium looks pretty awful) when hovering while logged in. I tried purging the pages and it made no difference; the map still appears when logged out. Home Lander (talk) 21:00, 24 March 2020 (UTC)[reply]
When you are logged out, the preview hover feature is mw:Page Previews which uses the page image. MediaWiki:Pageimages-blacklist only applies to page images. If you are logged in then the preview hover feature depends on your preferences. It sounds like you have disabled "Page previews" at Special:Preferences#mw-prefsection-rendering and enabled "Navigation popups" at Special:Preferences#mw-prefsection-gadgets. Wikipedia:Tools/Navigation popups does not use the page image (it predates the feature) but selects an image with its own algorithm. I don't know the details of that. There is code in MediaWiki:Gadget-popups.js. PrimeHunter (talk) 21:26, 24 March 2020 (UTC)[reply]
 Not done for now: please establish a consensus for this alteration before using the {{edit protected}} template. Izno (talk) 17:58, 29 March 2020 (UTC)[reply]

Protected edit request on 17 July 2020

[edit]

Add File:Conservatism in the United States Collage 3.jpg, for the same reasons as File:Conservatism in the United States Collage 2.jpg. At the moment, it's showing up as the page image at Candace Owens, for example. Vahurzpu (talk) 19:07, 17 July 2020 (UTC)[reply]

 Donexaosflux Talk 19:50, 17 July 2020 (UTC)[reply]

Protected edit request on 25 September 2020

[edit]

Add File:Liberalism in the United States Collage.png for the same reason as the above. Was showing up incorrectly on Sonia Sotomayor, for example. Vahurzpu (talk) 06:34, 25 September 2020 (UTC)[reply]

 Donexaosflux Talk 13:56, 25 September 2020 (UTC)[reply]

Protected edit request on 3 May 2022

[edit]

Transclude {{MediaWiki:Bad image list}} onto this page. Since none of the images on the Bad image list should be used outside of their designated pages, they should not show up in pop-ups or search results fed by pageimages either. (Note that this will require a null edit or a purge with the forcerecursivelinkupdate option be done on this page when MediaWiki:Bad image list is updated.) --Ahecht (TALK
PAGE
) 15:26, 4 May 2022 (UTC)[reply]

@Ahecht has this method been tested somewhere? — xaosflux Talk 15:29, 4 May 2022 (UTC)[reply]
@Xaosflux I've tested running the same SQL query that the pageimages extension does to pull the pagelinks table, and as long as the transcluding page is null edited or purged with the recursivelinkupdate option the SQL query returns the full list. I have not been able to test it with the actual pagelinks extension (a test was performed on a wiki in the betacluster, but it was inconclusive as the pageimages-denylist didn't work at all on that wiki, while it clearly works here). --Ahecht (TALK
PAGE
) 15:56, 4 May 2022 (UTC)[reply]
Do you know if testwiki supports that? I don't want to break this page accidentally, especially if it takes a while to cache out. — xaosflux Talk 16:26, 4 May 2022 (UTC)[reply]
@Xaosflux Testwiki doesn't have the pageimages extension installed. --Ahecht (TALK
PAGE
) 17:04, 4 May 2022 (UTC)[reply]
 Not done @Ahecht: declining per developer response at mw:Topic:Wv7qxbp3jvhf9qju that transclusion is not supported for this. — xaosflux Talk 10:52, 12 May 2022 (UTC)[reply]
Aside from it (currently) not working, I would Oppose that kind of misuse of these lists. First of all it would damage functionality such as PagePreviews. Secondly the purpose of BadImageList is vandalism prevention. That list contains 0% of our offensive images meaning it would be 0% effective, and any resemblance to an offensive-image list is incidental. If a bunch of people start spamming the Valentine's day image and it goes on the list, this proposal would be breaking PagePreviews and other functionality for the Valentine's day article. And finally, WP:NOTCENSORED is policy. It would be inappropriate to attempt to implement a censorship scheme without getting consensus on that Policy Talk page first. This idea would raise a lot of other problems as well, and there surely will be a lot of opposition at the policy page.
P.S. I am posting on this currently not-working subject in case anyone does attempt to get it working. Alsee (talk) 11:46, 19 January 2023 (UTC)[reply]