joe <no...@domain.invalid> wrote:
>> Is it?
>>
>
>
> The short answer: NO
Wow. Just wow.
A poster on this newsgroup who doesn't answer inconvenient facts about
F-U-N-C-T-I-O-N-A-L-I-T-Y with the typical Apple Apologist drivel of:
a. child-like potty-mouthed instant insults (e.g., Tim Streater)
b. incessant fabrication of non-existent imaginary functionality (e.g., JR)
c. silly semantic games (e.g., nospam)
d. child-like inability to comprehend detail (e.g., Lloyd Parsons)
etc.
Of course the correct answer is no.
I sincerely thank you for acting like an adult should on this Mac-related
newsgroup.
> The reasons:
>
> iTunes is bundled with the Mac OS. Therefore, there may be very few Macs
> in the world without iTunes.
Understood. Still, even with the iTunes abomination, the Mac is unable to
do the /simplest/ of things that the other platforms functionally do with
aplomb.
It's all about F-U-N-C-T-I-O-N-A-L-I-T-Y.
That's just an inconvenient fact that the Mac is less functional.
> One could remove iTunes, but you'd argue some components may still be
> installed and in use. Anyway someone using iTunes wouldn't want to
> delete it just to prove your silly game.
My questions are relevant and valid to the newsgroup.
That you consider the question silly is fine, but the
F-U-N-C-T-I-O-N-A-L-I-T-Y of being able to slide desired file back and
forth and to edit desired files from one platform to the other, is still
F-U-N-C-T-I-O-N-A-L-I-T-Y.
That you feel F-U-N-C-T-I-O-N-A-L-I-T-Y is "silly" need not be stated since
you already opined yourself that facts were "clutter" in your brain.
Did you not?
> On the other hand, your question involves accessing files via smb.
I complement you for being able to comprehend factual detail in that
statement.
I do agree with you that smb accords in some ways more functionality, and
in other ways, less functionality than does native USB connections,
particularly with respect to how the other common consumer platforms
natively handle iOS connections sans the iTunes abomination.
> iTunes functionality is not needed anyway unless that happens to be the
> application associated with the type of file you are trying to access.
Since you made that statement in seemingly good faith, I will concur with
you that the iTunes abomination is not normally removed by the Apple Mac
user - where they often reside completely ensconced within the walled
garden.
However, outside the narrow confines of the walled garden, in the real
world, the F-U-N-C-T-I-O-N-A-L-I-T-Y of being able to connect seamlessly to
the iOS file system from a desktop is required, especially as you must be
aware that the iTunes abomination does not actually work in the real world.
> In other words, the iTunes part of the question is rather pointless.
> iTunes has nothing to do with accessing an smb server.
The issue about removing the iTunes abomination is only that it needs to be
removed from the equation since it is proven to be restrictive in
functionality, and it is proven not to work in the real world.
There are other salient facts about the iTunes abomination which are just
as provable (e.g., it's the canonical example of bloatware), but the most
relevant reason for removing the iTunes abomination from the equation is
that it blocks F-U-N-C-T-I-O-N-A-L-I-T-Y.
> The question is about editing an arbitrary file. If the smb server
> doesn't export the entire file system, the selection of a file to edit
> isn't truly arbitrary.
It's not clear yet that there is an "smb server" (or client) for the Mac,
but I'll skip that question for later (see below).
As I stated prior, on Usenet, we don't have editors looking over our
shoulders watching over every single word used so that a kindergarten child
would comprehend.
As I repeatedly explained to you, I can create files of the name
"joe_is_foo" with arbitrary text of "this is joe is foo", in locations that
I don't even know what they do.
In fact, these locations are so arbitrary that, for whatever reason, their
mere existence (and or content) seems to have potentially revealed a
nascent bug in the Apple iOS software such as shown in this screenshot from
earlier today on my iPad:
http://i.cubeupload.com/x7WV2L.jpg
Finding platform-to-platform bugs seems to be my gift, since I found an
interesting one between Windows & Linux just this morning also:
Have you ever seen "unsupported reparse point" warnings in ls output?
<
https://groups.google.com/d/msg/alt.os.linux/3XyLpV-Za9o/mHiUyE3EAwAJ>
http://i.cubeupload.com/1ji0MX.jpg
If all the Mac users do is stay completely ensconced inside the walled
garden, and especially if they use the iTunes abomination to do so, they'll
never see what I see in the real world.
> All you were able to show was your smb server,
> "WiFi HD", only exposed the part of the file system in its sandbox.
Wow. Just wow again. Thank you for being an adult in answering a basic
question of what file system was exposed in that smb server output!
I wasn't sure, since I know almost nothing about iOS, whether that exposed
file system was the root level of the iOS device, or just the root level of
the application stored inside the iOS device.
Thank you for being the /first/ person on this thread, after, oh, I don't
know how many, scores of posts, who answered a simple question.
Thank you for acting like an adult on this Mac-related newsgroup.
> That
> means the choice of file to edit is far from arbitrary. You may call
> this a semantic argument, but you asked about arbitrary files, not those
> limited to a single application.
Again, we can quibble about a term that we both have extensively discussed
elsewhere in this thread.
We could have gotten to this point much quicker, just as the adults do on
the Linux, Windows, and Android newsgroups, if we simply clarified the
terms as one adult to another.
I agree with you, sticking only with SMB, that if that exposed file system
is only that which is essentially inside an app, then we don't have "much"
exposure to the root file system.
NOTE: We do have what seems like complete ad-hoc access to the syslog of
the iOS device - but - if we stick to only the more limited SMB access - we
don't have that syslog access, I agree.
> When asking for clarification, you
> responded by showing the server only accessed its own file and then with
> usb connection related details, and also included your usual slurry of
> insults. All your whining about the responses you get should be directed
> at you.
Here's where you are wrong.
In tens of thousands of posts over the years, I respond to what the posters
write, in terms of facts stated.
Do you think, for example, anyone but you (in this post I'm responding to)
has presented a /single/ fact?
The /only/ facts that were presented were by me.
Bear in mind that I have an extensive record on all the platform-related
newsgroup of only speaking facts. It's only on these Apple-related
newsgroups that facts are treated as threats to the posters' belief system.
For example, I posted an inconvenient fact this week to the Windows
newsgroup:
And, just today, I posted an inconvenient fact to the Linux newsgroup:
Do you instantly see how adults act on those newsgroups when confronted
with the reality of an inconvenient fact?
Can you instantly see the stark contrast with how Apple posters act when
confronted with inconvenient fact?
Elsewhere in this thread, dorayme posits that some of the more child-like
posters to this thread act as if they were "counterfactuals", which is a
tendency to manufacture their own internal belief systems, of sorts.
In concurrence, I clarified that assertion by stating that they're
overwhelmingly "positive counterfactuals", which, as I understand it, is
the tendency for them to manufacture completely illusory belief systems
where the facts come out differently and in a positive direction in terms
of actual Mac-to-iOS F-U-N-C-T-I-O-N-A-L-I-T-Y.
> About editing an arbitrary file, if you could access any file there is
> no guarantee that a Mac will have an editor that supports any arbitrary
> file format. (Unless you want to talk about hex editors.)
Hex editors are fine, by the way, but the point is more that the goal is to
be able to copy any desired file back and forth between the iOS and desktop
system, without restriction, to locations that matter to the user.
For example, I have perhaps 100GB of videos that I wish to transfer from
the Windows/Linux desktop (it's the same desktop in dual-boot
configuration), to the new iOS device, and I have plenty of screenshots and
video on the iOS device that I wish to edit, directly on the iOS device,
using powerful desktop editors.
With the help of the adults on both the Windows and Linux newsgroup, I have
been able to obtain that simple powerful F-U-N-C-T-I-O-N-A-L-I-T-Y.
I was just asking here if the Mac users had that same simple powerful
F-U-N-C-T-I-O-N-A-L-I-T-Y of editing files that reside on the iOS device
from the Mac, and of wholly unrestricted copying hundreds upon hundreds of
megabytes of video and audio between the iOS device and the desktop, at
about the rate of a GB per minute (roughly).
I have that functionality.
That's a fact.
I only ask if the Mac users have the same functionality.
It's a relevant question that simply deserves a factual answer.
> Basically, it
> is unlikely to be able to edit an "arbitrary file" in a general sense.
> If you are to choose the file based on the available editors, it is no
> longer an arbitrary file.
To expound upon what I already explained, mostly I want to edit any file on
the iOS device that I care to use a more powerful editor to edit it with.
For example, on iOS I might snap a movie using the default iOS app which st
stores the movie in a certain location. On Windows, I might wish to edit
that movie using, say, Shotcut freeware, which is easily enough done, all
the while the file resides only in the iOS device (and presumably in
Windows' RAM while it's being loaded and edited).
Notice that the file does not have to be /copied/ from the iOS device to
the desktop file system in order to edit that file /directly/ on the iOS
device.
That's F-U-N-C-T-I-O-N-A-L-I-T-Y.
I was asking if you Mac users have the same F-U-N-C-T-I-O-N-A-L-I-T-Y.
The answers to a simple functionality question shouldn't be to call the
person who asks, a "twit" as is the habit of some of the child-like Apple
posters here.
Nor should the response be to fabricate completely fictional functionality,
as is the incessant tendency of most of the Apple Apologists whom, with
dorayme's suggestion in mind, might better be described as "positive
counterfactuals".
The response in the Apple newsgroups should be similar to that of an adult,
just as it is in the Windows newsagroup when confronted with perhaps
inconvenient facts such as this screenshot today exemplifies:
https://u.cubeupload.com/3xLbd5.jpg
Notice a crucial difference between the adult discussion on the other
platform newsgroups, and the child-like responses in the Apple-related
newsgroups, even though, in both cases, inconvenient facts are presented
such as these:
https://u.cubeupload.com/CR5puo.jpg
Likewise, the posters on the Apple-related newsgroups should be adult
enough to comprehend the details of the facts, such as these which were
posted today in this screenshot to the Linux newsgroup.
https://u.cubeupload.com/1ji0MX.jpg
It's always a source of wonderment that I can reliably prove that, only on
the Apple-related newsgroups, is the fact-to-drivel level about 1 to 100,
whereas on the adult platform-related newsgroups, it's far more a ratio of
100 to 1.
Why?
I don't know why.
The Apple poster is not a normal adult is the /simplest/ way to describe
that obvious and well-proven fact.
This is an example of what an adult Windows poster posted, to respond to
inconvenient fact:
https://micklord.com/testpage/
Notice how different that is to the typical response of the Apple poster,
who simply says facts clutter their minds.
> The interesting point is that this is basically the same as you would
> find for a Windows or Linux system. All have the ability to access a
> file using smb protocols. You should have been able to learn that detail
> on your own.
Being an adult with adult comprehensive skills, I agree with you that smb
is quite limited in what it can do, so that's why you concentrate on the
SMB aspect of the question, which is fair enough since I learned that smb
was extremely limited during the process of evaluating SMB versus USB.
In short, as I already summarized on the adult platform newsgroups, smb is
less powerful (by far) than is USB, where USB gives almost perfect fast
access to portions of the iOS file system that I care about.
Even so, there are always inconvenient facts, which the adults on the other
platform newsgroups always seem to handle better than do the child-like
respondents on the mac related newsgroups.
For example, it's clear that SMB works far better by default on Windows
than it does on Linux, even with Samba and smbclient installed.
Similarly, USB works far better, by default, on Linux, once I updated the
drivers since Apple iOS changes keep breaking them in the real world, than
USB does, by default, on Windows.
Those are inconvenient facts to be sure; but what's starkly different is
that the adults on the other platform groups handle those inconvenient
facts as adults should - while the child-like posters on the Mac newsgroup
handles those facts like children would.
One question for you, by the way, Joe, is whether you also need to add a
Samba server and smbclient on the Mac in order to perform such smb
connections?
Q: Does the Mac need to add Samba/smbclient to add SMB server/client
functionality?
If so,
Q: Which smb client/server is the canonical smb client/server for the mac?
> The smb protocol does not change with the server's underlying OS. Nor
> should it matter that the server is a portable device or a PC or a big
> box server.
Actually, in my humble experience, SMB works quite differently on Windows
versus Linux with respect to connections with the WiFi HD app's smb server
and smbclients on iOS.
Likewise, you wouldn't think USB would work quite differently, but it does,
where on Linux, USB connections to iOS (once the iOS mobile device drivers
are updated to fix what Apple breaks in various iOS releases) work superbly
well, compared to the lackluster performance of USB connection between
Windows and iOS by default.
Notice that these inconvenient facts were handled with aplomb on the adult
platform newsgroups, but when I bring up similar inconvenient facts on the
Apple-related newsgroups, all but this one post of yours, Joe, is filled to
the brim with Apple Apologist (counterfactual) drivel.
Given those facts above, I respectfully disagree with you that, at least by
default, SMB works similarly on the various platforms.
My well-proven experience is that it does not, but I do at the same time
agree that I know next to nothing about SMB syntax, having learned what
little I do know during the time period of this thread.
> As far as not getting an answer, the first reply in this thread was an
> answer in that people have been editing files over an smb connection for
> years.
Except that it was a lie, which, by the way, is expected of the Apple
posters, since I've been on Usenet for decades, so, while I'll never
understand why Apple Apologists incessantly fabricate fictional
functionality, I certainly have proven time and again that they do.
Fact is, Apple posters can almost never prove their own statements, which
you have to admit, happened time and again in this very thread.
Meanwhile, the adults on the other platform newsgroups not only prove their
statements, but they supply videos such as this one, to be purposefully
helpful, even when confronted with inconvenient fact.
https://micklord.com/testpage/
> While my answer is 'no', that is mainly due to the way you worded the
> question. Yes, Macs can edit files on a smb server. But your "without
> iTunes" and "arbitrary iOS file" aspects to the question drive my answer
> to "no".
Let's just move forward, Joe.
You're the only person here yet, who owns a Mac, who has acted like an
adult would.
My main question for smb, at the moment, is simply whether you too have to
add a third-party SMB server & client, like I had to do on Linux (but not
on Windows).
Q: Does the Mac require installation of an smbclient/server for smb?
Q: If so, do you know which one is canonical smbclient/server for the mac?
As for SMB, given that the USB connectivity seems far more powerful,
another relevant previously asked question is whether you have the same,
more, or less read/write access to the iOS device as we do on Linux?
I won't repost the screenshot because I already proved that we easily get
three iOS file systems mounted on Linux, so I'm just curious if you get the
same three iOS file systems mounted when you connect an iOS device by USB
to your Macs.
Q: What read/write mount points occur when connecting iOS to a Mac?
> Given that you don't have a Mac, why even bother asking the question?
> Either way, the answer has no impact on what you do.
While I understand your point of view that it is bliss to remain ignorant,
I don't have the same conception that ignorance is bliss that you seem to
espouse.
I don't have an iPhone, and yet I work with iPhones all the time, and I've
jailbroken them, and I've bought a handful, just as I've bought a handful
of iPads but I don't happen to own every one, and just as I've bought a
handful of iPods but I don't happen to own every model.
Being ignorant is not bliss.
Hence, following your suggestion of being ignorant of the iPhone, simply
because I don't use an iPhone as my phone, wouldn't be blissful for me.
In fact, I just asked an iPhone-related question of the iOS newsgroup,
where the question is so simple that I won't be shocked to find out that
only child-like responses result.
Does Apple reset the iPhone to factory defaults when they replace the battery?
<
https://groups.google.com/forum/#!topic/misc.phone.mobile.iphone/n2vBUQgo_LU>
With respect to the Mac, I often work in the local school dictrict as a
volunteer, and I run into the Mac constantly. What never ceases to amaze
me, in fact, in the school system, is that supposedly intelligent adults
are so clueless aboutg what a Linux-based desktop can accomplish with
respect to connectivity outside the crippling effect of the iTunes
abomination.
In fact, I'm so often frustrated by the sheer fact that Macs never seem to
have the functionality that I just expect out of a linux-based desktop,
that it behooves me to ask questions about the Mac with respect to
connectivity.
In short, I disagree with your suggestion, but I understand it, that being
ignorant of Mac functionality with respect to interoperabily in the real
world is a desireable thing.
> You can cry semantics, but your were the one who posed the question. You
> chose the words, not anyone else. You failed to respond to the
> clarification about the server exposing all files with a clear answer.
C'mon Joe, Now you're acting very Snit like. Up until you said I failed to
respond to all accusations, you were doing well with respect to being an
adult with facts.
I responded to /every/ request for clarification.
You were the one, in fact, who refused to prove your statements.
Many of the others also refused to prove their statements.
It's actually so common on the Apple-related newsgroups for people to never
be able to prove their statements that it's sort of expected that the Mac
and iOS users simply lie.
Why do the Apple users incessantly lie?
I don't know why.
But the fact is that they do. Constantly.
So I expect 9 out of 10 responses on this newsgroup to be lies or silly
semantic games, or just useless drivel.
And yet, I prove /all/ my assertions.
Every single one.
I only speak fact.
You Apple users aren't used to facts.
But the adult platform newsgroups handle facts quite well.
I've provided many examples, where I've asked the /same/ question of the
relevant newsgroups, and almost every time, only on the Apple-related
newsgroups the posters are invariably child like.
Why are Apple posters almost, to a person, acting like children?
I don't know why.
I suspect they can't handle inconvenient facts, and they can't do anything
outside the neat little false world that Apple provides them for safety and
functionality that only works inside the walled garden.
But I don't ever claim to understand why Apple posters are different from
normal adults.
All I can reliably prove is that they are.
> Instead you chose insults.
You're wrong here, Joe.
Look at your own responses to mine.
I resort to telling you the truth.
When you act like a child - I tell you you're acting like a child.
When you act like an adult - I tell you you're acting like an adult.
Don't be like that Lloyd Parson's guy, who thinks that if he acts like an
adult once out of ten posts, that I should consider him an adult for all
ten posts.
If you act like an adult, I'll commend you for acting like an adult.
If you act like a child, I'll point out that you're acting like a child.
I only speak fact.
> Your lack of respect for the posters here and
> Apple users and products in general is blatantly obvious. If you
> continually sling insults what do you expect in return?
Do you realize what you just said?
Do you?
I can't imagine that you do, but, you must understand, that the way you
Apple Apologists handle inconvenient fact is what sets you off as
completely different than normal adults.
You don't see this, I'm sure, but I'm trying to tell you something which
I've proven more than a few times in this thread alone, which is that in
the adult platform newsgroups, people handle inconvenient facts with
aplomb.
On the adult platform newsgroups, when I bring up, say, a dislike of the
way Windows handles updates, they agree, or they disagree, but they don't
consider the inconvenient fact of how Windows handles updates to be an
attack on them personally.
Only in the Apple-related newsgroups do the posters incessantly handle
inconvenient facts as an attack upon the very foundation of their core
belief system.
Fact it.
An inconvenient fact is merely a fact.
That you may consider an inconvenient fact as an attack on the core of your
entire belief system, only makes it so in your child-like mind.
In an adult mind, such as that which you see in spades on the Linux and
Windows and Android newsgroups, an inconvenient fact is merely that.
> If you had spent time with web browser, you could have answered this
> yourself.
I don't think you realize at all that this question has /never/ been asked
before.
Show me proof, for example, that a browser search will show me the mount
points that will show up when I attach an iOS device to a Mac.
Can you prove a single one of your statements Joe?
Can you?
I prove all of mine.
> Also, I am not Snit.
That's good because, in decades of being on Usenet, Snit is the only person
I have ever had to killfile, not because Snit is, much like Jolly Roger,
completely immune to adult reason, but because Snit never gives up (he
posted an Android fallacy 400 times also that Android can't record the
screen and audio when it went native /years/ ago and only showed up in iOS
last September).
For example, you should see this hilarious thread where Snit composed a
video directly attacking me, which he posted over 400 times alone, over the
period of three months, where not a single statement he makes is actual
fact.
It's a fact iOS devices can't even graph Wi-Fi signal strength over time
https://groups.google.com/forum/#!topic/comp.mobile.ipad/-T7FEXIdU9Q[1-25]
What's funnier, is that both nospam and Jolly Roger high-fived him for
supposedly proving my facts wrong (which would have been a notable
accomplishment indeed)... which you have to admit is hilarious because my
facts are almost never wrong ... simply because I don't make things up.
Making things up comes so natually to the Apple posters on the associated
platform newgroups that one has to wonder about why the Apple poster feels
the /need/ to make things up when confronted with inconvenient facts.
Certainly they did so, in spades, in this thread.
Why do Apple users feel the incessant need to claim functionality which
simply does not exist?