Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #148008 > unrolled thread
| Started by | Marion <marion@facts.com> |
|---|---|
| First post | 2025-04-22 02:51 +0000 |
| Last post | 2025-04-22 15:40 -0700 |
| Articles | 18 on this page of 38 — 8 participants |
Back to article view | Back to comp.mobile.android
Does anyone here have experience with "photofs"? Marion <marion@facts.com> - 2025-04-22 02:51 +0000
Does anyone here have experience with "photofs" fixing photo naming? Marion <marion@facts.com> - 2025-04-22 03:05 +0000
Re: Does anyone here have experience with "photofs" fixing photo naming? Herbert Kleebauer <klee@unibwm.de> - 2025-04-22 07:58 +0200
Re: Does anyone here have experience with "photofs" fixing photo naming? Bill W <nothing@nowhere.com> - 2025-04-22 10:36 -0500
Re: Does anyone here have experience with "photofs" fixing photo naming? Jolly Roger <jollyroger@pobox.com> - 2025-04-22 15:56 +0000
Re: Does anyone here have experience with "photofs" fixing photo naming? Tyrone <none@none.none> - 2025-04-22 16:36 +0000
Re: Does anyone here have experience with "photofs" fixing photo naming? Marion <marion@facts.com> - 2025-04-22 16:50 +0000
Re: Does anyone here have experience with "photofs" fixing photo naming? Alan <nuh-uh@nope.com> - 2025-04-22 10:32 -0700
Re: Does anyone here have experience with "photofs" fixing photo naming? Jolly Roger <jollyroger@pobox.com> - 2025-04-22 21:24 +0000
Re: Does anyone here have experience with "photofs" fixing photo naming? Marion <marion@facts.com> - 2025-04-22 16:29 +0000
Re: Does anyone here have experience with "photofs" fixing photo naming? David <BoaterDave@hotmail.co.uk> - 2025-04-22 21:27 +0100
Re: Does anyone here have experience with "photofs" fixing photo naming? Herbert Kleebauer <klee@unibwm.de> - 2025-04-22 22:34 +0200
Re: Does anyone here have experience with "photofs" fixing photo naming? Marion <marion@facts.com> - 2025-04-24 04:55 +0000
Re: Does anyone here have experience with "photofs" fixing photo naming? Tyrone <none@none.none> - 2025-04-22 21:59 +0000
Re: Does anyone here have experience with "photofs" fixing photo naming? Jolly Roger <jollyroger@pobox.com> - 2025-04-22 22:05 +0000
Re: Does anyone here have experience with "photofs" fixing photo naming? Tyrone <none@none.none> - 2025-04-22 22:14 +0000
Re: Does anyone here have experience with "photofs" fixing photo naming? Tyrone <none@none.none> - 2025-04-22 22:35 +0000
Re: Does anyone here have experience with "photofs" fixing photo naming? Herbert Kleebauer <klee@unibwm.de> - 2025-04-23 08:32 +0200
Re: Does anyone here have experience with "photofs" fixing photo naming? Marion <marion@facts.com> - 2025-04-24 04:30 +0000
Re: Does anyone here have experience with "photofs" fixing photo naming? Alan <nuh-uh@nope.com> - 2025-04-23 22:12 -0700
Re: Does anyone here have experience with "photofs" fixing photo naming? Bill W <nothing@nowhere.com> - 2025-04-24 11:14 -0500
Re: Does anyone here have experience with "photofs" fixing photo naming? Alan <nuh-uh@nope.com> - 2025-04-24 09:43 -0700
Re: Does anyone here have experience with "photofs" fixing photo naming? Bill W <nothing@nowhere.com> - 2025-04-24 12:55 -0500
Re: Does anyone here have experience with "photofs" fixing photo naming? Alan <nuh-uh@nope.com> - 2025-04-24 11:12 -0700
Re: Does anyone here have experience with "photofs" fixing photo naming? Alan <nuh-uh@nope.com> - 2025-04-23 09:31 -0700
Re: Does anyone here have experience with "photofs" fixing photo naming? Tyrone <none@none.none> - 2025-04-23 17:47 +0000
Re: Does anyone here have experience with "photofs" fixing photo naming? Alan <nuh-uh@nope.com> - 2025-04-23 11:03 -0700
Re: Does anyone here have experience with "photofs" fixing photo naming? Jolly Roger <jollyroger@pobox.com> - 2025-04-23 19:04 +0000
Re: Does anyone here have experience with "photofs" fixing photo naming? Alan <nuh-uh@nope.com> - 2025-04-23 13:08 -0700
Re: Does anyone here have experience with "photofs" fixing photo naming? Jolly Roger <jollyroger@pobox.com> - 2025-04-23 20:11 +0000
Re: Does anyone here have experience with "photofs" fixing photo naming? Alan <nuh-uh@nope.com> - 2025-04-23 13:18 -0700
Re: Does anyone here have experience with "photofs" fixing photo naming? Tyrone <none@none.none> - 2025-04-23 22:18 +0000
Re: Does anyone here have experience with "photofs" fixing photo naming? Alan <nuh-uh@nope.com> - 2025-04-23 15:25 -0700
Re: Does anyone here have experience with "photofs" fixing photo naming? Tyrone <none@none.none> - 2025-04-23 22:31 +0000
Re: Does anyone here have experience with "photofs" fixing photo naming? Marion <marion@facts.com> - 2025-04-24 04:22 +0000
Re: Does anyone here have experience with "photofs" fixing photo naming? Alan <nuh-uh@nope.com> - 2025-04-23 22:15 -0700
Re: Does anyone here have experience with "photofs" fixing photo naming? candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-04-23 21:50 +0000
Re: Does anyone here have experience with "photofs" fixing photo naming? Alan <nuh-uh@nope.com> - 2025-04-22 15:40 -0700
Page 2 of 2 — ← Prev page 1 [2]
| From | Bill W <nothing@nowhere.com> |
|---|---|
| Date | 2025-04-24 11:14 -0500 |
| Subject | Re: Does anyone here have experience with "photofs" fixing photo naming? |
| Message-ID | <vudo0i$1ua7a$1@dont-email.me> |
| In reply to | #148058 |
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.
[toc] | [prev] | [next] | [standalone]
| From | Alan <nuh-uh@nope.com> |
|---|---|
| Date | 2025-04-24 09:43 -0700 |
| Subject | Re: Does anyone here have experience with "photofs" fixing photo naming? |
| Message-ID | <vudpn4$1vtst$1@dont-email.me> |
| In reply to | #148068 |
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.
[toc] | [prev] | [next] | [standalone]
| From | Bill W <nothing@nowhere.com> |
|---|---|
| Date | 2025-04-24 12:55 -0500 |
| Subject | Re: Does anyone here have experience with "photofs" fixing photo naming? |
| Message-ID | <vudttu$23b92$1@dont-email.me> |
| In reply to | #148069 |
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...
[toc] | [prev] | [next] | [standalone]
| From | Alan <nuh-uh@nope.com> |
|---|---|
| Date | 2025-04-24 11:12 -0700 |
| Subject | Re: Does anyone here have experience with "photofs" fixing photo naming? |
| Message-ID | <vuduu9$240aq$13@dont-email.me> |
| In reply to | #148080 |
On 2025-04-24 10:55, Bill W wrote: > 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... > Or just use the excellent tools that iOS (and macOS) provide to find photos by using the metadata. :-)
[toc] | [prev] | [next] | [standalone]
| From | Alan <nuh-uh@nope.com> |
|---|---|
| Date | 2025-04-23 09:31 -0700 |
| Subject | Re: Does anyone here have experience with "photofs" fixing photo naming? |
| Message-ID | <vub4lk$3e2ab$1@dont-email.me> |
| In reply to | #148038 |
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.
[toc] | [prev] | [next] | [standalone]
| From | Tyrone <none@none.none> |
|---|---|
| Date | 2025-04-23 17:47 +0000 |
| Subject | Re: Does anyone here have experience with "photofs" fixing photo naming? |
| Message-ID | <ec6cnYjmXqtbupT1nZ2dnZfqnPGdnZ2d@supernews.com> |
| In reply to | #148044 |
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.
[toc] | [prev] | [next] | [standalone]
| From | Alan <nuh-uh@nope.com> |
|---|---|
| Date | 2025-04-23 11:03 -0700 |
| Subject | Re: Does anyone here have experience with "photofs" fixing photo naming? |
| Message-ID | <vuba2g$3kpek$1@dont-email.me> |
| In reply to | #148045 |
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...
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2025-04-23 19:04 +0000 |
| Subject | Re: Does anyone here have experience with "photofs" fixing photo naming? |
| Message-ID | <m6sru1Fuc89U1@mid.individual.net> |
| In reply to | #148046 |
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. -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
| From | Alan <nuh-uh@nope.com> |
|---|---|
| Date | 2025-04-23 13:08 -0700 |
| Subject | Re: Does anyone here have experience with "photofs" fixing photo naming? |
| Message-ID | <vubhbd$3l2ga$1@dont-email.me> |
| In reply to | #148047 |
On 2025-04-23 12:04, Jolly Roger wrote: > 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. > 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. And and just to tweak Arlen, one of the pictures that I happened to look at shows the BMW 135i he claims I don't drive... ...and the 1998 RF98-2 Van Diemen Honda Formula F he claims I don't race! <https://drive.google.com/file/d/1smiW1xOAcGxuW0Cgnc2AWMEnhccNn8LY/view?usp=share_link> 😎
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2025-04-23 20:11 +0000 |
| Subject | Re: Does anyone here have experience with "photofs" fixing photo naming? |
| Message-ID | <m6svr9Fet6U1@mid.individual.net> |
| In reply to | #148048 |
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. -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
| From | Alan <nuh-uh@nope.com> |
|---|---|
| Date | 2025-04-23 13:18 -0700 |
| Subject | Re: Does anyone here have experience with "photofs" fixing photo naming? |
| Message-ID | <vubhu0$3l2ga$2@dont-email.me> |
| In reply to | #148049 |
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. :-)
[toc] | [prev] | [next] | [standalone]
| From | Tyrone <none@none.none> |
|---|---|
| Date | 2025-04-23 22:18 +0000 |
| Subject | Re: Does anyone here have experience with "photofs" fixing photo naming? |
| Message-ID | <yv-dnS07LarM-pT1nZ2dnZfqn_WdnZ2d@supernews.com> |
| In reply to | #148050 |
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.
[toc] | [prev] | [next] | [standalone]
| From | Alan <nuh-uh@nope.com> |
|---|---|
| Date | 2025-04-23 15:25 -0700 |
| Subject | Re: Does anyone here have experience with "photofs" fixing photo naming? |
| Message-ID | <vubpd5$2d5e$1@dont-email.me> |
| In reply to | #148052 |
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. ;-)
[toc] | [prev] | [next] | [standalone]
| From | Tyrone <none@none.none> |
|---|---|
| Date | 2025-04-23 22:31 +0000 |
| Subject | Re: Does anyone here have experience with "photofs" fixing photo naming? |
| Message-ID | <n12dnTiu4_DZ95T1nZ2dnZfqnPednZ2d@supernews.com> |
| In reply to | #148053 |
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.
[toc] | [prev] | [next] | [standalone]
| From | Marion <marion@facts.com> |
|---|---|
| Date | 2025-04-24 04:22 +0000 |
| Subject | Re: Does anyone here have experience with "photofs" fixing photo naming? |
| Message-ID | <vucean$ec0$1@nnrp.usenet.blueworldhosting.com> |
| In reply to | #148054 |
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. Bear in mind that my premise is not only that Apple coders are the bizarre equivalent of high-school dropouts, but that the proof that Apple designs the iOS device as a brain-dead dumb terminal is inherent in Apple's absurdly unfriendly non-customer-centric ridiculous image file naming. You Apple trolls can fabricate all the lame excuses in the world for why Apple designed the iOS operating system as a dumb terminal OS, but all your preposterous excuses don't change the fact no other operating system in the world forces its users to endure the grotesque naming conventions of Apple. The fact remains iOS creates ludicrously preposterous file names, and, iOS is so brain dead of a dumb terminal, that you can't change their default. The fact iOS is a dumb terminal is easily shown in this farcical reality. -- It's no longer shocking how little Apple trolls understand of iOS.
[toc] | [prev] | [next] | [standalone]
| From | Alan <nuh-uh@nope.com> |
|---|---|
| Date | 2025-04-23 22:15 -0700 |
| Subject | Re: Does anyone here have experience with "photofs" fixing photo naming? |
| Message-ID | <vuche6$s06m$1@dont-email.me> |
| In reply to | #148057 |
On 2025-04-23 21:22, Marion wrote: > 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. No. It's a simple naming convention... ...because the images are created with a surfeit of metadata, so you don't NEED to use clever naming conventions.
[toc] | [prev] | [next] | [standalone]
| From | candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> |
|---|---|
| Date | 2025-04-23 21:50 +0000 |
| Subject | Re: Does anyone here have experience with "photofs" fixing photo naming? |
| Message-ID | <slrn100ini3.2n3a6.candycanearter07@candydeb.host.invalid> |
| In reply to | #148038 |
Tyrone <none@none.none> wrote at 22:35 this Tuesday (GMT): > 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. At least that format would give you 16^32 different files, or 3.4e38. Excluding any possibly restricted filenames, that is still a lot. -- user <candycane> is generated from /dev/urandom
[toc] | [prev] | [next] | [standalone]
| From | Alan <nuh-uh@nope.com> |
|---|---|
| Date | 2025-04-22 15:40 -0700 |
| Subject | Re: Does anyone here have experience with "photofs" fixing photo naming? |
| Message-ID | <vu95sg$1gtg2$5@dont-email.me> |
| In reply to | #148009 |
On 2025-04-21 20:05, Marion wrote: > 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? Riiiiiiight. It's "brain-dead" to name images sequentially... ...when they have all this metadata associated with them: Aperture Value: 1.356 Brightness Value: -1.496 Color Space: Uncalibrated CompositeImage: 2 Date Time Digitized: Mar 24, 2025 at 18:22:09 Date Time Original: Mar 24, 2025 at 18:22:09 Exif Version: 2.3.2 Exposure Bias Value: 0 Exposure Mode: Auto exposure Exposure Program: Normal program Exposure Time: 1/20 Flash: Off, did not fire FNumber: 1.6 Focal Length: 5.96 Focal Length In 35mm Film: 52 Photographic Sensitivity (ISO): 640 Lens Make: Apple Lens Model: iPhone 16 back dual wide camera 5.96mm f/1.6 Lens Specification: 2.22, 5.96, 1.6, 2.2 Metering Mode: Pattern Time Zone for Modification Date: -07:00 Time Zone for Digitized Date: -07:00 Time Zone for Original Date: -07:00 Pixel X Dimension: 4,032 Pixel Y Dimension: 3,024 Scene Type: A directly photographed image Sensing Method: One-chip color area sensor Shutter Speed Value: 1/20 Subject Area: 2,015, 1,507, 1,106, 662 Sub-second Time Digitized: 505 Sub-second Time Original: 505 White Balance: Auto white balance And this: Altitude: 27.76 m (91.07 ft) Altitude Reference: above sea level Date Stamp: Mar 25, 2025 Destination Bearing: 68.77 Destination Bearing Reference: Magnetic direction Horizontal Positioning Error: 11.81 Image Direction: 68.77 Image Direction Reference: Magnetic north Latitude: <redacted> Longitude: <redacted> Speed: 0.3 Speed Reference: Kilometers per hour Time Stamp: 01:22:07 UTC Oh, and this: Date Time: Mar 24, 2025 at 18:22:09 Host Computer: iPhone 16 Make: Apple Model: iPhone 16 Orientation: 6 (Rotated 90° CCW) Resolution Unit: inches Software: 18.3 Tile Length: 512 Tile Width: 512 X Resolution: 72 Y Resolution: 72 How could someone EVER hope to search for a file without a tool like "photofs"? LOL!
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | comp.mobile.android
csiph-web