gangleri wrote:

see also
bug 3089: Warning when uploading images like 600px-foo

foenyx wrote:

*** Bug 3089 has been marked as a duplicate of this bug. ***

• Bug 3822 has been marked as a duplicate of this bug. ***

alphasigmax wrote:

They stuff up categories and such as well.

msgm.rose wrote:

nice idea

gangleri wrote:

Is this request a request for "Product" 'MediaWiki' and "Component" 'UploadingÄ
or for "Product" 'Wikimedia' and "Component" 'General/Unknown'?

gangleri wrote:

marking as dependend of
Bug 2532: Image filenames in the form 123px-Something.jpg are not reserved

Not a dependency, that's a dupe.

• This bug has been marked as a duplicate of 2532 ***

dbenbenn wrote:

Nobody at bug 2532 has proposed disallowing images named 123px-foo. That bug is
about the fact that the thumbnail directory migration was done in a buggy way,
so that thumbnails weren't properly generated for images named 123px-foo. I'm
going to reopen this bug, unless someone wants to address *this actual issue*,
which has to do with human error when transferring images to the Commons, at bug

2532. (I agree that this bug doesn't depend on bug 2532; the two issues are

independent.)

The summary on 2532 is wrong then. Ah well, marking it FIXED and this WONTFIX.

dbenbenn wrote:

Guess what: marking a bug as WONTFIX without any explanation is a great way to
piss people off, and scare away potential contributors. Is there any reason
behind the WONTFIX declaration?

I've reopened bug 3089, which proposes at least having a *warning* when people
try to upload these thumbnails. I think disallowing the upload entirely would
be better, though.

• Bug 3089 has been marked as a duplicate of this bug. ***

It doesn't seem to be something that actually needs to be done, since there's no
longer any technical reason to prevent such uploads.

I've marked 3089 as a duplicate of this seems it seems to be *exactly* the same
issue stated in slightly different terms.

wiki.bluefish wrote:

not only commons needs this feature. in de.wp there were on November 18th 213 of
these 123px-images, mostly transferred from en.wp:
http://de.wikipedia.org/w/index.php?title=Benutzer:BLueFiSH.as/Datenbankabfragen/px-bilder&oldid=10917420
I have removed some, but there are still many pictures that need to be cleaned
up, (with a transfer to commons):
http://de.wikipedia.org/w/index.php?title=Benutzer:BLueFiSH.as/Datenbankabfragen/px-bilder&oldid=12002837

It would help really to minimize the effort for the "cleaning brigade" by
disallowing 123px-images!

dbenbenn wrote:

(In reply to comment #13)

It doesn't seem to be something that actually needs to be done, since there's no
longer any technical reason to prevent such uploads.

It's a people issue, not a technical issue. As FoeNix wrote in the first comment,
when moving an image to the Commons, "people forget to upload the fullsize version
(and sometimes they ask for deletion of original afterward leading to loss of the
fullsize original image)". See
http://commons.wikimedia.org/wiki/Category:Images_uploaded_at_reduced_resolution
for example. All of those images are going to have to be replaced by hand. If
MediaWiki had prevented their upload in the first place, with a helpful message
about uploading the full size version instead, a lot of effort could have been
saved.

What is needed is a configuration option to allow disabling these thumbnail
uploads. I know the Commons would want to set that option; German Wikipedia
might too.

Ah, ok I see. Sorry, my mistake. Reopening.

I would be inclined to keep it a warning rather than a strict disallowing,
but a warning should do the job.

Rather than a special feature for this, why not have an "image blacklist" giving a list of restricted regular expressions,
which displays a system message when the blacklist is matched? It could pass the matched regexp and the filename as
parameters to the system message. Then people could easily configure the server to do this and many other upload restriction
tasks.

(In reply to comment #16)

I would be inclined to keep it a warning rather than a strict disallowing,
but a warning should do the job.

Implemented as warnings in r20563.