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

On Apr 22, 2025 at 12:29:22 PM EDT, "Marion" <marion@facts.com> wrote:

Just to let you know, other adults on the Apple operating system newsgroups
have also complained about the file-naming conventions of iOS which
basically force you to log into Apple's mainframes to get decent names.

What exactly is the problem?  It's just a file name.  Once you copy it over
from DCIM, feel free to change it to whatever you want.

BTW, last week you didn't even know that you COULD connect to DCIM on any
iDevice. You denied it for days. You called us all liars. Once we
bitch-slapped you out of your "privileged ports" fantasy land and into
reality, you FINALLY accepted the facts.  

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.

And one is no harder to change than the other.

And what makes you think Apple has "mainframes"?  Much more likely - not to
mention cheaper/easier to program and maintain - would be racks of
load-balanced Mac Minis. Apple probably has their own internal hardware
configuration of Mac servers running the entire show. All running MacOS (Unix)
of course. Exactly how much horsepower do you think is needed to store photos
and forward text messages/emails?

Sounds to me like you just need SOMETHING new to complain about, now that you
have been PROVEN WRONG about (1) the Files app and (2) the iOS SMB Server. 
Even worse than that, you had to admit that iOS can do something that Android
can't do.