[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: erikrose Type: PLIP| Status: closed Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: fixed Keywords: | +--- Changes (by esteele): * status: reopened = closed * resolution: = fixed Comment: Merged in http://dev.plone.org/collective/changeset/99402 -- Ticket URL: http://dev.plone.org/plone/ticket/9186#comment:52 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: erikrose Type: PLIP| Status: reopened Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Comment(by esteele): This PLIP has been accepted for merging into Plone 4.0 The final vote was: Alec Mitchell +1 David Glick +1 Erik Rose - Laurence Rowe +1 Matthew Wilkes +1 Ross Patterson +1 Please merge your branches into the Plone 4.0 head by end-of-day Friday Oct 16. If you need assistance with merging, please contact me. We'll be assigning a documentation ticket to this PLIP shortly. Please assist the docs team in documenting the changes and new features that this PLIP introduces. -- Ticket URL: http://dev.plone.org/plone/ticket/9186#comment:50 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: erikrose Type: PLIP| Status: reopened Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Comment(by rossp): FWT vote: +1 for merge -- Ticket URL: http://dev.plone.org/plone/ticket/9186#comment:49 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: erikrose Type: PLIP| Status: reopened Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Comment(by erikrose): (In [30229]) Updated to describe the improved implementation. Refs #9186. -- Ticket URL: http://dev.plone.org/plone/ticket/9186#comment:48 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: erikrose Type: PLIP| Status: reopened Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Comment(by esteele): Your PLIP has been reviewed by the Framework team. Feel free to discuss any suggested changes either here in the PLIP ticket or on the mailing lists. Final deadline for this PLIP is set for September 23. -- Ticket URL: http://dev.plone.org/plone/ticket/9186#comment:45 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: erikrose Type: PLIP| Status: reopened Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Comment(by erikrose): (In [29558]) Put CMFTestCase back in the buildout; apparently, it was necessary after all. (Why didn't the tests fail after I ran buildout without it?) Refs #9186. -- Ticket URL: http://dev.plone.org/plone/ticket/9186#comment:44 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: erikrose Type: PLIP| Status: reopened Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Comment(by davisagli): I looked into the FTP connection issue and filed a Zope bug at https://bugs.launchpad.net/zope2/+bug/418454 (it's an incompatibility between Zope's FTP server and a change in the asyncore module in Python 2.6). -- Ticket URL: http://dev.plone.org/plone/ticket/9186#comment:43 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: erikrose Type: PLIP| Status: reopened Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Comment(by alecm): (In [29329]) Add review for PLIP #9186 (refs #9186) -- Ticket URL: http://dev.plone.org/plone/ticket/9186#comment:42 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: erikrose Type: PLIP| Status: reopened Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Old description: '''Proposed by:''' Erik Rose[[BR]] '''Seconded by:''' (Step right up!) == The Problem == The Image type chooses the IDs of new objects differently than other types: rather than transforming the Title (My Dog Watches Me Eat becoming my-dog-watches-me-eat), they use the name of the uploaded file. This has several disadvantages: 1. Inconsistency with other types. 8.5 (yes, there was a half) out of 14 of our Plone user's group attendees today find the current behavior surprising or counterproductive. Only 1 actively prefers the current behavior. The rest don't see any problem in changing it. 1. Many common use cases involve images whose filenames are autogenerated and uninformative. All these cases result in URLs like `Picture%201.PNG`, which are uninformative, subjectively funny looking, and hard to remediate without first renaming and then re-uploading a large file: * Screenshots on a Mac come with titles like `Picture 1` and, because their lifetimes on disk are typically short, aren't often renamed. * Pictures from cameras look like `P1090404.JPG`. * Flickr images look like `3425573738_90e84302e8.jpg`. 1. When screenshots are routinely uploaded to the same folder (say, a site-wide `images` folder), everybody but the first uploader of `Picture 1.png` is met with an error—There is already an item named Picture 1.png in this folder.—and has to do a context switch back to another app to rename the file (which, if the user had good reason to name the local file Picture 1, is pretty intrusive). 1. The case of image extensions differs depending on platform. Windows tends to use capital `.JPG`; Mac, `.jpg`. Such inconsistency makes URLs hard to guess. 1. There's no other way in Plone, short of manually enabling short-name editing, to end up with capital letters in URLs. == The Proposal == * Have Images choose their IDs based on entered Titles, as with other types. * The Title field remains unrequired, thus maintaining happiness with uploads via WebDAV or FTP, which don't provide opportunity to enter a title. Choosing an image file should stick its name in the Title field via JS if that field was empty, thus effectively providing the current behavior as an option as well as showing the user what's about to happen. * On creation form submission, the object's ID is assigned as follows: * If the Title field is the same as the name of the uploaded file, the ID is the contents of the Title field, without going through the typical Title-field-normalization filter. This maintains the current behavior as an option. * If the Title field is different than the name of the uploaded file, the ID is the normal munged Title field contents. * ~~If browsers are awful and require file extensions in URLs~~ (which they don't), ~~compute them from the uploaded MIME type using the existing `guess_content_type()` machinery or something. This solves the inconsistency where some files say `.jpg`, others `.jpeg`, and still others `.JPG`.~~ == Addendum: the File type == P.S. Though this PLIP shouldn't succeed or fail based on this, we might also consider making a similar change to the behavior of the File type. New description: '''Proposed by:''' Erik Rose[[BR]] '''Seconded by:''' (Step right up!) == The Problem == The Image type chooses the IDs of new objects differently than other types: rather than transforming the Title (My Dog Watches Me Eat becoming my-dog-watches-me-eat), they use the name of the uploaded file. This has several disadvantages: 1. Inconsistency with other types. 8.5 (yes, there was a half) out of 14 of our Plone user's group attendees today find the current behavior surprising or counterproductive. Only 1 actively prefers the current behavior. The rest don't see any problem in changing it. 1. Many common use cases involve images whose filenames are autogenerated and uninformative. All these cases result in URLs like `Picture%201.PNG`, which are uninformative, subjectively funny looking, and hard to remediate without first renaming and then re-uploading a large file: * Screenshots on a Mac come with titles like `Picture 1` and, because their lifetimes on disk are typically short, aren't often renamed. * Pictures from cameras look like `P1090404.JPG`. * Flickr images look like `3425573738_90e84302e8.jpg`. 1. When screenshots are routinely uploaded to the same folder (say, a site-wide `images` folder), everybody but the first uploader of `Picture 1.png` is met with an
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: erikrose Type: PLIP| Status: closed Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: fixed Keywords: | +--- Changes (by erikrose): * status: assigned = closed * resolution: = fixed Comment: In [http://dev.plone.org/collective/changeset/94846 collective changeset 94846]: * Stopped errors about duplicate filenames even if the title is going to be used as the ID. * Fixed a failing test due to the uploaded file being at EOF to begin with. -- Ticket URL: http://dev.plone.org/plone/ticket/9186#comment:38 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: erikrose Type: PLIP| Status: reopened Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Changes (by esteele): * status: closed = reopened * resolution: fixed = Comment: I'll close PLIP tickets when they've been merged or rejected. Before this is considered ready for review, we'll need you to add a set of review instructions to the plips folder in the 4.0 buildout. Thanks. -- Ticket URL: http://dev.plone.org/plone/ticket/9186#comment:39 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: erikrose Type: PLIP| Status: assigned Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Comment(by erikrose): [https://dev.plone.org/collective/changeset/94438 Collective changeset 94438]: Refactored so I don't repeat myself anymore. Now `_setATCTFileContent` is parametrized by a `_should_set_id_to_filename` method in its subclasses, `ATFile` and `ATImage`. -- Ticket URL: http://dev.plone.org/plone/ticket/9186#comment:36 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: erikrose Type: PLIP| Status: assigned Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Comment(by erikrose): (In [28496]) Added buildout config for [https://dev.plone.org/old/plone/ticket/9186 image-ID-from-title PLIP]. Refs #9186. -- Ticket URL: http://dev.plone.org/plone/ticket/9186#comment:32 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: erikrose Type: PLIP| Status: assigned Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Comment(by alecm): I thought the consensus was Title field optional, if filled use title for the id (for images not files) otherwise use filename. No js. Am I misremembering? -- Ticket URL: http://dev.plone.org/plone/ticket/9186#comment:34 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: erikrose Type: PLIP| Status: assigned Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Comment(by erikrose): That sounds pretty good to me. The only downside is that you lose the present ability to upload an image, use the filename as the ID, and, at the same time, give it an unrelated Title—you'd have to leave Title blank when uploading, then come back and edit it. -- Ticket URL: http://dev.plone.org/plone/ticket/9186#comment:35 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: erikrose Type: PLIP| Status: assigned Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Changes (by erikrose): * status: new = assigned -- Ticket URL: http://dev.plone.org/plone/ticket/9186#comment:30 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: erikrose Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Changes (by yurj): * cc: yurj (added) Comment: JS should be used only to be more informative, we should not rely on it. We could provide a checkbox with [] Use the file name instead of the title for the image url This can leave room for people which likes to mantain file names. What if I change the title? The id will not be changed, so we will end up in inconsistencies again. Also, if you want to use webdav, you will upload a file and have no way to set the title to change the id, so the problem is not solved again. -- Ticket URL: http://dev.plone.org/plone/ticket/9186#comment:29 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Comment(by esteele): Approved by FWT vote. -- Ticket URL: http://dev.plone.org/plone/ticket/9186#comment:27 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Comment(by erikrose): Abstaining since this is my PLIP. -- Ticket URL: http://dev.plone.org/plone/ticket/9186#comment:24 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Old description: '''Proposed by:''' Erik Rose[[BR]] '''Seconded by:''' (Step right up!) == The Problem == The Image type chooses the IDs of new objects differently than other types: rather than transforming the Title (My Dog Watches Me Eat becoming my-dog-watches-me-eat), they use the name of the uploaded file. This has several disadvantages: 1. Inconsistency with other types. 8.5 (yes, there was a half) out of 14 of our Plone user's group attendees today find the current behavior surprising or counterproductive. Only 1 actively prefers the current behavior. The rest don't see any problem in changing it. 1. Many common use cases involve images whose filenames are autogenerated and uninformative. All these cases result in URLs like `Picture%201.PNG`, which are uninformative, subjectively funny looking, and hard to remediate without first renaming and then re-uploading a large file: * Screenshots on a Mac come with titles like `Picture 1` and, because their lifetimes on disk are typically short, aren't often renamed. * Pictures from cameras look like `P1090404.JPG`. * Flickr images look like `3425573738_90e84302e8.jpg`. 1. When screenshots are routinely uploaded to the same folder (say, a site-wide `images` folder), everybody but the first uploader of `Picture 1.png` is met with an error—There is already an item named Picture 1.png in this folder.—and has to do a context switch back to another app to rename the file (which, if the user had good reason to name the local file Picture 1, is pretty intrusive). 1. The case of image extensions differs depending on platform. Windows tends to use capital `.JPG`; Mac, `.jpg`. Such inconsistency makes URLs hard to guess. 1. There's no other way in Plone, short of manually enabling short-name editing, to end up with capital letters in URLs. == The Proposal == * Have Images choose their IDs based on entered Titles, as with other types. * Make the Title field required, as with other types. Choosing an image file should stick its name in the Title field via JS if that field was empty, thus effectively providing the current behavior as an option as well as showing the user what's about to happen. * ~~If browsers are awful and require file extensions in URLs~~ (which they don't), ~~compute them from the uploaded MIME type using the existing `guess_content_type()` machinery or something. This solves the inconsistency where some files say `.jpg`, others `.jpeg`, and still others `.JPG`.~~ == Addendum: the File type == P.S. Though this PLIP shouldn't succeed or fail based on this, we might also consider making a similar change to the behavior of the File type. New description: '''Proposed by:''' Erik Rose[[BR]] '''Seconded by:''' (Step right up!) == The Problem == The Image type chooses the IDs of new objects differently than other types: rather than transforming the Title (My Dog Watches Me Eat becoming my-dog-watches-me-eat), they use the name of the uploaded file. This has several disadvantages: 1. Inconsistency with other types. 8.5 (yes, there was a half) out of 14 of our Plone user's group attendees today find the current behavior surprising or counterproductive. Only 1 actively prefers the current behavior. The rest don't see any problem in changing it. 1. Many common use cases involve images whose filenames are autogenerated and uninformative. All these cases result in URLs like `Picture%201.PNG`, which are uninformative, subjectively funny looking, and hard to remediate without first renaming and then re-uploading a large file: * Screenshots on a Mac come with titles like `Picture 1` and, because their lifetimes on disk are typically short, aren't often renamed. * Pictures from cameras look like `P1090404.JPG`. * Flickr images look like `3425573738_90e84302e8.jpg`. 1. When screenshots are routinely uploaded to the same folder (say, a site-wide `images` folder), everybody but the first uploader of `Picture 1.png` is met with an error—There is already an item named Picture 1.png in this folder.—and has to do a context switch back to another app to rename the file (which, if the user had good reason to name the local file Picture 1, is pretty intrusive). 1. The case of image extensions differs depending on platform. Windows tends to use capital `.JPG`; Mac, `.jpg`. Such inconsistency makes URLs hard to guess. 1. There's no other way in Plone, short of manually enabling short-name editing, to end up with capital letters in URLs. == The Proposal == * Have
[PLIP-Advisories] Re: [Plone] #9186: Set Image IDs from Title field
#9186: Set Image IDs from Title field +--- Reporter: erikrose|Owner: Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Description changed by erikrose: Old description: '''Proposed by:''' Erik Rose[[BR]] '''Seconded by:''' (Step right up!) == The Problem == The Image type chooses the IDs of new objects differently than other types: rather than transforming the Title (My Dog Watches Me Eat becoming my-dog-watches-me-eat), they use the name of the uploaded file. This has several disadvantages: 1. Inconsistency with other types. 8.5 (yes, there was a half) out of 14 of our Plone user's group attendees today find the current behavior surprising or counterproductive. Only 1 actively prefers the current behavior. The rest don't see any problem in changing it. 1. Many common use cases involve images whose filenames are autogenerated and uninformative. All these cases result in URLs like `Picture%201.PNG`, which are uninformative, subjectively funny looking, and hard to remediate without first renaming and then re-uploading a large file: * Screenshots on a Mac come with titles like `Picture 1` and, because their lifetimes on disk are typically short, aren't often renamed. * Pictures from cameras look like `P1090404.JPG`. * Flickr images look like `3425573738_90e84302e8.jpg`. 1. When screenshots are routinely uploaded to the same folder (say, a site-wide `images` folder), everybody but the first uploader of `Picture 1.png` is met with an error—There is already an item named Picture 1.png in this folder.—and has to do a context switch back to another app to rename the file (which, if the user had good reason to name the local file Picture 1, is pretty intrusive). 1. The case of image extensions differs depending on platform. Windows tends to use capital `.JPG`; Mac, `.jpg`. Such inconsistency makes URLs hard to guess. 1. There's no other way in Plone, short of manually enabling short-name editing, to end up with capital letters in URLs. == The Proposal == * Have Images choose their IDs based on entered Titles, as with other types. * The Title field remains unrequired. Choosing an image file should stick its name in the Title field via JS if that field was empty, thus effectively providing the current behavior as an option as well as showing the user what's about to happen. * On creation form submission, the object's ID is assigned as follows: * If the Title field is the same as the name of the uploaded file, the ID is the contents of the Title field, without going through the typical Title-field-normalization filter. This maintains the current behavior as an option. * If the Title field is different than the name of the uploaded file, the ID is the normal munged Title field contents. * ~~If browsers are awful and require file extensions in URLs~~ (which they don't), ~~compute them from the uploaded MIME type using the existing `guess_content_type()` machinery or something. This solves the inconsistency where some files say `.jpg`, others `.jpeg`, and still others `.JPG`.~~ == Addendum: the File type == P.S. Though this PLIP shouldn't succeed or fail based on this, we might also consider making a similar change to the behavior of the File type. New description: '''Proposed by:''' Erik Rose[[BR]] '''Seconded by:''' (Step right up!) == The Problem == The Image type chooses the IDs of new objects differently than other types: rather than transforming the Title (My Dog Watches Me Eat becoming my-dog-watches-me-eat), they use the name of the uploaded file. This has several disadvantages: 1. Inconsistency with other types. 8.5 (yes, there was a half) out of 14 of our Plone user's group attendees today find the current behavior surprising or counterproductive. Only 1 actively prefers the current behavior. The rest don't see any problem in changing it. 1. Many common use cases involve images whose filenames are autogenerated and uninformative. All these cases result in URLs like `Picture%201.PNG`, which are uninformative, subjectively funny looking, and hard to remediate without first renaming and then re-uploading a large file: * Screenshots on a Mac come with titles like `Picture 1` and, because their lifetimes on disk are typically short, aren't often renamed. * Pictures from cameras look like `P1090404.JPG`. * Flickr images look like `3425573738_90e84302e8.jpg`. 1. When screenshots are routinely uploaded to the same folder (say, a site-wide `images` folder), everybody but the first uploader of `Picture 1.png` is met with an error—There is already an item named Picture 1.png in this folder.—and has to do a context switch back
