On 26 Jul 2018 18:27:30 GMT, sms wrote:
> This is still not really the answer to the question that was asked. 
Hi sms,
You know that I'm reasonable, and I know that you're just as reasonable and 
logical as I am. So I suspect the correct answer is the one you already 
gave the OP, which is that it can't be done the way he wants to do it.
I tested it out myself, just to make sure, but I can't test what he has 
because I gave away the last iPhone I bought. 
Hence, I *believer you* that it can't be done ... where it will be 
interesting to see what fabulous concoctions both nospam and Jolly Roger 
come up with.
I was just telling the OP how my test when, which confirmed your answer, 
but I kept going until I was successful - but where I used a method that 
worked but which wasn't what the OP asked (and I agree with you on that).
> As I 
> understand the question, What the OP wants to do is to let the web site 
> choose an audio file on the phone and upload it. On a non-jail-broken 
> iPhone you can't do this.
I'm going to agree with you since Safari didn't even *show* up in my tests, 
even thoough Chrome and Firefox did, but both of those only handle "html 
links" and not files in the sharing GUI.
So I agree with you, where, as I always say, facts are funny that way.
Two logical people can always agree on facts. 
It's when Jolly Roger and nospam get involved that the OP is sent off on a 
wild goose chase. I don't know why they do that. It's almost as if they're 
both sadistic that way.
> There are various ways to get the M4A file off the phone (iTunes sync, 
> iCloud, etc.), and then upload it, but that was clearly not the 
> question. It is sometimes useful to send a voice memo directly from a 
> phone without syncing to the cloud or to a computer.
Again, I completely agree with you on your facts. 
Facts are funny that way.
For example, Savageduck mentioned the OP can use the cloud, which, of 
course, so could I when I tested it, but that wasn't the question. 
The *closest* to the question that I could come up with in my tests (which 
I only spent about 10 minutes on so there may be better ways), was to place 
the file on the network so that a PC could access it. 
> Not just on Usenet, but on other forums, there is a tendency for people 
> to not want to answer the actual question but to explain some 
> workaround, It can be helpful at times, but it is often not. In this 
> case the original poster even clearly stated "Also, no syncing onto a 
> computer."
Again, I agree (facts are funny that way) since we're both logical people.
What Jolly Roger and nopsam tend to do is make believe that some fantastic 
iOS functionality exists, even though they just make it up every time. 
In the end, when you pin them down, after a dozen or more exasperating 
retorts from those two bona fide proven idiots, you find out that they tell 
you to "use the cloud" or something stupid like that which everyone already 
knows.
It just amazes me that such sadistic childish idiots exist as both Jolly 
Roger and nospam prove themselves to be in almost every post they make.
Actually, what I *tried* (which should have worked and which would have 
been in the spirit of the OP's original question) 
> 
> I love my iPad Pro, and my wife likes her iPhone 7, but after being used 
> to Android devices, it's sometimes frustrating that something that is 
> trivial to accomplish on Android is so difficult or impossible to 
> accomplish on the iPad or iPhone. 
I'm glad you said that what is trivial to do on Android is either difficult 
or impossible on iOS, where I certainly know that but where I think the iOS 
gullibles don't know that. They're so used to "just giving up" that they 
don't realize how many things every single day they can't do on iOS, that 
on Android, you wouldn't even think twice about it (like saving the APKs as 
we discussed prior, or viewing wifi signal strength graphically over time 
for all access points, or just organizing the homescreen the way you like 
or just accessing a freaking file for heaven's sake - which is what the OP 
is trying to do).
> It's a difference in philosophy, and 
> there's often a downside to the Android device's capability, in terms of 
> security.
Here is the only place I think we differ, and it's not in fact, but in 
philosophy where you weigh what I consider a supremely overconfident false 
sense of security as being far more valuable than I think it is.
If you actually think that your iPhone is "secure", then, of course, 
Android is far less secure. But the fact is, IMHO, that the number of holes 
in your iPhone security is only, oh, I don't know, say, half of the number 
of holes in Android. 
But security is a funny thing. It's the weakest links that are the ones 
that get you, and, guess what? In all consumer mobile devices, the weakest 
links are essentially the same. 
So you traded, IMHO, a false sense of security, for a vastly overpriced 
phone (hardware comparison wise) that still has plenty of security holes, 
where I trade a vastly more powerful and five times cheaper than an iPhone 
device for, in the end, an insecure device that, I think, has the same 
security holes that you have, and then some more on top of that! :)
Anyway, it's nice to know that there are logical people on this newsgroup 
who actually comprehend adult logic - since the likes of Lewis, BK@OnRamp, 
nospam, Jolly Roger and sometimes that idiot Savageduck, just send the OP 
on sadistic wild goose chases.
BTW, I did test something briefly that *should* have worked for the OP, but 
it didn't, but it would have worked if it were Android I would think, or 
Windows, but let me run it by you since you're the only one here so far 
that has any adult comprehensive skills.
Would this work?
1. The OP "Shares" (saves" the file to something that has an HTTP server 
inside of it so that the OP gets a URL to that file of the format:
 
http://192.168.1.2:8080/file.mp4
2. Then, from Safari on the *same device*, the OP accesses that URL and 
hence the OP can then save the file to the iOS "Downloads" directory that 
Safari uses.
3. From there, the OP can *upload* that file using Safari onto the web site 
of his choosing.
Does that sound like it would work to solve the OP's problem?
If not, why not?
HINT: It's here that an expert like David Empson could be helpful.