Groups > misc.phone.mobile.iphone > #194682 > unrolled thread

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

Started by	Marion <marion@facts.com>
First post	2025-04-22 03:05 +0000
Last post	2025-04-22 15:40 -0700
Articles	20 on this page of 37 — 8 participants

Back to article view | Back to misc.phone.mobile.iphone

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Page 1 of 2 [1] 2 Next page →

#194682 — Does anyone here have experience with "photofs" fixing photo naming?

From	Marion <marion@facts.com>
Date	2025-04-22 03:05 +0000
Subject	Does anyone here have experience with "photofs" fixing photo naming?
Message-ID	<vu7127$2e1e$1@nnrp.usenet.blueworldhosting.com>

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?

[toc] | [next] | [standalone]

#194684

From	Herbert Kleebauer <klee@unibwm.de>
Date	2025-04-22 07:58 +0200
Message-ID	<vu7b6h$3u07r$1@dont-email.me>
In reply to	#194682

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".

[toc] | [prev] | [next] | [standalone]

#194691

From	Bill W <nothing@nowhere.com>
Date	2025-04-22 10:36 -0500
Message-ID	<vu8d23$s9jj$1@dont-email.me>
In reply to	#194684

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?

[toc] | [prev] | [next] | [standalone]

#194694

From	Jolly Roger <jollyroger@pobox.com>
Date	2025-04-22 15:56 +0000
Message-ID	<m6pshjFfp43U1@mid.individual.net>
In reply to	#194691

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

-- 
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]

#194701

From	Tyrone <none@none.none>
Date	2025-04-22 16:36 +0000
Message-ID	<uu2cnW2ahPTuWJr1nZ2dnZfqnPqdnZ2d@supernews.com>
In reply to	#194694

On Apr 22, 2025 at 11:56:35 AM EDT, "Jolly Roger" <jollyroger@pobox.com>
wrote:

> 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

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).

[toc] | [prev] | [next] | [standalone]

#194703

From	Marion <marion@facts.com>
Date	2025-04-22 16:50 +0000
Message-ID	<vu8hcr$2t07$1@nnrp.usenet.blueworldhosting.com>
In reply to	#194701

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.)

[toc] | [prev] | [next] | [standalone]

#194705

From	Alan <nuh-uh@nope.com>
Date	2025-04-22 10:32 -0700
Message-ID	<vu8js1$do42$2@dont-email.me>
In reply to	#194703

On 2025-04-22 09:50, Marion wrote:
> 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.

Actually, you REPEATEDLY claimed it COULD NOT POSSIBLY work.

Because you KNEW how iOS had to behave.

> 
> 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.)

You are SUCH an idiot:

I just turned on "LAN drive" again, and then did the command:

"C:\Users\Alan>net use e: \\iPhone16\DCIM"

<https://drive.google.com/file/d/1Vz7mhzAz7pNhlLKvVeSVKXW2Otv7U_pW/view?usp=share_link>

And lo and behold what do I find in File Explorer's sidebar?

<https://drive.google.com/file/d/100oVcBhbj_0QHFd4-pyAUeAPeczzWiFX/view?usp=share_link>

[toc] | [prev] | [next] | [standalone]

#194713

From	Jolly Roger <jollyroger@pobox.com>
Date	2025-04-22 21:24 +0000
Message-ID	<m6qfogFiiqbU1@mid.individual.net>
In reply to	#194703

On 2025-04-22, Marion <marion@facts.com> wrote:
> 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

LOL... Little Arlen has been claiming iOS can't do what we all know it
can do since at least *2018*. He really does think we don't remember! Here
are his own words (under another nym of course, because: troll):

On 2018-03-15, Ragnusen Ultred <ragnusen@ultred.com> wrote:
> 
> 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?

... and here he is, SEVEN FUCKING YEARS LATER *still* going on about it. 

Fucking clown.

-- 
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]

#194700

From	Marion <marion@facts.com>
Date	2025-04-22 16:29 +0000
Message-ID	<vu8g51$24lt$1@nnrp.usenet.blueworldhosting.com>
In reply to	#194684

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".

Hi Herbert,

I know you're a smart guy so I'm going to give you the correct response
but realize that my response below requires you to understand Linux a bit.

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.

The attitude that you can't fix something just because it's designed poorly
is, in my humble opinion, the wrong attitude - and - I'm pretty sure you
don't normally hold that attitude.

All we need to do with photofs is work around Apple's dumb-terminal
restrictions, much as we did by hooking up iOS to a Linux USB port.
 <https://i.postimg.cc/s2x0f9Js/files14.jpg> Linux, win10 & iOS together
 <https://i.postimg.cc/g269S8rT/files13.jpg> How does macOS work with iOS?
 <https://i.postimg.cc/pVJf72fN/files12.jpg> iOS hacks very often will fail
 <https://i.postimg.cc/cChf8mx1/files11.jpg> iOS requires hacks to copy
 <https://i.postimg.cc/9MGdc2s7/files10.jpg> Android is 2-way fast over USB
 <https://i.postimg.cc/mDx3xkp4/files09.jpg> iOS is only DCIM & only 1-way 
 <https://i.postimg.cc/3xcCBngd/files08.jpg> iOS is a dumb brick on Windows
 <https://i.postimg.cc/KjK4nHwf/files07.jpg> Ubuntu is two-way, everything
 <https://i.postimg.cc/Jhmy9KH7/files06.jpg> Ubuntu iFuse is just magical
 <https://i.postimg.cc/qqg61Rh8/files05.jpg> Ubuntu, movies _to_ iOS on USB
 <https://i.postimg.cc/QMk7tvZW/files04.jpg> Ubuntu is two way, everything
 <https://i.postimg.cc/d3SGkdgr/files03.jpg> Android is two way, everything
 <https://i.postimg.cc/L8b18Zmx/files02.jpg> iOS "Files" is nothing useful
 <https://i.postimg.cc/NFkXsJ0X/files01.jpg> iOS/Win is 1-way & DCIM only

Note that this afc command (which one in five million people know about), 
instantly turns the iOS dumb terminal into a usable read/write USB drive.
 /run/user/1000/gvfs/afc:hose=<40char>,port=3/org.videolan.vlc-ios
 <http://img4.imagetitan.com/img.php?image=18_ios170.jpg>

So instead of "just giving up", we can be intelligent and learn how to 
convert the iOS dumb-terminal device into something more useful to us.
 <http://img4.imagetitan.com/img.php?image=18_ios180.jpg> Read & write all!
 <http://img4.imagetitan.com/img.php?image=18_ios170.jpg> Anywhere you want
 <http://img4.imagetitan.com/img.php?image=18_ios160.jpg> Any file you want
 <http://img4.imagetitan.com/img.php?image=18_ios150.jpg> Copy Win10 to iOS
 <http://img4.imagetitan.com/img.php?image=18_ios140.jpg> read & write iOS
 <http://img4.imagetitan.com/img.php?image=18_ios130.jpg> iFuse mounts all!
 <http://img4.imagetitan.com/img.php?image=18_ios120.jpg> iFuse mounts iOS
 <http://img4.imagetitan.com/img.php?image=18_ios110.jpg> iFuse Windows mnt
 <http://img4.imagetitan.com/img.php?image=18_ios100.jpg> iFuse is native 
 <http://img4.imagetitan.com/img.php?image=18_ios090.jpg> Nobody knows this
 <http://img4.imagetitan.com/img.php?image=18_ios080.jpg> The trick!
 <http://img4.imagetitan.com/img.php?image=18_ios070.jpg> Look closely
 <http://img4.imagetitan.com/img.php?image=18_ios060.jpg> Both read & write
 <http://img4.imagetitan.com/img.php?image=18_ios050.jpg> Including DCIM
 <http://img4.imagetitan.com/img.php?image=18_ios040.jpg> View iOS filesys
 <http://img4.imagetitan.com/img.php?image=18_ios030.jpg> iOS mounts 
 <http://img4.imagetitan.com/img.php?image=18_ios020.jpg> Allow access?
 <http://img4.imagetitan.com/img.php?image=18_ios010.jpg> Trust Computer?
 <http://img4.imagetitan.com/img.php?image=18_ios000.jpg> Ubuntu before iOS

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.

The way Apple designs things is nothing actually works in iOS unless you're
logging into Apple's Cupertino servers every single second of your life.

That's because the entire iOS device is designed as a dumb terminal, where
I have two of them beside me right now testing how long it will take for
Apple to unilaterally brick them because I refuse to log into their matrix.

Note: Apple bricked the last two in two years, so I'm simply testing a
different set of conditions to see how long it takes Apple to brick the
devices simply because I refuse to log into their matrix servers every day.

Back to photofs, note that iFuse with AFC turns the iOS device into a
usable USB device, with read and write permission on the iOS filesystem.

I'm hoping photfs will work as well as iFuse/afc works with the iOS device
to break free of iOS' dumb-terminal strategy w/o logging into the matrix.

I just need to find people who know more than I do, that's all.

[toc] | [prev] | [next] | [standalone]

#194711

From	David <BoaterDave@hotmail.co.uk>
Date	2025-04-22 21:27 +0100
Message-ID	<m6qce3Fi057U5@mid.individual.net>
In reply to	#194700

On 22/04/2025 17:29, Marion wrote:
> I just need to find people who know more than I do, that's all.

Have you tried asking questions on the Apple Support Communities (ASC) 
Forums?

https://discussions.apple.com/welcome

You don't need a REAL Apple Account (Apple ID) - any concocted one will do.

See:- https://support.apple.com/en-gb/apple-account

Try it! You might like it! ;-)

-- 
David

[toc] | [prev] | [next] | [standalone]

#194712

From	Herbert Kleebauer <klee@unibwm.de>
Date	2025-04-22 22:34 +0200
Message-ID	<vu8ufr$1a587$3@dont-email.me>
In reply to	#194700

On 22.04.2025 18:29, Marion wrote:
> 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.

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.

> 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.

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.

[toc] | [prev] | [next] | [standalone]

#194745

From	Marion <marion@facts.com>
Date	2025-04-24 04:55 +0000
Message-ID	<vucg86$2tku$1@nnrp.usenet.blueworldhosting.com>
In reply to	#194712

On Tue, 22 Apr 2025 22:34:03 +0200, Herbert Kleebauer wrote :


> 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.

Hi Herbert,

I try to speak to each person at the level of that person, if possible.

I know you to be a purposefully helpful and knowledgeable individual, where 
I can easily tell you don't wish to dig into photofs, which is just fine.

However, since I respect your knowledge, I do wish to say that I was 
serious, but perhaps I chose a poorly framed example to make my point.

Bear in mind that I graduated with higher degrees and worked for decades in 
the Silicon Valley solving problems that didn't have obvious solutions.

Along that vein, note that I have multiple iOS devices right beside me 
doing nothing other than testing how long it will be before Apple 
unilaterally bricks them, simply for me not logging into Cupertino.

How many people know that Apple bricks your devices, Herbert?
I'd wager only one in a billion. Right?

Why do I know that, Herbert?
Because I have Apple devices to test. And I test them.

Why do I know the Apple trolls lied when they said iTunes backed up their 
IPAs, Herbert? Because I tested iTunes and it simply does not do that.

Why do I know Apple trolls lied when they claimed, many times, that iOS 
could do something as simple as graphically debug Wi-Fi signal strength?

Because I have iOS devices.

Why do I know that iOS can't even run something as basic to anonymity as 
the Tor browser, Herbert? Because I have iOS devices to test, that's why.

Also note that I volunteer multiple times a week at the local 
assisted-living centers, helping the residents utilize their devices.

Many of them are on iOS. 

All of that would be impossible were I to ditch iOS simply because Apple 
designed iOS to be a (very) dumb terminal in terms of image naming.
 
>> [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

Again, I understand that you are rather intelligent, and I've read almost 
all (if not all) your posts on the a.c.o.w-10 newsgroup, so I know that 
you're a very helpful guy when it comes to writing excellent batch 
solutions (particularly those which avoid leaving command windows open).

I know you care about the English language even, as you post to a.u.e and 
you wrote scripts that you posted to a.c.o.w-10 for spelling self 
improvement.

 for /f "tokens=*" %%i in (%spelltxtfile%) do call echo %%random%% %%i>>%spellerrfile%
 sort /o %spelltmpfile% %spellerrfile%
 del %spellerrfile%
 set /a ok=0
 set /a not_ok=0

 for /f "tokens=1*" %%i in (%spelltmpfile%) do call :sub %%j
 :end
 del speak.vbs
 del %spelltmpfile%
 echo.
 echo %ok% words correct,  %not_ok% words incorrect
 echo.
 pause
 exit

That's only a snippet, but I know you can solve problems when you feel 
those problems are worth solving - and so do I - so we're similar that way.

You do NOT feel solving the problem of iOS being a dumb terminal in terms 
of file-naming conventions is worth it - and I completely understand you.

Maybe it's not worth it. But maybe it is.
You know, I suspect only one in a billion people (IMHO) know how to use 
iFuse with AFC to *write* to the iOS file system from Linux, Herbert.

How did I learn?
I couldn't ever have learned how if I didn't have iOS devices, right?

Well, I think it's a similar thing here where it's obvious to everyone that 
iOS is designed as a dumb terminal with grotesque image-naming conventions.

The main question in this thread, is whether photofs can solve that 
hideously unnatural problem of iOS' being designed so poorly that it is 
incapable of outputting image files with human-readable file names.

Maybe iOS can be forced to put out non-outlandish monstrous file names. 
This ng has solved far more difficult problems than a simple file name.

> 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.

Well, I'm hoping to find someone who knows more than I do about how to get 
iOS to stop being a dumb terminal to get iOS to write normal file names.

Don't laugh. It may very well be possible. 
Take for example how we were able to write to iOS over USB years ago.

We did something like this (from memory) by way of critical example:
Install Necessary Software:
sudo apt-get install libimobiledevice-dev ifuse
sudo apt-get install usbmuxd
sudo systemctl enable --now usbmuxd
Pair Your Device: 
Connect your iOS device to your Linux computer via USB. 
You might be prompted on your iOS device to "Trust This Computer." 
Make sure to tap "Trust." 
You can try to pair your device using idevicepair:

idevicepair pair
Create a Mount Point: 
Create a directory on your Linux system where you want to mount the iOS 
device's file system:

mkdir ~/iphone_mount
Mount the Device using iFuse: 
Use the ifuse command to mount your device to the created directory:

ifuse ~/iphone_mount
If this is successful, you should now be able to see some of your device's 
files and folders within the ~/iphone_mount directory. 

By default, you'll likely have access to the media directories (DCIM, etc.) 
and potentially application-specific "Documents" folders if the apps support 
file sharing.

Writing Files: 
You can now attempt to write files to the mounted directories 
using standard Linux commands:

cp my_document.pdf ~/iphone_mount/Documents/MyAppName/ # If the app 'MyAppName' supports file sharing
or
cp my_image.jpg ~/iphone_mount/DCIM/ # Might not allow direct writing in all subdirectories

Important Considerations and Limitations:
Permissions: Due to the sandboxed nature of AFC, you cannot typically 
write to arbitrary locations on the iOS file system using standard 
iFuse and AFC on a non-jailbroken device. You are generally restricted 
to specific directories designated for media or application file sharing.

Application Support: 
Writing to an application's "Documents" folder will only work if the 
iOS application explicitly supports file sharing via iTunes File Sharing 
(which exposes these folders through AFC). You'll need to know the 
specific bundle identifier or folder name used by the app. 

The ifuse --list-apps command can sometimes help list applications
and their identifiers.
Jailbreaking (iFuse --root): If your iOS device is jailbroken 
and has the necessary AFC2 service installed, you might be able 
to mount the root file system with the --root option:

sudo ifuse --root ~/iphone_mount

gphoto2: 
For accessing photos, you might also see your iPhone mounted 
as a camera using the gphoto2:// protocol in some file managers. 
This is a separate mechanism from AFC but also allows transferring photos. 
Writing back to these locations might be limited.

Troubleshooting: If you encounter issues, make sure usbmuxd is running, 
your device is trusted, and you have the necessary libimobiledevice
and ifuse versions installed. 

Check the output of the ifuse command for any error messages.
In summary, while iFuse allows you to interact with your iOS 
device's file system over USB using the AFC protocol on Linux, 
writing is generally restricted to specific media directories 
and application file-sharing folders on non-jailbroken devices.
For broader write access, a jailbroken device with additional 
services might be required, but this comes with significant risks.
-- 
To understan an iOS device, is to understand why Apple designed 
it as a (very) dumb terminal, devoid of even basic capability.

Like choosing the name of an image file out of the camera app.

[toc] | [prev] | [next] | [standalone]

#194715

From	Tyrone <none@none.none>
Date	2025-04-22 21:59 +0000
Message-ID	<NrCdncN7kaWojJX1nZ2dnZfqn_GdnZ2d@supernews.com>
In reply to	#194700

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.

[toc] | [prev] | [next] | [standalone]

#194716

From	Jolly Roger <jollyroger@pobox.com>
Date	2025-04-22 22:05 +0000
Message-ID	<m6qi4rFitptU1@mid.individual.net>
In reply to	#194715

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.

-- 
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]

#194717

From	Tyrone <none@none.none>
Date	2025-04-22 22:14 +0000
Message-ID	<eeOcndK9oIZdiZX1nZ2dnZfqnPWdnZ2d@supernews.com>
In reply to	#194716

On Apr 22, 2025 at 6:05:15 PM EDT, "Jolly Roger" <jollyroger@pobox.com> wrote:

> 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.

That whooshing sound you hear is Arlen, once again desperately moving the goal
posts.

[toc] | [prev] | [next] | [standalone]

#194718

From	Tyrone <none@none.none>
Date	2025-04-22 22:35 +0000
Message-ID	<3j-dnXJunf4_hJX1nZ2dnZfqnPWdnZ2d@supernews.com>
In reply to	#194715

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.

[toc] | [prev] | [next] | [standalone]

#194725

From	Herbert Kleebauer <klee@unibwm.de>
Date	2025-04-23 08:32 +0200
Message-ID	<vua1hm$2bvoc$1@dont-email.me>
In reply to	#194718

On 23.04.2025 00: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.

Seems they are using "Universally Unique IDentifiers" (UUIDs) (rfc9562)
as file names:

https://datatracker.ietf.org/doc/html/rfc9562

[toc] | [prev] | [next] | [standalone]

#194744

From	Marion <marion@facts.com>
Date	2025-04-24 04:30 +0000
Message-ID	<vucep0$23sn$1@nnrp.usenet.blueworldhosting.com>
In reply to	#194725

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.
-- 
Only one out of billions understand anything about Apple's core strategy.

[toc] | [prev] | [next] | [standalone]

#194748

From	Alan <nuh-uh@nope.com>
Date	2025-04-23 22:12 -0700
Message-ID	<vuch87$s0ru$2@dont-email.me>
In reply to	#194744

On 2025-04-23 21:30, Marion wrote:
> 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.

Utterly false.

> 
> 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.

You want to use "naming conventions" as a replacement for comprehensive 
metadata.

[toc] | [prev] | [next] | [standalone]

#194752

From	Bill W <nothing@nowhere.com>
Date	2025-04-24 11:14 -0500
Message-ID	<vudo0i$1ua7a$1@dont-email.me>
In reply to	#194744

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]

Page 1 of 2 [1] 2 Next page →

csiph-web

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

Contents

#194682 — Does anyone here have experience with "photofs" fixing photo naming?

#194684

#194691

#194694

#194701

#194703

#194705

#194713

#194700

#194711

#194712

#194745

#194715

#194716

#194717

#194718

#194725

#194744

#194748

#194752