User talk:Shubinator/Archive 40

DYKcheck prose
Shubinator, I was just running DYKcheck on St. Augustine Parish Church (Laguna), and noticed that it was counting some text in the External links section, about as prose. A quick investigation showed that this text was generated by the "commons category inline" template; it's the "Media related to" X "available at Wikimedia Commons" message. Is there an easy way you can convince DYKcheck that this is not prose that should count? (Indeed, I wonder whether anything should count as article prose if it's in External links.)

Thanks for looking into this. BlueMoonset (talk) 14:24, 21 September 2014 (UTC)


 * I took a look at the HTML and unfortunately it's fairly difficult to figure out that the template isn't standard text: 

 Media related to Saint Augustine Parish Church of Bay at Wikimedia Commons 
 * It's even using the p HTML tag, generally used to denote prose. If the template is tweaked so it's easier to identify (adding a div tag around it with a class name might be enough), I could tweak DYKcheck to recognize it. As is, though, there isn't an identifying mark. Shubinator (talk) 02:11, 24 September 2014 (UTC)

A new task for your DYK bot?
At Talk:Main Page, various suggestions have been discussed to deal with the occasional problem of TFA images not being protected at Commons. One clever person remembered that your DYK bot issues an alert if a DYK image is unprotected. Do you think you might be able to configure it to issue an alert (to a location to be decided) if "Wikipedia:Today's featured article/[tomorrow's date]" has an unprotected image? Yours, BencherliteTalk 15:42, 20 October 2014 (UTC)
 * Definitely doable, I can tweak DYKUpdateBot to do this. The code is the checkIfProtected function at User:DYKUpdateBot/Code. The toughest part would be figuring out which image is next up. I'm not sure that'll entirely fix TFA's problem though. Is it possible for the automated Commons protection to accidentally protect an image that has already been vandalized? Shubinator (talk) 03:51, 21 October 2014 (UTC)
 * Presumably it can just do something like this?
 * Find tomorrow's TFA using something like: Today's featured article/
 * Check to see if the blurb uses TFAIMAGE. If not, stop.
 * If yes, then find the file name (TFAIMAGE doesn't use a "File:" prefix but hopefully this won't be difficult to overcome)
 * Check to see whether the file exists at Commmons. If not, then the file is locally hosted and automatically protected.  Stop.
 * If yes, then check to see if the file is fully protected. If yes, then stop.
 * If no, then issue alert.
 * The question of image vandalism while the blurb is still in the queue is a slightly different issue, but AFAIK it hasn't happened yet, whereas alterations to images that should have been protected but weren't has now happened. If we can address one problem first, then we can see if we need to prevent something else!  In any event, vandalizing an image earlier in the process would hopefully be spotted well in advance of the blurb reaching the main page (not least because it's rare for an image to be used in a TFA blurb that isn't also in the article, so changing the image would change it in both places).  Thanks, BencherliteTalk 10:21, 21 October 2014 (UTC)
 * Sounds good. Let me know when everyone's settled on an alert page (the page the bot should post a notice to when tomorrow's TFA image is unprotected). I'll start tinkering with the code, might take a while since I don't have much spare time these days. Shubinator (talk) 01:12, 22 October 2014 (UTC)