User talk:Jeff G.

From Wikimedia Commons, the free media repository
(Redirected from User:Jeff G./talk)
Jump to navigation Jump to search

Babel user information
en-N This user has a native understanding of English.
en-US-N This user has a native understanding of American English.
es-1 Este usuario tiene un conocimiento básico del español.
Users by language

Welcome to my user talk page![edit]

Current Monthly Archive

   (redlinked the first week
   or more of each month):

2024/March

Past Monthly Archives

Newly registered and IP editors may leave messages at the bottom of this page.

"Fixes"[edit]

Hi, In Commons:Deletion requests/File:Inaugurazione Komen Italia.jpg and other DRs, the link leads to nothing. Yann (talk) 10:06, 5 March 2024 (UTC)[reply]

@Yann: I know, we need one of the solutions discussed at MediaWiki talk:Gadget-GoogleImagesTineye.js#Google Images searches failing for whatever tool Nutshinou used to make this edit (probably the "Report copyright violation" tool). It would be great if the "Challenge speedy deletion" functionality of {{Copyvio}} didn't just blindly accept the first set of right braces it came upon, necessitating fixes like this. Also, please expound on your reasoning for creation of Commons:Deletion requests/File:My meal had a name 近江牛 2008 (2761261149).jpg rather than deletion.   — 🇺🇦Jeff G. please ping or talk to me🇺🇦 10:26, 5 March 2024 (UTC)[reply]
Yes, this is the tool I put at my common.js, after checking the link, I believe I've made the according change. Hope this doesn't cause any more issues. Nutshinou Talk! 12:22, 5 March 2024 (UTC)[reply]
@Nutshinou: Thanks, I have copied your "Copyvio (www)" section and I will try it the next time I have a need.   — 🇺🇦Jeff G. please ping or talk to me🇺🇦 12:44, 5 March 2024 (UTC)[reply]
My first attempt worked on the file page, but failed on the user talk page in this edit. Further attempts failed. Please just use the following lines from the source of this section for the "talk" parts:
'talk_tag': '{'+'{subst:copyvionote|1=%FILE%|2=Found elsewhere on the web and unlikely to be own work.}}',
'talk_summary': 'Notification of possible copyright violation for %FILE% because it is Found elsewhere on the web and unlikely to be own work.',
  — 🇺🇦Jeff G. please ping or talk to me🇺🇦 14:16, 5 March 2024 (UTC)[reply]
Pinging @Minorax as host of the "live examples" referenced by Help:QuickDelete.   — 🇺🇦Jeff G. please ping or talk to me🇺🇦 14:21, 5 March 2024 (UTC)[reply]
Nope, my limited knowledge in .js can't help with this. --Min☠︎rax«¦talk¦» 01:23, 6 March 2024 (UTC)[reply]
My two pence. Looks like
should have been (using File:Silversmith.jpg instead of the deleted File:Saurabhtamhane.jpg)
Glrx (talk) 02:30, 6 March 2024 (UTC)[reply]
Looking at common.js
{
                    'label': 'Copyvio (www)',
                    'tag': '{'+'{copyvio|1=[[COM:CSD#F1]], Possible copyright violation: [[COM:NETCOPYRIGHT|Found elsewhere on the web and unlikely to be own work]]: [https://lens.google.com/uploadbyurl?url={{filepath:{'+'{subst:BASEPAGENAME}}}} Google Lens]}}',
                    'img_summary': 'speedy deletion: possible copyvio',
                    'talk_tag': '{'+'{subst:copyvionote|1=%FILE%|2=[[COM:NETCOPYRIGHT|Found elsewhere on the web and unlikely to be own work]].}}',
                    'talk_summary': 'Notification of possible copyright violation for %FILE% because it is [[COM:NETCOPYRIGHT|found elsewhere on the web and unlikely to be own work]].',
                },
The effective {{filepath:{{subst:BASEPAGENAME}}}} is the issue. On a File page, it may get the right value, but putting the string on a user talk page will not get the file name. The subst in the tag is not executed when common.js is loaded but rather when the text is pasted into the File page and again when pasted into the Talk page.
Glrx (talk) 03:04, 6 March 2024 (UTC)[reply]
See MW:Manual:Interface/JavaScript and mw.config.get("wgTitle"). Something like
"... https://lens.google.com/uploadbyurl?url={{urlencode:{{filepath:" + mw.config.get("wgTitle") + "}}}} ..."
might do the trick.
A %FILE% substitution does not work because {{filepath:File:name.jpg}} fails; we do not want the "File:" namespace identifier. There may be a %word% that does not include the namespace.
Glrx (talk) 17:19, 6 March 2024 (UTC)[reply]
@Glrx: Thanks for trying. I made this edit, found File:Flag of Gafsa Governorate (1979-2000).svg (which qualified and is now deleted), and tagged it that way, resulting in these edits implicating this incorrect URL. Please try again.   — 🇺🇦Jeff G. please ping or talk to me🇺🇦 20:50, 6 March 2024 (UTC)[reply]
Hmm. Compare the actual URL to the expected URL:
ACTUAL: https://lens.google.com/uploadbyurl?url=https%3A%2F%2Fupload.wikimedia.org%2Fwikipedia%2Fcommons%2F1%2F1a%2FFlag_of_Gafsa_Governorate_%25281979-2000%2529.svg
EXPECT: https://lens.google.com/uploadbyurl?url=https%3A%2F%2Fupload.wikimedia.org%2Fwikipedia%2Fcommons%2F1%2F1a%2FFlag_of_Gafsa_Governorate_%281979-2000%29.svg}}
So it looks like filepath URL-encoded the parentheses as %28 and %29, and then urlencode quoted the percent signs as %25.
Check using a File with a paren in its name to test filepath. Consider File:Flag of the United Kingdom (3-5).svg
OK, so filepath is URL encoding. Do not need to do it twice. The filename colons and slashes should pass as URL parameters.
Consequently, we can just delete the urlencode magic word. That is, use
  • {
      'talk_tag': '{'+'{subst:copyvionote|1=%FILE%|2=[[COM:NETCOPYRIGHT|Found elsewhere on the web and unlikely to be own work]]: [https://lens.google.com/uploadbyurl?url={{filepath:' + mw.config.get("wgTitle") + '}} Google search].}}'
    }
    
Test case: https://lens.google.com/uploadbyurl?url=https://upload.wikimedia.org/wikipedia/commons/8/83/Flag_of_the_United_Kingdom_%283-5%29.svg
Test case fails; that might be because it is an SVG file. Try a PNG.
Test case (PNG conversion): https://lens.google.com/uploadbyurl?url=https://upload.wikimedia.org/wikipedia/commons/thumb/8/83/Flag_of_the_United_Kingdom_%283-5%29.svg/300px-Flag_of_the_United_Kingdom_%283-5%29.svg.png
PNG works.
Another point. Here is your old common.js; notice that the single quotes and double quotes do not match up, but somehow it worked (that is 'foo" was interpreted as 'foo').
  • {
      'talk_tag': '{'+'{subst:copyvionote|1=%FILE%|2=[[COM:NETCOPYRIGHT|Found elsewhere on the web and unlikely to be own work]]: [https://lens.google.com/uploadbyurl?url={{urlencode:{{filepath:" + mw.config.get("wgTitle") + "}}}} Google search].}}'
    }
    
make the quotation marks match
  • {
      'talk_tag': '{'+'{subst:copyvionote|1=%FILE%|2=[[COM:NETCOPYRIGHT|Found elsewhere on the web and unlikely to be own work]]: [https://lens.google.com/uploadbyurl?url={{urlencode:{{filepath:' + mw.config.get("wgTitle") + '}}}} Google search].}}'
    }
    
Glrx (talk) 02:10, 7 March 2024 (UTC)[reply]
@Glrx: Thanks again, that worked to form a good link in special:diff/858640674! I have removed the link from the talk_summary because it's not clickable there.   — 🇺🇦Jeff G. please ping or talk to me🇺🇦 10:16, 7 March 2024 (UTC)[reply]
Hi. You need to remove the urlencode magic word that wraps a filepath. My fault because the last two syntaxhighlights were showing a problem with the old code. That is, in lines 114–120 of your commons.js,
                {
                    'label': 'Copyvio (www)',
                    'tag': '{'+'{copyvio|1=[[COM:CSD#F1]], Possible copyright violation: [[COM:NETCOPYRIGHT|Found elsewhere on the web and unlikely to be own work]]: [https://lens.google.com/uploadbyurl?url={{filepath:{'+'{subst:BASEPAGENAME}}}} Google search]}}',
                    'img_summary': 'speedy deletion: possible copyvio',
                    'talk_tag': '{'+'{subst:copyvionote|1=%FILE%|2=[[COM:NETCOPYRIGHT|Found elsewhere on the web and unlikely to be own work]]: [https://lens.google.com/uploadbyurl?url={{urlencode:{{filepath:' + mw.config.get("wgTitle") + '}}}} Google search].}}',
                    'talk_summary': 'Notification of possible copyright violation for %FILE% because it is [[COM:NETCOPYRIGHT|found elsewhere on the web and unlikely to be own work]].}}',
                }
Line 118 should be
                    'talk_tag': '{'+'{subst:copyvionote|1=%FILE%|2=[[COM:NETCOPYRIGHT|Found elsewhere on the web and unlikely to be own work]]: [https://lens.google.com/uploadbyurl?url={{filepath:' + mw.config.get("wgTitle") + '}} Google search].}}',
Glrx (talk) 17:07, 7 March 2024 (UTC)[reply]
@Glrx: Ok, that works with normal filenames and with a parenthesized filename here.   — 🇺🇦Jeff G. please ping or talk to me🇺🇦 10:58, 8 March 2024 (UTC)[reply]

Not worth the time, I'm afraid[edit]

Regarding this comment of yours, I'm afraid you're wasting your time. He's been on Commons since circa 2006, and numerous people (myself included) have tried to give him similarly-helpful advice over the decades- yet he hasn't given any real sign of taking any of it on board.

I've no idea if it's primarily lack of money for better equipment (*), but I suspect not. Faults like haze or dirt on the lens- which would be easy to address even on an otherwise inadequate camera or smartphone- have remained across the numerous models he's used over the years. Ditto (e.g.) the weird framing on cars and habit of squeezing them into the diagonal.

Point is, he's a creature of habit, and if he hasn't changed after almost 18 years... he won't.

It's frustrating to see someone who (on one hand) obviously dedicates so much time and borderline-obsessive effort to take such photos yet consistently squander that on dismal quality- due both to equipment and technique- but I'm afraid that's the deal.

Also, thank you for your support for my suggested proposal (despite its misrepresentation) that uploading his car photos should at least have been considered separately from the distinct and far more serious problems surrounding those of people- and given a fair consideration their own (albeit still minimal and questionable) "merits".

(*) A far greater issue on the photos of people because- unlike the cars- those tend to be taken under less bright lighting that shows up the problems with tiny, noise-prone/noise-reduced smartphone sensors even more seriously.

All the best,

Ubcule (talk) 00:32, 9 March 2024 (UTC)[reply]