Re: Does anyone here have experience with "photofs" fixing photo naming?

On 2025-04-23 10:47, Tyrone wrote:

On Apr 23, 2025 at 12:31:47 PM EDT, "Alan" <nuh-uh@nope.com> wrote:

On 2025-04-22 15:35, Tyrone wrote:

On Apr 22, 2025 at 5:59:17 PM EDT, "Tyrone" <none@none.none> wrote:
>

And what exactly is the "decent name" you get from Apple? On my
Macs and my iCloud-connected Windows PCs, I get names like
"IMG_4737.jpg".  Why is "IMG_4737.jpg" a better name than
"5C297223-793B-4508-A22F-BC319105026B.jpg"?  Both are totally
arbitrary names.  Both are totally meaningless.

>
It just hit me why Apple uses these file names for photos. Being a
programmer (for 40 years) it is obvious that those are all Hex
digits. 8 digits-4 digits-4 digits-4 digits-12 digits. Letters
between A and F. That they are broken up by dashes probably has
some context.
>
The file names have to be absolutely unique so that MY files don't
get overwritten by someone else's files in iCloud.  And vice-versa.
>
Apple is storing billions of photos.  The worst thing that could
happen is that files get crossed.

>
Where does Apple use long file names like that?
>
I've never seen any on any of my devices.

 
In the DCIM folder.  You can see it using the iOS SMB Server. One of
the shares it creates is for the DCIM photos folder.

>
Ah! I'd not seen that before.
>
I'm wondering why some have those names and some have the shorter
"IMG_###.jpg/heic" form...