Path: csiph.com!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: candycanearter07 Newsgroups: comp.mobile.android,misc.phone.mobile.iphone,rec.photo.digital Subject: Re: Does anyone here have experience with "photofs" fixing photo naming? Date: Wed, 23 Apr 2025 21:50:03 -0000 (UTC) Organization: the-candyden-of-code Lines: 24 Message-ID: References: <3j-dnXJunf4_hJX1nZ2dnZfqnPWdnZ2d@supernews.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Wed, 23 Apr 2025 23:50:03 +0200 (CEST) Injection-Info: dont-email.me; posting-host="eecd9d74832e78987a2248a608480466"; logging-data="57332"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/psnTAaybopl6V4OjDxnF0J/8viBiF/WizEtVD3IFpzw==" User-Agent: slrn/1.0.3 (Linux) Cancel-Lock: sha1:Q4iewEO92s4w/nC2wkJ5Fl7AHy8= X-Face: b{dPmN&%4|lEo,wUO\"KLEOu5N_br(N2Yuc5/qcR5i>9-!^e\.Tw9?/m0}/~:UOM:Zf]% b+ V4R8q|QiU/R8\|G\WpC`-s?=)\fbtNc&=/a3a)r7xbRI]Vl)r<%PTriJ3pGpl_/B6!8pe\btzx `~R! r3.0#lHRE+^Gro0[cjsban'vZ#j7,?I/tHk{s=TFJ:H?~=]`O*~3ZX`qik`b:.gVIc-[$t/e ZrQsWJ >|l^I_[pbsIqwoz.WGA] wrote at 22:35 this Tuesday (GMT): > On Apr 22, 2025 at 5:59:17 PM EDT, "Tyrone" 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 is generated from /dev/urandom