On Tue, 6 Nov 2018 15:33:23 -0000 (UTC), Diesel wrote:

I couldn't help but notice you now specifically use the words,
'visible' file system; instead of full access as you previously (yet
incorrectly) assumed that 3rd party driver you thought only you knew
about (hahaha) gave you.

Hi Diesel,
I think I may have not been clear, so I apologize that you seem to have
misunderstood what "visible" means, where I've used the term
umpteen times on Windows, Linux, Android, and iOS contexts, so I simply
assumed you understood what it means in the context of the typical user.

It's all about read/write permission.

What visible indicates is what a typical "user" can read/write to.
o On Linux home desktops, that's typically everything
o On Windows home desktops, it's typically everything

However, if you're at the local public library, then the "visible" file
system (aka, the area the user can read and write to), may be vastly
limited.

Given the context of a desktop writing to a mobile device, I don't expect
the desktop to write to the "non visible" portion of the mobile device
(without rooting/jailbreaking).

Does that clarification make sense to you yet?

It's my fault that you seemed to miscomprehend what "visible file system"
means, where you seem to have attributed, seemingly, some sort of sinister
intent, but it just means what the user can read and write to.
o On Android, it's typically _not_ the entire file system
o On iOS, it's even far less of the file system

To the point of the "visible" file system on Android, there's no problem
for a typical user to read _and write_ to that _entire_ visible file system
from the desktop (e.g., from Windows).

But the trick, always, in cross platform read/write compatibility, is not
Android and Windows, but iOS and Windows (or iOS and Linux).

Put another way, it's easy to claim cross platform compatibility if you
ignore either iOS, or if you ignore the entire visible file system on iOS.

A simple test of the ability to _write_ to the entire visible file system
of iOS is to simply write to the DCIM directy from the desktop over USB.
o I can easily do that
o But almost nobody else can

Why not?
They don't know what I know about writing to the iOS visible file system.

To wit:
o I can read _and write_ to the entire visible iOS file system
o But most people can't do that.

How can I prove that most people can't do that?
o Just slide a file from their desktop onto the iOS DCIM directory.

IMHO, 999 out of 1,000 people will fail at that simple task.
And yet, DCIM is clearly a component of the iOS visible file system.

I hear a _lot_ of people _claim_ they can do it, but if they can't tell me
how they did it, then I _know_ they're just making up those claims (hoping
that nobody realizes that they don't actually know how to do it).

You're not one of those people Diesel, who would make a claim without being
able to actually do it - but a lot of people _think_ they're far smarter
than they really are ...

And the proof (in this case) is simple:
o If they can write from the desktop to the DCIM directory
Then what they claim is true
o If they can _not_ write from the desktop to the DCIM directory
Then what they claim is false.

As I said, it's binary (where the DCIM directory is just _one_ of the many
directories in the typical iOS visible file system).