| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 28 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 51:22:10 |
| Calls: | 422 |
| Files: | 1,025 |
| Messages: | 90,551 |
With every adult operating system, you can name the photos coming out of
the mobile device - except with the brain-dead dumb-terminal iOS devices.
On 22.04.2025 05:05, Marion wrote:
With every adult operating system, you can name the photos coming out of the mobile device - except with the brain-dead dumb-terminal iOS devices.
There is a very simple solution: don't use iPhones but phones with
an "adult operating system”.
On Apr 22, 2025, Herbert Kleebauer wrote
(in article <vu7b6h$3u07r$1@dont-email.me>):
On 22.04.2025 05:05, Marion wrote:
With every adult operating system, you can name the photos coming out of >> > the mobile device - except with the brain-dead dumb-terminal iOS devices. >>There is a very simple solution: don't use iPhones but phones with
an "adult operating system”.
Then what would Arlen spend his boundless time on? What else could he write a few trillion words about every other week?
On 2025-04-22, Bill W <nothing@nowhere.com> wrote:
On Apr 22, 2025, Herbert Kleebauer wrote
(in article <vu7b6h$3u07r$1@dont-email.me>):
On 22.04.2025 05:05, Marion wrote:
With every adult operating system, you can name the photos coming out of >>>> the mobile device - except with the brain-dead dumb-terminal iOS devices. >>>There is a very simple solution: don't use iPhones but phones with
an "adult operating system”.
Then what would Arlen spend his boundless time on? What else could he write a
few trillion words about every other week?
BINGO
With every adult operating system, you can name the photos coming out of
the mobile device - except with the brain-dead dumb-terminal iOS devices.
There is a very simple solution: don't use iPhones but phones with
an "adult operating system".
Not to mention that before last week he was whining that it was impossible to get to the iOS DCIM folder. Because "walled garden".
Now that we have PROVED to him that it easy to do, he has to whine about file names? What does he expect? Picture of Arlen at the beach.jpg? IMG-3769275.jpg is a "better" name?
And look how long it took him to accept the FACT that the iOS SMB server worked! He admitted to "googling furiously" to prove that we were wrong. It never occurred to him to DL the fucking app and TRY IT!
NOW he is whining about not getting a drive letter assigned in Windows when he
connects to the iOS SMB server. But of course it works when conecting to Android. As if the server you are connecting to controls the drive letter in the client (Windows in this case).
On Tue, 22 Apr 2025 16:36:03 +0000, Tyrone wrote :
Not to mention that before last week he was whining that it was impossible to
get to the iOS DCIM folder. Because "walled garden".
Please don't call the Apple ecosystem a "walled garden" when it's really
more like a subterranean cavern, unlike the real world in almost every way.
Now that we have PROVED to him that it easy to do, he has to whine about file
names? What does he expect? Picture of Arlen at the beach.jpg?
IMG-3769275.jpg is a "better" name?
I wonder if you realize how many millions of people have "whined" about the idiotic way Apple iOS does the file naming on their photos files Tyrone?
And look how long it took him to accept the FACT that the iOS SMB server
worked! He admitted to "googling furiously" to prove that we were wrong. It >> never occurred to him to DL the fucking app and TRY IT!
First off, I didn't say it didn't work - I said I didn't think nix-based systems allowed 3rd-party apps to bind to privileged ports, and, I said
that I couldn't find any documentation saying iOS could - and - let's be clear - neither could you - and neither could anyone find that
documentation.
So the only way to prove that it worked was to try it out, but what you
don't understand is believing you Apple trolls is like believing that
Charles Manson didn't do it - even as many still insist he's innocent.
It's a shock that you Apple trolls have ever been right, as you Apple
trolls still insist on imaginary iOS functionality day in and day out.
Do I need to list all the claims Jolly Roger & nospam have made for
example, where even in the past week Jolly Roger insisted iTunes backs up
his IPA's off of his iOS device when that is impossible.
NOW he is whining about not getting a drive letter assigned in Windows when he
connects to the iOS SMB server. But of course it works when conecting to
Android. As if the server you are connecting to controls the drive letter in >> the client (Windows in this case).
I supplied images. I tried it. You didn't try it. You're just guessing.
What you're suggesting is to use a *different* mapping mechanism.
You don't even realize the discrepancy.
It might work with that different mapping.
But that's now how it has to work with WebDAV.
For the record, I will try the mapping using the *DIFFERENT* mechanism that you suggest, but that doesn't change the fact that "net use" didn't do it.
(You'd think they "should" give the same results but they well may not.)
I just need to find people who know more than I do, that's all.
On Tue, 22 Apr 2025 07:58:40 +0200, Herbert Kleebauer wrote :
With every adult operating system, you can name the photos coming out of >>> the mobile device - except with the brain-dead dumb-terminal iOS devices.
There is a very simple solution: don't use iPhones but phones with
an "adult operating system".
That's really not the solution as it's the same when I hear people telling immigrants to go back where they came from if they don't like how things
are in the United States.
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.
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.
On Tue, 22 Apr 2025 16:36:03 +0000, Tyrone wrote :
And look how long it took him to accept the FACT that the iOS SMB
server worked! He admitted to "googling furiously" to prove that we
were wrong. It never occurred to him to DL the fucking app and TRY
IT!
First off, I didn't say it didn't work
For example, I've been able to easily transfer files from Linux to iOS over WiFi using the SMB server inside of the freeware WiFi HD program using the smbclient inside of Linux.
Tell me, Jolly Roger & nospam, how do you accomplish /that/ with your
vaunted Apple solutions?
On 2025-04-22, Tyrone <none@none.none> wrote:
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.
That's *exactly* what this is: he's desperately trying to move on from
his embarrassing file transfer troll to a different troll.
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.
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.
Does anyone here have experience with "photofs" fixing photo naming? https://jeromebelleman.gitlab.io/posts/filesystems/photofs/
With every adult operating system, you can name the photos coming out of
the mobile device - except with the brain-dead dumb-terminal iOS devices.
Since Apple only hires high school dropouts to define their file-naming conventions, it can apparently be used to map Apple's sophomoric DCIM file-naming conventions to something that the modern world uses.
Seriously though, if you've never looked at the brain-dead way Apple iOS devices name photos, you'll never understand how bad Apple coders are.
It's almost as if nothing works in iOS the way it should unless you log
into Apple's Cupertino mainframes every moment of your life.
Just to get a reasonable name out of each of your photos on Apple's dumb terminal iOS devices (seriously - look at the stupid names Apple uses).
Well, apparently, PhotoFS is to the rescue, perhaps fixing Apple's dumb-terminal brain-dead photo-naming conventions that nobody ever uses.
PhotoFS, is, apparently, a FUSE (Filesystem in Userspace) filesystem that presents your photo & video collection as a structured file system based on their metadata instead of how Apple's dumb-terminal devices display them.
PhotoFS creates a virtual filesystem where directories and filenames are dynamically generated based on the EXIF and XMP metadata found within your image and video files.
Unfortunately, there's only so much you can do to fix Apple's absurd dumb-terminal file-naming conventions, as PhotoFS is a read-only
filesystem. It does not modify your original files. It only presents a different view of your existing collection.
In essence, PhotoFS offers a clever way to navigate and interact with your media library by leveraging the rich information already embedded within
your files to create a more meaningful and searchable file system
structure.
Hence, I ask, does anyone here have experience with "photofs" photo naming?
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.
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.
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.
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.
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...
On 2025-04-23, Alan <nuh-uh@nope.com> wrote:
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...
It could be that the IMG_### files were created before Apple switched to UUIDs.
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.
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.
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.
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.
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.
:-)
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.
;-)
doesn't know anything about anything
Seems they are using "Universally Unique IDentifiers" (UUIDs) (rfc9562)
as file names:
https://datatracker.ietf.org/doc/html/rfc9562
Hope that wasn't meant seriously. A smartphone is not a lifetime device,
it is replaced every few years. And if you are not happy with your
current device, choose a different type next time.
If an immigrant could decide every 3 years in which country he wants
to live, then nothing is wrong with the advice: try a different country
next time if you are not happy with the USA.
[3 quoted lines suppressed]
Sorry, but I don't understand your problem. You don't like the file-naming
on your iPhone. There are two easy solutions:
- don't use an iPhone or
- rename the file to names you like
I suppose you already transfer the pictures to a PC for a backup.
Rename the pictures on the PC (there are many renaming tools available
or use a simple batch to do it). Select the pictures you want/need on
your iPhone and copy them back with the new names.
On Wed, 23 Apr 2025 08:32:23 +0200, Herbert Kleebauer wrote :
Seems they are using "Universally Unique IDentifiers" (UUIDs) (rfc9562)
as file names:
https://datatracker.ietf.org/doc/html/rfc9562
Hi Herbert,
You're intelligent, so I can converse with you on a level that is far and above that which the common Apple trolls can possibly comprehend.
IMHO, most people don't understand iOS is designed, by Apple, to be nothing more than a dumb terminal - which *requires* logging into Apple's matrix servers to do the simplest of the most basic of the most common things.
I do understand that. Not only because I'm intelligent.
But because I have plenty of iOS devices.
And therefore, I see what they do with respect to image naming conventions.
And I point out this starkly obvious evidence you, yourself dug up, that shows iOS is designed as nothing more than a (very) dumb terminal.
Apple's iOS is the only common consumer operating system that is designed
to badly that it can't even use sensible consumer-friendly image names.
While I'm well aware that iOS is nothing more than a (very) dumb terminal,
I, for one, do not wish to endure Apple's grotesque naming conventions.
Which is the reason, after all, for the technical question I posed herein.
On Wed, 23 Apr 2025 22:31:32 +0000, Tyrone wrote :
doesn't know anything about anything
Since r.p.d is involved, it behooves us to *UNDERSTAND* how dumb iOS is
when it comes to the ability for iOS to use sane image-naming conventions.
The senseless image naming is yet another obvious piece of evidence that
iOS is designed to be nothing more than a (very) dumb terminal, and you
Apple trolls actually agree since you're so desperate to excuse the proof.
Not only because I'm intelligent
On Apr 23, 2025, Arlen wrote
(in article<vucep0$23sn$1@nnrp.usenet.blueworldhosting.com>):
Not only because I'm intelligent
It seems to me that your “intelligence” is deeply rooted in meth or ketamine or both.
On 2025-04-24 09:14, Bill W wrote:
On Apr 23, 2025, Arlen wrote
(in article<vucep0$23sn$1@nnrp.usenet.blueworldhosting.com>):
Not only because I'm intelligent
It seems to me that your “intelligence” is deeply rooted in meth or ketamine or both.
Nah...
Arlen is a perfect example of the idea that those who are most certain
about a subject are almost always those who actually understand it least.
On Apr 24, 2025, Alan wrote
(in article <vudpn4$1vtst$1@dont-email.me>):
On 2025-04-24 09:14, Bill W wrote:
On Apr 23, 2025, Arlen wrote
(in article<vucep0$23sn$1@nnrp.usenet.blueworldhosting.com>):
Not only because I'm intelligent
It seems to me that your “intelligence” is deeply rooted in meth or
ketamine or both.
Nah...
Arlen is a perfect example of the idea that those who are most certain
about a subject are almost always those who actually understand it least.
He expends a lot of energy proving that over and over. I get tired trying to get through his logorrheic posts. And I hate iOS (I have an iPad and iPhone), but still can’t understand his purpose. There is good and bad to every OS out there. You either work around what you just can’t stomach, or drop that OS completely. Or, as others have said, just rename those photos...
