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

On Apr 23, 2025 at 6:25:41 PM EDT, "Alan" <nuh-uh@nope.com> wrote:

On 2025-04-23 15:18, Tyrone wrote:

On Apr 23, 2025 at 4:18:08 PM EDT, "Alan" <nuh-uh@nope.com> wrote:
 

On 2025-04-23 13:11, Jolly Roger wrote:

On 2025-04-23, Alan <nuh-uh@nope.com> wrote:

On 2025-04-23 12:04, Jolly Roger wrote:

On 2025-04-23, Alan <nuh-uh@nope.com> wrote:

 
I'm wondering why some have those names and some have the shorter
"IMG_###.jpg/heic" form...

 
It could be that the IMG_### files were created before Apple switched to
UUIDs.

 
I don't think that's it...
 
Let me start up the LAN Drive software again.
 
Yeah... ...looking at recent files on "DCIM", I see files mixed in
together: UUID names and IMG_#### names.
 
The first two with UUID names are files imported from others sources and
then the IMG_#### named files that follow are pictures (and screenshots
and screen recordings) taken on my iPhone.
 
That seems to be a theme: items taken on my iPhone have IMG_#### names
and items from other sources...
 
...INCLUDING FROM MY OWN OTHER iOS DEVICES...
 
...get UUID names.

 
That makes sense, because photos imported from other devices definitely
need to have universally unique names to avoid conflicts with photos
that originated on the device.
 

 
My thought exactly.
 
:-)

 
Ahh, I get it now.  I was ONLY seeing the very long files names, because I am
looking at DCIM on an iPad.  ALL of these files came from iCloud, because I
rarely take a picture using the iPad.
 
So to test, I took a picture on my iPad. The new file is indeed IMG_0089.HEIC.
 
So mystery solved, and there is a VERY good reason for the long file names.

 
Yeah.
 
It's almost like Apple knows what they're doing.
 
;-)

And again, its almost like Arlen doesn't know anything about anything. Look at
how ridiculous his original post is in this thread. Trolling along as usual.