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

Path	csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From	Jolly Roger <jollyroger@pobox.com>
Newsgroups	comp.mobile.android, misc.phone.mobile.iphone, rec.photo.digital
Subject	Re: Does anyone here have experience with "photofs" fixing photo naming?
Date	23 Apr 2025 19:04:33 GMT
Organization	People for the Ethical Treatment of Pirates
Lines	44
Message-ID	<m6sru1Fuc89U1@mid.individual.net> (permalink)
References	<vu707r$ct2$1@nnrp.usenet.blueworldhosting.com> <NrCdncN7kaWojJX1nZ2dnZfqn_GdnZ2d@supernews.com> <3j-dnXJunf4_hJX1nZ2dnZfqnPWdnZ2d@supernews.com> <vub4lk$3e2ab$1@dont-email.me> <ec6cnYjmXqtbupT1nZ2dnZfqnPGdnZ2d@supernews.com> <vuba2g$3kpek$1@dont-email.me>
Mime-Version	1.0
Content-Type	text/plain; charset=utf-8
Content-Transfer-Encoding	8bit
X-Trace	individual.net PQYUI8+ERaiFlLxoOoafiQhZkbK9JAZLBIdw5l1Mjzyl/pxac1
Cancel-Lock	sha1:lO8PKmIls4PMFKzgwFzxhQhVklw= sha256:Ic/DEfgDXw3cK0u3OEcPw6XTMbXffbBuGOXHu7GVyCU=
Mail-Copies-To	nobody
X-Face	_.g>n!a$f3/H3jA]>9pN555<`}Tud57>1<n@LQ!aZ7vLO_nWbK~@T'XIS0,oAJcU.qLM dk/j8Udo?O"o9B9Jyx+ez2:B<nx(k3EdHnTvB]'eoVaR495,Rv~/vPa[e^JI+^h5Zki`Q;ezqDW< ZFs6kmAJWZjOH\8[$$7jm,Ogw3C_%QM'\|H6nygNGhhl+@}n30Nz(^vWo@h>Y%b\|b-Y~()~\t,LZ3e up1/bO{=-)
User-Agent	slrn/1.0.3 (Darwin)
Xref	csiph.com comp.mobile.android:148047 misc.phone.mobile.iphone:194731 rec.photo.digital:244467

Cross-posted to 3 groups.

Show key headers only | View raw

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

Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

csiph-web