• If you're used to the Windows WhatsApp SAVE PDF to device...

    From Maria Sophia@mariasophia@comprehension.com to comp.sys.mac.system,alt.comp.os.windows-10,misc.phone.mobile.iphone on Wed Oct 28 23:26:22 2026
    From Newsgroup: alt.comp.os.windows-10

    Woo hoo!

    Frank recently astutely noted on the Android newsgroup there is a save to device on the desktop WhatsApp but not a similar option in the Android WA.
    I agree, saving *should* be a feature of WhatsApp, but - contrary
    to the Windows version - the Android version of WhatsApp does not
    have a save (file) feature, only Share. And by default - at least
    my Samsung phone - Share does not have a a save choice either.
    So... you'll need a extra file manager to get that.

    Moments ago, I found a solution to that problem, which *adds* the Save on Device option to WhatsApp on Android so that they both work the same way.
    <https://i.postimg.cc/B6ryMZpn/saveasfile.jpg>

    The solution is below, but it's as simple as installing this one FOSS app.
    <https://f-droid.org/packages/name.lmj001.savetodevice>

    Now the desktop and the Android device WhatsApp will save PDF files easily.

    I don't use WhatsApp on my iPads so I ask the iPhone users if the WhatsApp
    on iOS can save directly to the device outside of WhatsApp storage?

    Probably not...

    ==== < cut here for the original thread on this topic > ====
    Richmond wrote:
    What's odd is some payware actually works, but it complains that it has no >> way of charging me, which I never did understand but which is not frequent.

    You did all that and then installed Whatsapp??

    This thread asks two generic questions for the benefit of the team:
    a. What app to use to view PDFs from WhatsApp, and,
    b. How to save that PDF outside of the WhatsApp file system storage.

    Woo hoo! We solved the second half of the age-old issue of SAVING a file!
    <https://i.postimg.cc/B6ryMZpn/saveasfile.jpg>

    Again, you're new here so you may have no idea what WhatsApp does when
    dealing with people from Europe (in my case, German relatives) via phones.

    I started using WhatsApp for that reason, but well before RCS became all
    the rage, my own children (who are still on my long-grandfathered family
    plan) are on both platforms. The girls are in iPhones. Pink iPhones.

    That's how I got introduced to jailbreaking, actually, since my first
    iPhone was, oh, it must have been the iPhone 4 I think, where I was on
    T-Mobile and Apple had made some kind of deal to only be on AT&T.

    So I had to jailbreak the damn thing, and add Cydia, and put Limewire songs such as "I'm a barbie girl" as the ringtone, which is what you do for kids.

    Now those kids have kids, and every day I enjoy a plethora of images and videos, where if you look closely at the whatsapp avatar, that's a baby.
    <https://i.postimg.cc/tRmWnpFP/whatsappshare.jpg>

    And, in fact, the entire conversation about the plumber fixing the toilets
    was for their house, not for mine, which is why they sent me that quote.
    <https://i.postimg.cc/g2kQdrwY/toilet.jpg>

    In the end, I bought the parts and my son in law did the repair, where the reason for WhatsApp is that it makes communication with images much better.
    <https://i.postimg.cc/nLX4d4Cz/nowhatsappsave.jpg>

    Back to the topic at hand, the good news is we learned WhatsApp doesn't
    have a SAVE button, but as Frank said, there are "Open with" options
    galore, but that doesn't change the question as to the best PDF reader.

    Also, when Frank said this (verbatim), it made me think of a workaround:

    Since we're all about clever solutions to every problem set, that anyone
    can use, so that the team benefits as a whole from every suggestion, I
    might be able to test this program which I previously used for Aurora.
    <https://f-droid.org/packages/name.lmj001.savetodevice>
    "Save on Device adds an option to the Android Sharesheet
    that allows you to save files to your device."

    But at that point, the Share button is hidden, just two levels deeper.

    When I longpress on the PDF I get on top these icons inside WhatsApp
    Left arrow, 1, bent left arrow, trash, bent doubleright arrow, 3dots

    Looking up what they mean, apparently they mean
    a. Left arrow: Go back / unselect
    b. 1: Indicates 1 item selected
    c. Bent left arrow (Reply): Reply to the message
    d. Trash: Delete message
    e. Bent double-right arrow (Forward): Forward the message to another chat
    f. 3 dots (More): Additional option s

    There's no share icon. :(

    But inside of the 3 dots is
    A. Verify security code
    B. Star
    C. Share
    D. Reply privately
    E. Pin
    F. Ask Meta AI
    G. Report (phone number)

    When I tap "Share", I get a billion options (way more than before with the
    Open With dialog, and one of those is "Save on device" from F-Droid.
    <https://i.postimg.cc/B6ryMZpn/saveasfile.jpg>

    Note that I happen to have tested all the free ad-free file managers for Android so I do realize many of those also have the same SAVE AS option.

    However, the F-Droid "Save on Device" tool should work for everyone.
    No matter what file managers they happen to have installed on Android.

    Voila! This solution will work for everyone, probably in every app too!
    I love solutions that are free and ad free and which EVERYONE can use!

    That's the entire point of Usenet, after all, to add to the knowledge base.
    --
    Only the best of the Usenet posters can add value in every single article.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Herbert Kleebauer@klee@unibwm.de to comp.sys.mac.system,alt.comp.os.windows-10,misc.phone.mobile.iphone on Thu Oct 29 09:01:16 2026
    From Newsgroup: alt.comp.os.windows-10

    On 10/29/2026 4:26 AM, Maria Sophia wrote:

    The solution is below, but it's as simple as installing this one FOSS app.
    <https://f-droid.org/packages/name.lmj001.savetodevice>

    Now the desktop and the Android device WhatsApp will save PDF files easily.
    I would suggest to install this app instead:

    https://f-droid.org/en/packages/org.primftpd/

    It also adds the ability to save shareable files but it is
    also an ftpd server. You don't need to use WhatsApp to copy
    pdf files to the smartphone but you can just drag&drop
    them with the mouse in Windows explorer.

    You can also just open the pdf file (for example in
    Firefox) and then save the pdf file from the pdf reader.
    No need to install an extra app for this purpose (but
    the ftpd server is a must have anyhow).





    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to comp.sys.mac.system,alt.comp.os.windows-10,misc.phone.mobile.iphone on Thu Oct 29 16:00:38 2026
    From Newsgroup: alt.comp.os.windows-10

    Herbert Kleebauer wrote:
    I would suggest to install this app instead:

    https://f-droid.org/en/packages/org.primftpd/

    It also adds the ability to save shareable files but it is
    also an ftpd server. You don't need to use WhatsApp to copy
    pdf files to the smartphone but you can just drag&drop
    them with the mouse in Windows explorer.

    You can also just open the pdf file (for example in
    Firefox) and then save the pdf file from the pdf reader.
    No need to install an extra app for this purpose (but
    the ftpd server is a must have anyhow).

    Hi Herbert,

    Thanks for helping out, as you very often come up with great ideas that
    almost nobody else comes up with, so your solutions are always valuable.

    FTP servers work but the problem is we have to get the file out of the app first, and if we can't do that, then there is no file that can be FTP'd.

    Also, opening the file in Firefox (or, for that matter, in *anything*) presupposes you can share the file to that app which opens the PDF for
    viewing and, which saves the PDF (which is the 2nd desired constraint).

    Interestingly, Frank astutely pointed out that the desktop WA has a Save To. But the mobile WA does NOT have a save to. Instead, mobiles have Share-To.

    That turned out to be a learning experience, for me, as apparently Android (and iOS) are designed to not allow a direct "save as" from installed apps.

    My response to Andy, who first pointed that out to me, is below.

    But, I think the real issue is strategically structural, in that desktops
    have a "save as" philosophy, whereas mobiles use a "share to" instead.

    Luckily, I found a universal solution that turns a share-to into a save-as.

    *PSA: I found a GREAT way to add 'save to device' to the Android share sheet (which works on apps like WA that don't want you to share to the device!)*
    <https://xdaforums.com/t/psa-i-found-a-great-way-to-add-save-to-device-to-the-android-share-sheet-which-works-on-apps-like-wa-that-dont-want-you-to-share-to-the-device.4806835/>

    I love when we all work together to make the computer do exactly what
    we want the computer to do, and not only what the OEM wants it to do.

    ==== < cut here for response to Andy on strategy > ====
    Newsgroups: comp.mobile.android
    Subject: Re: What do you prefer for reading & saving PDFs on Android?
    Date: Thu, 29 Oct 2026 15:23:34 -0400
    Message-ID: <11c06fm$2vu8$1@nnrp.usenet.blueworldhosting.com>

    Andy Burns wrote:
    You simply can not blame me for WhatsApp NOT having a 'Save As' button.
    If "someone tells me that", they are a bona fide idiot

    But "save-as" isn't the android way, "share-to" is.

    Which you've found a utility to act as a bridge between sharing and
    saving ...

    Hi Andy,

    THANK YOU for that strategic vision!
    And, thank you for noticing it's not my fault WA has no "Save as" button.

    More importantly, you happen to know WHY WA doesn't have a "Save as" click.

    I treat your articles differently than most people's posts because you know more about Android than I do, so when you say 'it's not the Android way', I have to think about that, from the perspective of Android design strategy.

    The solution I came up with I already had because I used it to save APKs
    from the Google Play Store without having a Google login, which is a neat
    trick given 9,999 out of 10,000 people think that feat can't be done.

    But I didn't think to apply that APK-saving trick to WA saving until now.
    *PSA: I found a GREAT way to add 'save to device' to the Android share sheet (which works on apps like WA that don't want you to share to the device!)*
    <https://xdaforums.com/t/psa-i-found-a-great-way-to-add-save-to-device-to-the-android-share-sheet-which-works-on-apps-like-wa-that-dont-want-you-to-share-to-the-device.4806835/>

    Looking it up, apparently your purposefully helpful advice touches on a fundamental divergence in philosophy between desktop operating systems (Windows/macOS/Linux) and mobile operating systems (Android/iOS).

    Apparently, on a traditional desktop OS, apps are trusted (or given broad permission) to browse & write to a global, hierarchical file system.

    But when Google bought/designed Android (& Apple designed iOS), they
    shifted away from that chaotic desktop model for various reasons.

    I wasn't aware of that strategic mindset shift, until I just looked it up.
    a. App sandboxing
    b. Message-passing intents
    c. Bridging via the share sheet

    I'm impressed that you UNDERSTOOD the strategic design better than I did.
    I didn't even realize that though, until you said it, and I looked it up.

    You're right.
    Android apps don't really want to "do" a 'Save As', by design.

    Luckily, our workaround is effective because it leverages Android's intent architecture in a way the OS designers intended, but for a new purpose.

    Apparently, these little utilities like Save on Device register themselves
    with the Android system as a valid sharing target. When we tap "Share" in WhatsApp and pick Save on Device, WhatsApp passes the file data to the
    utility via an Android Intent.

    Because that utility does have permission to write to our local storage folders, it acts as the bridge that WhatsApp apparently refused to build.

    In summary, you've opened my eyes to WHY WhatsApp follows the rulebook of passing data via "Share" while, at the same time, the utility catches that
    data & applies the "Save" action that the desktop world takes for granted.

    Thank you for EXPLAINING the strategic LOGIC behind the decision of WA
    (and other apps) for not having something as useful as a "Save as" button.
    --
    Sometimes you can find helpful people on Usenet who know more than you do.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to comp.sys.mac.system,alt.comp.os.windows-10,misc.phone.mobile.iphone on Thu Oct 29 13:13:05 2026
    From Newsgroup: alt.comp.os.windows-10

    On 2026-10-28 20:26, Maria Sophia wrote:
    Woo hoo!

    Frank recently astutely noted on the Android newsgroup there is a save to device on the desktop WhatsApp but not a similar option in the Android WA.
    I agree, saving *should* be a feature of WhatsApp, but - contrary
    to the Windows version - the Android version of WhatsApp does not
    have a save (file) feature, only Share. And by default - at least
    my Samsung phone - Share does not have a a save choice either.
    So... you'll need a extra file manager to get that.

    Moments ago, I found a solution to that problem, which *adds* the Save on Device option to WhatsApp on Android so that they both work the same way.
    <https://i.postimg.cc/B6ryMZpn/saveasfile.jpg>

    The solution is below, but it's as simple as installing this one FOSS app.
    <https://f-droid.org/packages/name.lmj001.savetodevice>

    Now the desktop and the Android device WhatsApp will save PDF files easily.

    I don't use WhatsApp on my iPads so I ask the iPhone users if the WhatsApp
    on iOS can save directly to the device outside of WhatsApp storage?

    Probably not...

    As usual, Arlen/Andy/Maria/(too many nyms to count) is wrong:

    A PDF file sent to me via WhatsApp.

    I open it to view it.

    Then use the Share icon (the ubiquitous square with the upward facing arrow)...

    ...and choose "File".

    It was easy.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Herbert Kleebauer@klee@unibwm.de to comp.sys.mac.system,alt.comp.os.windows-10,misc.phone.mobile.iphone on Fri Oct 30 00:07:45 2026
    From Newsgroup: alt.comp.os.windows-10

    On 10/29/2026 9:00 PM, Maria Sophia wrote:
    Herbert Kleebauer wrote:

    I would suggest to install this app instead:

    https://f-droid.org/en/packages/org.primftpd/

    It also adds the ability to save shareable files but it is
    also an ftpd server. You don't need to use WhatsApp to copy
    pdf files to the smartphone but you can just drag&drop
    them with the mouse in Windows explorer.

    You can also just open the pdf file (for example in
    Firefox) and then save the pdf file from the pdf reader.
    No need to install an extra app for this purpose (but
    the ftpd server is a must have anyhow).

    FTP servers work but the problem is we have to get the file out of the app first, and if we can't do that, then there is no file that can be FTP'd.

    Now I'm confused. We started with the problem to transfer a pdf file
    from the PC to the smartphone. Once copied to the smartphone (for
    example by an ftp transfer) you can open the file with any pdf reader,
    for example Firefox.

    Then the idea was, if already installed, you can also use WhatsApp
    to transfer the pdf to the smartphone. But then you can only open
    the pdf file in a pdf reader but not directly store it on the disk,
    because WhatsApp doesn't provide a "save as". But this isn't a
    problem, because the pdf reader provides a "save as".


    Also, opening the file in Firefox (or, for that matter, in *anything*) presupposes you can share the file to that app which opens the PDF for viewing and, which saves the PDF (which is the 2nd desired constraint).

    But there is absolutely no problem using the combination WhatsApp/Firefox
    for pdf files.


    Interestingly, Frank astutely pointed out that the desktop WA has a Save To. But the mobile WA does NOT have a save to. Instead, mobiles have Share-To.

    If you want to transfer files of any type, Firefox is of no help. Then
    you need an app which doesn't interpret the content of the file, but
    just offers a "save as".


    Luckily, I found a universal solution that turns a share-to into a save-as.

    *PSA: I found a GREAT way to add 'save to device' to the Android share sheet (which works on apps like WA that don't want you to share to the device!)*
    <https://xdaforums.com/t/psa-i-found-a-great-way-to-add-save-to-device-to-the-android-share-sheet-which-works-on-apps-like-wa-that-dont-want-you-to-share-to-the-device.4806835/>
    My answer was: if you install an app for this purpose, better install https://f-droid.org/en/packages/org.primftpd/

    Primitive FTPd not only provides the "save as" function as your app,
    but also an FTPd server. This way you don't have to use WhatsApp for
    the file transfer but can do it by a simple drag&drop with the mouse
    in Windows explorer. Primitive FTPd is a replacement for your suggested
    app and you also can use it as FTPd server.








    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nick Charles@none@none.none to alt.comp.os.windows-10,comp.sys.mac.system,misc.phone.mobile.iphone on Fri Oct 30 00:27:17 2026
    From Newsgroup: alt.comp.os.windows-10

    On Oct 29, 2026 at 4:13:05rC>PM EDT, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-10-28 20:26, Maria Sophia wrote:

    I don't use WhatsApp on my iPads so I ask the iPhone users if the WhatsApp >> on iOS can save directly to the device outside of WhatsApp storage?

    Probably not...

    As usual, Arlen/Andy/Maria/(too many nyms to count) is wrong:

    A PDF file sent to me via WhatsApp.

    I open it to view it.

    Then use the Share icon (the ubiquitous square with the upward facing arrow)...

    ...and choose "File".

    It was easy.

    But! IT is a self-proclaimed EXPERT on iOS!!! Just ask IT and IT will tell you. Over and over.

    Nevermind that IT:

    Did not know that iOS has a built-in music playing app.

    Does not know how to use the Notes app.

    Does not know how to use the Files app.

    Did not know that the Files app can network to any computer.

    Thinks that Android is more secure than iOS.

    Thinks that every iOS update is the ENTIRE 10GB (or whatever size) iOS, even
    if just a single line of code was changed. Because he thinks that iOS is monolithic. Nevermind that you can see the exact size of EVERY iOS update. Which explains why x.0.0 versions take more time to DL/install than x.x.1 versions.

    Thinks that all apps will stop working if you are not logged into the "Apple Mainframes".

    Common Knowledge. Its not what you know. Its what you THINK you know.

    <https://www.youtube.com/watch?v=e0HGEZXTy8Y>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.comp.os.windows-10,comp.sys.mac.system,misc.phone.mobile.iphone on Thu Oct 29 22:57:05 2026
    From Newsgroup: alt.comp.os.windows-10

    Nick Charles wrote:
    On Oct 29, 2026 at 4:13:05rC>PM EDT, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-10-28 20:26, Maria Sophia wrote:

    I don't use WhatsApp on my iPads so I ask the iPhone users if the WhatsApp >>> on iOS can save directly to the device outside of WhatsApp storage?

    Probably not...

    As usual, Arlen/Andy/Maria/(too many nyms to count) is wrong:

    A PDF file sent to me via WhatsApp.

    I open it to view it.

    Then use the Share icon (the ubiquitous square with the upward facing
    arrow)...

    ...and choose "File".

    It was easy.

    But! IT is a self-proclaimed EXPERT on iOS!!! Just ask IT and IT will tell you. Over and over.

    Nevermind that IT:

    Did not know that iOS has a built-in music playing app.

    Does not know how to use the Notes app.

    Does not know how to use the Files app.

    Did not know that the Files app can network to any computer.

    Thinks that Android is more secure than iOS.

    Thinks that every iOS update is the ENTIRE 10GB (or whatever size) iOS, even if just a single line of code was changed. Because he thinks that iOS is monolithic. Nevermind that you can see the exact size of EVERY iOS update. Which explains why x.0.0 versions take more time to DL/install than x.x.1 versions.

    Thinks that all apps will stop working if you are not logged into the "Apple Mainframes".

    Common Knowledge. Its not what you know. Its what you THINK you know.

    <https://www.youtube.com/watch?v=e0HGEZXTy8Y>

    Why do they Apple religious nutcases have to prove me right about them.
    Every time they post.

    Sigh. Unfortunately, the iOS nutcases who post to the Apple newsgroups
    clearly know nothing about how the iOS operating system really works.

    Worse, they prove me correct about them every single time they defend
    iOS to the death no matter what, using the first absurd excuse they can
    think of that pops into their heads.

    To wit... -----------------------------------------------------------------------
    Thinks that all apps will stop working if you are not logged into the "Apple Mainframes".

    Of all common consumer operating systems, only iOS requires users to
    maintain a privacy-robbing mothership account on the device just so that
    you can install software.

    Nobody else. Just Apple.

    Worse, if the iOS app needs an update, and you deleted your App Store
    account used to get the app in the first place, you're screwed. It can't be updated.

    If you think that's not true, then explain WHY you think it's not correct. -----------------------------------------------------------------------
    Thinks that every iOS update is the ENTIRE 10GB

    It's no longer surprising Apple owners have absolutely no idea that the iOS updates are monolithic from the factory and then delta updated on devices.

    When Apple ships an iOS update to an iPhone, it is packaged and delivered
    as a single, unified firmware image (an .ipsw file container). Apple cannot push a fragmented, a la carte bundle of separate, independent OS component packages to your phone the way Windows or Android can (outside of minor exceptions like the relatively new Rapid Security Responses). From the
    factory build pipeline to the end-user's download screen, it is treated, compiled, and deployed as a single block.

    If you think that's not true, then explain WHY you think it's not correct.
    (And notice the "delta" you "think" you understand, isn't the point here.)

    At Apple's engineering headquarters and build servers, iOS is compiled and packaged as a single, unified block of firmware (the .ipsw master image).
    Apple does not maintain modular, standalone OS package repositories like
    Linux distros or Android's Project Mainline. The master artifact built at
    the factory is a monolith.

    The Delivery Mechanism is a Delta Patch: When that monolith is pushed Over-The-Air (OTA) to an active device, Apple's update server dynamically generates a targeted, differential patch (a delta) tailored precisely to
    what is already sitting on that specific user's flash storage.

    Apple nutjobs confuse the delivery method with the operating system's architecture. But it's the architecture why iOS has so many exploits.

    Note this monolithic structure is IMPORTANT because it's a huge reason
    why Apple iOS software is so buggy. They have to COLLECT all the bugs! -----------------------------------------------------------------------

    I could go on, but the point is the Apple nutcases don't know anything
    about how Apple products work. They just hate that they work the way they
    do, and they are religious nutjobs that deny every fact about Apple.

    Using the first absurd excuse that they can think of.

    It's what Apple religious zealot nutcases do.
    1. None of them have any education
    2. All of them believe EVERYTHING Apple marketing told them
    3. And all defend Apple to the death, no matter what
    Even as not one of them understands a single thing about Apple products.
    --
    On Usenet, unfortunately, are those who couldn't get a high school diploma.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to comp.sys.mac.system,alt.comp.os.windows-10,misc.phone.mobile.iphone on Thu Oct 29 23:49:52 2026
    From Newsgroup: alt.comp.os.windows-10

    Herbert Kleebauer wrote:
    FTP servers work but the problem is we have to get the file out of the app >> first, and if we can't do that, then there is no file that can be FTP'd.

    Now I'm confused. We started with the problem to transfer a pdf file
    from the PC to the smartphone. Once copied to the smartphone (for
    example by an ftp transfer) you can open the file with any pdf reader,
    for example Firefox.

    Yikes!

    Ooops. You're right. I conflated two different iOS-to:from-Windows issues
    1. Getting the clipboard between iOS and Windows
    2. Getting a WhatsApp attached PDF between iOS and Windows

    Never in the history of my posting to Usenet did I not own my mistakes.
    that was a mistake. A faux pas. Mea culpa. I agree with you. Sorry.

    I openly and publicly apologize for mixing up two concurrent threads.
    Nolo contendere.

    Then the idea was, if already installed, you can also use WhatsApp
    to transfer the pdf to the smartphone. But then you can only open
    the pdf file in a pdf reader but not directly store it on the disk,
    because WhatsApp doesn't provide a "save as". But this isn't a
    problem, because the pdf reader provides a "save as".

    You bring up, as always, a good point for us to discuss, truthfully.

    You're almost certainly correct that some PDF readers, once they read the
    PDF, will be able to save that PDF, OUTSIDE of protected Android storage.

    I actually looked that question up just now, and it seems about 50:50.
    1. About half can NOT save to storage outside their scoped storage
    2. But about half can

    Apparently, many viewers have no save, export, or download function.
    Worse, many try to push our files into their cloud storage solution first.
    And, keep in mind, Android's scoped storage restrictions.

    Even if the app does want to save it, current Android versions block apps
    from writing freely across the file system unless they invoke Android's
    native system file picker (ACTION_CREATE_DOCUMENT). So, an anemic PDF
    reader can fail to trigger this correctly, resulting in silent crashes or "Permission Denied" errors when we try to save.

    I've run into this problem (not with PDFs, but with other files).
    So has Andy. I'm sure many of us have run into this problem.

    Especially with apps built on older versions of Android.
    Or when we upgrade our Android to newer versions with stricter permissions.

    In decades of posting to Usenet, I've always strived to craft brilliantly elegant solutions, as do you, where I think the save-on-device trick allows
    us to not have to trust a random PDF reader to have a competent export function. With a dedicated share-sheet tool, we can force the file out of WhatsApp's sandbox straight to whatever local folder we actually want.

    Also, opening the file in Firefox (or, for that matter, in *anything*)
    presupposes you can share the file to that app which opens the PDF for
    viewing and, which saves the PDF (which is the 2nd desired constraint).

    But there is absolutely no problem using the combination WhatsApp/Firefox
    for pdf files.

    In all my decades on Usenet, I have NEVER disputed a logically sound
    argument, where I'm sure opening in a web browser will work in most cases.

    But please look at this WA PDF OpenWith screenshot from yesterday, Herbert.
    <https://i.postimg.cc/tRmWnpFP/whatsappshare.jpg>

    Do you see any web browsers in that Android WhatsApp PDF OpenWith menu?
    I don't.

    Now, you might claim I don't have web browsers, but I have a billion.
    So why don't the web browsers show up in the WhatsApp PDF OpenWith menu?

    Looking up WHY there is no web browser in the WhatsApp PDF OpenWith menu...

    The web browsers aren't showing up in that WhatsApp "Open With" menu likely because of MIME type and Intent Filter filtering rules on Android.

    When WhatsApp triggers an intent to pass a file, it specifies the MIME type
    (in this case, application/pdf) or hands off a specific content URI schema.

    Even though standard web browsers 'can' render PDFs, many mobile browsers register their intent filters primarily around web URL schemes (http://, https://) or specific web-based document types, rather than raw local
    binary file intents coming out of a chat app's document picker.

    Alternatively, my research shows perhaps WhatsApp's custom share
    implementation explicitly narrows the target list to apps registered as dedicated document viewers or file handlers.

    I THANK YOU for this extra test, which I didn't check until just now, but you've just VALIDATED PERFECTLY why the brilliant solution we came up with
    is better.

    Assuming a browser will just "always be there" to catch and save a file
    from a chat app ignores how messy Android's app-to-app communication
    actually is.

    Interestingly, Frank astutely pointed out that the desktop WA has a Save To. >> But the mobile WA does NOT have a save to. Instead, mobiles have Share-To.

    If you want to transfer files of any type, Firefox is of no help. Then
    you need an app which doesn't interpret the content of the file, but
    just offers a "save as".

    Yes. Indeed. We agree. Again, I've never once in my entire set of decades posting to Usenet ever disagreed with any logically sensible point of view.

    What I love about this brilliantly elegant solution, is a tiny FOSS utility allows almost any app to "save as" from the "share to" menu.

    It's ingenious. It's brilliant. It's simple. It's robust. It just works!
    But if people don't like it, that's fine. It's just yet another method.

    Luckily, I found a universal solution that turns a share-to into a save-as. >>
    *PSA: I found a GREAT way to add 'save to device' to the Android share sheet (which works on apps like WA that don't want you to share to the device!)*
    <https://xdaforums.com/t/psa-i-found-a-great-way-to-add-save-to-device-to-the-android-share-sheet-which-works-on-apps-like-wa-that-dont-want-you-to-share-to-the-device.4806835/>
    My answer was: if you install an app for this purpose, better install https://f-droid.org/en/packages/org.primftpd/

    Primitive FTPd not only provides the "save as" function as your app,
    but also an FTPd server. This way you don't have to use WhatsApp for
    the file transfer but can do it by a simple drag&drop with the mouse
    in Windows explorer. Primitive FTPd is a replacement for your suggested
    app and you also can use it as FTPd server.

    I have an excellent memory (all intelligent people must have a good memory
    in order to put together things to make reasonable conclusions), so I'm
    well aware we've had this discussion in the past, multiple times already.

    See below where I include my responses to you back in January of this year.

    I don't know if you know how many tutorials I've written in the past on not only Primitive FTPd but a BILLION other FTP server solutions for Android/Windows. Seriously. A billion. I know them all. More than anyone.

    Just *LOOK* at my Windows software hierarchy to get a hint at how many.
    <https://i.postimg.cc/fRxm39Mj/ftp.jpg>

    Don't even get me started on how many similar Android utilities I tested.
    AirDroid <https://www.airdroid.com/personal/>
    ADB <https://developer.android.com/tools/adb>
    AFT MTP client <https://whoozle.github.io/android-file-transfer-linux/>
    DirectNetDrive <http://www.directnet-drive.net/>
    FTPUse <https://www.ferrobackup.com/download/FtpUseInst.exe>
    Ftpuse <https://www.ferrobackup.com/map-ftp-as-disk.html>
    Fb-adb Android Linux shell <https://github.com/facebook/fb-adb>
    Go-mtpfs MTP FUSE filesystem <https://github.com/hanwen/go-mtpfs>
    Gphotofs Camera Linux mount <http://www.gphoto.org/proj/gphotofs/>
    JMTP FS <https://github.com/JasonFerrara/jmtpfs>
    KDEconnect <https://play.google.com/store/apps/details?id=org.kde.kdeconnect>
    Kies Connect <https://www.samsung.com/africa_en/support/kies/>
    LibIconv <http://gnuwin32.sourceforge.net/packages/libiconv.htm>
    LibMTP <https://github.com/hanwen/go-mtpfs>
    LibMTP <https://sourceforge.net/projects/libmtp/>
    LibMTP library MTP implementation <http://libmtp.sourceforge.net>
    LibUSB Win32 <http://libusb-win32.sourceforge.net/>
    LibUsbK <https://sourceforge.net/projects/libusb-win32/>
    LibiConv <http://gnuwin32.sourceforge.net/packages/libiconv.htm>
    MTP support on KDE <https://cgit.kde.org/kio-mtp.git>
    MTPDrive <http://mtpdrive.com/download.html>
    MTPSync <https://www.adebenham.com/mtpsync/>
    MTPdude <http://mtpdude.sourceforge.net>
    MTPfs FUSE filesystem <https://www.adebenham.com/mtpfs/>
    NetDrive 1.3.2.0 <https://filehippo.com/download_netdrive/12615/>
    NetDrive 3.6.571 <http://netdrive.net/ (deprecated)
    Nitroshare <https://play.google.com/store/apps/details?id=net.nitroshare.android>
    PhoneLink <https://www.samsung.com/us/support/answer/ANS00083910/>
    SFTP Net Drive <https://www.nsoftware.com/sftp/netdrive/>
    SideSync <https://play.google.com/store/apps/details?id=com.sidesync.freeapp>
    SMB Cifs (client) X-Plore <https://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore>
    SMB Cifs (root) <https://play.google.com/store/apps/details?id=com.imperioustech.www.sambaserver>
    Scrcpy/sndcpy <https://github.com/Genymobile/scrcpy>
    Termux copy <https://github.com/termux>
    WebDav <https://play.google.com/store/apps/details?id=com.theolivetree.webdavserver>
    WebDrive <https://webdrive.com/download/>
    XNJB Mac OS X GUI <http://www.wentnet.com/projects/xnjb/>

    See the appended "ftp versus webdav" below, which we did back in January.

    I've tested every single free file-copy utility ever suggested on the Android/Windows newsgroups, for decades, and FTP is substandard compared to others. It just is. There are reasons for that. But that's not for now.

    Now, I'm NOT saying FTP doesn't work. It does work. It works fine.
    But other solutions are FAR BETTER for many reasons, than FTP, IMHO.

    For example, WebDav. Which allows us to MOUNT the Android phone as a drive!
    <https://i.postimg.cc/6371SxNd/mountandroidonwindows.jpg>

    Anyway, I get it you sugges FTP and there's nothing wrong with it, per se. Since I've tested EVERYTHING ever suggested, I personally would use WebDav.

    But that's not to say that FTP isn't workable.
    Let's agree on that (since we've had this discussion many times).

    See below for proof.


    ==== < cut here for our recent webdav versus ftp discussions > ==== Newsgroups:
    alt.comp.os.windows-11,alt.comp.os.windows-10,comp.mobile.android
    Subject: Discussion of FTP vs WebDav for Android/iOS filesystem sharing on Windows PC
    Date: Tue, 27 Jan 2026 12:11:06 -0500
    Message-ID: <10larja$2ai$1@nnrp.usenet.blueworldhosting.com>

    This is intended to be a formal team discussion of the topic:
    FTP vs WebDav for Android/iOS filesystem sharing on Windows PC

    This thread is intended to summarize & then discuss the practical
    differences between FTP and WebDAV for Android or iOS filesystem sharing on
    a Windows PC.
    Protocol Network Location Drive Letter Native Needs 3rd Party
    FTP Yes No Yes Yes
    WebDAV Yes Yes Yes No

    The goal is to clarify what Windows can do natively, versus what requires third-party tools, and what the terms share, mount, network drive, and
    network location actually mean (since Windows terminology is confusing).

    IMHO:
    1. FTP is simple. So is WebDAV. On Windows. On Android.
    2. Both are native to Windows. Both have free servers on Android.
    3. There's no difference in simplicity between them (as far as I can tell).

    FTP:
    A. FTP is fine for ad-hoc file transfers.
    B. But FTP cannot provide a native drive letter on Windows.
    C. FTP requires third-party tools for filesystem integration.

    WebDAV:
    a. WebDAV provides native drive-letter mounting on Windows.
    b. WebDAV integrates cleanly with Windows scripts, applications & tools.
    c. For full filesystem interoperability between Android or iOS and Windows,
    WebDAV is more capable than FTP if mapping a drive is one of your needs.

    Occam's Razor says a simple solution that solves all needs is likely best.

    FTP ON WINDOWS

    1. Windows includes a native FTP client, but it does not include an FTP
    filesystem redirector.

    2. Because there is no redirector, Windows cannot mount an FTP server as a
    drive letter.

    3. Windows Explorer can open an FTP server as a virtual folder.
    This is called a Network Location, not a Network Drive.

    4. Example of a Network Location:
    C:\> explorer.exe ftp://username:password@host/

    5. This is not a mount. It does not create a drive letter.
    It does not behave like a filesystem.
    It is only Explorer acting as an FTP client.

    6. To get a real drive letter for FTP, a third-party redirector
    is required.

    7. Example of a third-party mount:
    C:\> ftpuse Z: ftp://192.168.1.2 user password

    8. This works apparently, but it is not native Windows functionality.

    WEBDAV ON WINDOWS

    1. Windows includes a native WebDAV filesystem redirector called WebClient.

    2. Because the redirector is built in, Windows can mount WebDAV as a real
    network drive with a drive letter.

    3. No third-party tools are required.

    4. Example of a native WebDAV mount:
    C:\> net use Z: \\192.168.1.2@8000\DavWWWRoot /USER:jim *
    /PERSISTENT:YES

    5. DavWWWRoot is a Windows native keyword that has existed since the days
    of Windows XP and Windows Server 2003.

    6. This is a mapped network drive, not just a network location.

    ROLES: SHARE VS MOUNT
    a. A server shares a filesystem.
    b. A client mounts a filesystem.
    c. FTP servers on Android can share, but they cannot mount anything.
    d. WebDAV servers on Android can share & Windows can mount them natively.

    Occam's Razor:

    i. The simplest solution is not what makes any solution likely the best.
    ii. The best solution is usually the simplest one that solves all needs.

    Certainly FTP is simple, but FTP is limited.
    FTP cannot provide a drive letter without third-party Windows tools.

    Just as certainly, WebDAV is simple too. Just as simple as FTP is, IMHO.
    And WebDAV provides native drive-letter mounting on Windows.

    WebDAV solves more requirements than FTP in a Windows environment.
    If you don't need or want native drive-letter mapping, then FTP is fine.

    But they're not equivalent.
    I. FTP is less functional in that respect than WebDav is.
    II. Yet, both are super simple.

    KEY QUESTION FOR THIS TEAM DISCUSSION

    Q: What does FTP do better than WebDAV for Android or iOS filesystem
    interoperability on a Windows PC on a local LAN?

    A: ?
    --
    Usenet is a forum for discussing essential tools we use to solve problems.


    Newsgroups: comp.mobile.android,alt.comp.os.windows-11
    Subject: Re: Erracitic results, export chats from Whatsapp to windows 11.
    Date: Tue, 27 Jan 2026 11:34:36 -0500
    Message-ID: <10lapes$1g47$1@nnrp.usenet.blueworldhosting.com>

    Herbert Kleebauer wrote:
    But I prefer WebDav over FTP because it's just like sliced bread is.
    <https://i.postimg.cc/4yKdxWS4/chart-ftpshare-vs-webdavdrive.jpg>

    You don't need an external program (ftpuse) to access the
    Android file system. It's all built into Windows explorer.

    Hi Herbert,

    Windows can "map" an FTP server, but not as a drive letter.
    It maps it as a Network Location, not as a Network Drive.

    That's an important distinction that matters to the discussion below.

    We're old friends. :)

    We have this same discussion *every* time I bring up WebDav to your FTP.
    For years (and years), you've said the same thing, as have I about them.

    But you haven't seemed to discuss shares and mounts when we discuss them.
    There are fundamental differences when it comes to Windows mounts & shares!

    One is mere mapping; the other is mounting as a drive letter.
    They're not the same thing.

    Shares and Mounts are "roles" on Windows, not protocol features.
    Windows has an FTP client (ftp.exe), but that client cannot mount.

    Tools like ftpuse, netdrive, winfsp + curlftpfs, etc. add a mount layer.
    That is, they can "map a network drive" as a drive letter on Windows.

    1. FTPUse can mount ftp server filesystems on Android to Windows:
    C:\> ftpuse Z: ftp://192.168.1.2 user password
    Windows calls this a "mounted network drive via a redirector"
    2. WebDav server filesystems on Android can be mounted on Windows
    C:\> net use Z: http://android-device:port/dav
    Windows calls this a "mapped network drive (native)".
    3. But FTP servers on Android cannot mount in and of itself.
    C:\> explorer.exe ftp://username:password@host/
    Windows calls this a "mapped network location".

    Notice a "mapped network location" is not a "mapped network drive".
    That's a critically important distinction that I need you to understand.

    You claim FTP is simpler. It's not but being simpler isn't important.
    I claim WebDav is not only as simple, but vastly more powerful.

    With WebDav, you can mount the entire Android filesys as a Windows drive.
    It's just as simple as FTP but it's vastly more powerful in that respect.

    I have used FTP for decades, just as you have used FTP for decades.
    But have you ever tried to use WebDav? If not, then you need to try it. :)

    With that in mind, I understand what you're trying to say, since you do
    very much love FTP. I need to make it clear that I used to love FTP too, decades ago, since I grew up in a Unix world.

    But are your FTP connections Windows network shares or not?
    That's one key difference between FTPUse versus just plain old FTP.

    Having pointed out the network share, we have to remember Occam's Razor.

    It's not the simplest solution that is likely best, and even if it was, FTP
    is no simpler than WebDav in terms of Android/iOS:Windows filesys interoperability in a home environment on a local LAN (like ours are).

    Occam's Razor has TWO tenets:
    a. Simple
    b. Solves all needs

    The simplest solution that solves all the needs is likely the better.
    So what matters is what are our respective needs.

    Mine are to seamlessly "mount" (or share) the mobile filesys with Windows. FTPUse claims to be able to do that; however, I do not myself use FTPUse,
    so if you deprecate FTPUse, that changes nothing for me as it's just a way
    to "mount" a file system as a Windows drive (since FTP already shares).

    Note the Windows difference between a share & a mount, as it's critical.

    Like you, I used to use FTP for decades (sftp, filezilla, winscp, tftp2, tftp64, netdrive, directnetdrive, ftpdrive, sftpnetdrive, webdrive, expanddrive, etc.) as my PC file system is littered with ftp variants.

    Yet, I haven't used FTP in years because I found something (much) better.

    Bear in mind I'm an interoperability hound where I expect an extremely high level for interoperability between Android & Windows, so "just" having the file explorer see all of Android (including root) isn't enough for me.

    I've tested *every* solution (AFAIK) ever suggested on this newsgroup for filesystem access between the two (actually three including iOS) systems.
    Offhand, some of the Android/Windows file-sharing solutions are
    AirDroid <https://www.airdroid.com/personal/>
    ADB <https://developer.android.com/tools/adb>
    AFT MTP client <https://whoozle.github.io/android-file-transfer-linux/>
    DirectNetDrive <http://www.directnet-drive.net/>
    FTPUse <https://www.ferrobackup.com/download/FtpUseInst.exe>
    Ftpuse <https://www.ferrobackup.com/map-ftp-as-disk.html>
    Fb-adb Android Linux shell <https://github.com/facebook/fb-adb>
    Go-mtpfs MTP FUSE filesystem <https://github.com/hanwen/go-mtpfs>
    Gphotofs Camera Linux mount <http://www.gphoto.org/proj/gphotofs/>
    JMTP FS <https://github.com/JasonFerrara/jmtpfs>
    KDEconnect <https://play.google.com/store/apps/details?id=org.kde.kdeconnect>
    Kies Connect <https://www.samsung.com/africa_en/support/kies/>
    LibIconv <http://gnuwin32.sourceforge.net/packages/libiconv.htm>
    LibMTP <https://github.com/hanwen/go-mtpfs>
    LibMTP <https://sourceforge.net/projects/libmtp/>
    LibMTP library MTP implementation <http://libmtp.sourceforge.net>
    LibUSB Win32 <http://libusb-win32.sourceforge.net/>
    LibUsbK <https://sourceforge.net/projects/libusb-win32/>
    LibiConv <http://gnuwin32.sourceforge.net/packages/libiconv.htm>
    MTP support on KDE <https://cgit.kde.org/kio-mtp.git>
    MTPDrive <http://mtpdrive.com/download.html>
    MTPSync <https://www.adebenham.com/mtpsync/>
    MTPdude <http://mtpdude.sourceforge.net>
    MTPfs FUSE filesystem <https://www.adebenham.com/mtpfs/>
    NetDrive 1.3.2.0 <https://filehippo.com/download_netdrive/12615/>
    NetDrive 3.6.571 <http://netdrive.net/ (deprecated)
    Nitroshare <https://play.google.com/store/apps/details?id=net.nitroshare.android>
    PhoneLink <https://www.samsung.com/us/support/answer/ANS00083910/>
    SFTP Net Drive <https://www.nsoftware.com/sftp/netdrive/>
    SideSync <https://play.google.com/store/apps/details?id=com.sidesync.freeapp>
    SMB Cifs (client) X-Plore <https://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore>
    SMB Cifs (root) <https://play.google.com/store/apps/details?id=com.imperioustech.www.sambaserver>
    Scrcpy/sndcpy <https://github.com/Genymobile/scrcpy>
    Termux copy <https://github.com/termux>
    WebDav <https://play.google.com/store/apps/details?id=com.theolivetree.webdavserver>
    WebDrive <https://webdrive.com/download/>
    XNJB Mac OS X GUI <http://www.wentnet.com/projects/xnjb/>
    (this is mostly offhand so I likely missed as many as I listed)

    There likely hasn't ever been an interoperability tool suggested on this newsgroup in the past decade (Windows 10 anyway) that I haven't tested.

    Since I write scripts on Windows that access the Android file system, I
    employ a permanent drive letter so that Android is seamless with Windows.
    net use Z: \\102.168.1.2@8000\DavWWWRoot /USER:joe * /PERSISTENT:YES

    Note that DavWWWRoot is a Windows keyword!
    The Windows DavWWWRoot keyword has nothing (per se) to do with Android.

    Windows natively knows all about DavWWWRoot, and it has been so since 2001.
    For me, there is no distinction between Windows & Android file systems.

    They're one and the same.
    1. Windows is accessible to me from Android all the time (when at home)
    2. Android is accessible to me from Windows all the time (when at home)

    Everything I do on Windows I do on Android at the same time, in fact, so
    it's not only that Android is a drive letter on Windows in my setup, but
    the Windows clipboard is the Android clipboard, and the PC mouse is the Android tap and the PC keyboard is the Android keyboard and the PC audio is the Android audio, etc., such that I operate Android completely on the PC.

    As with FTP, nothing needs to be installed on Windows for WebDav to mount
    your entire Android file system (yes, root too!) as a Windows drive letter. >> <https://i.postimg.cc/1zrmSmQc/davroot.jpg> Windows can see Android root!

    Already the first line is a lie.

    Hmmm.... nothing needs to be installed on Windows for WebDav to mount the entire file system onto the PC. All you need to do is run this command:
    net use Z: \\192.168.1.2@8000\DavWWWRoot /USER:jim * /PERSISTENT:YES

    Note that DavWWWRoot has been a Windows keyword since, oh, around 2001.

    || Native Windows Integration
    || FTP Server on Android/iOS: Requires a separate FTP client application
    || Windows Drive over WebDAV on Android/iOS: Integrated for drive mapping via Explorer

    No separate FTP client is necessary!

    Again and again we have this discussion Herbert, so I get it that Windows
    has FTP native, so you don't need to tell me that basic fact about FTP.

    I used FTP longer than my own children have lived & they have children now.
    But IMHO, FTP sucks when you compare it to WebDAV for iOS/Android interops.

    You do know Windows long ago deprecated FTP as insecure, but that's not my beef with FTP as I used Unix FTP for decades long before the IBM PC.

    All you need on Windows is to use the "net use" command to mount Android:
    C:\> net use Z: \\102.168.1.2@8000\DavWWWRoot /USER:jim * /PERSISTENT:YES

    The simpler solution is always the better solution.

    Occam's Razor says it's not the simplest solution, but the simplest
    solution that solves All the problems that is the better solution.

    FTP is simple. I grant you that.
    But so is WebDav.

    What can FTP do that WebDav doesn't already do, for example?

    Once you figure out that there's nothing (that I can think of),
    then it's time to ask what WebDav does that FTP doesn't do.

    For example, how do you permanently mount Android on Windows using FTP?

    I start
    Primitive ftpd on the phone (just a finger tip) and open
    an explorer window on the pc. I put the cursor into the
    address bar of explorer and use the QR-code scanner to
    scan the QR-code on the phone. That's all. Now in the
    explorer window I can access the Android file system (including
    SD card) and use drag&drop like in a local explorer window.

    After the file transfer I stop Primitive ftpd and then nothing
    is running on the phone which could be used as entry point
    for illegal accessing the phone from outside.

    I don't do anything and my entire Android phone is permanently mounted on Windows the moment I boot up my Android phone and I boot up Windows.

    Remember, even though WebDav is even simpler than FTP is, it's not the simplest solution is the better solution since FTP can't do what WebDav
    does (AFAIK) without extra tools (which you and I both equally shun).

    There's nothing wrong, per se, with you using the inferior FTP solution
    since you're comfortable with it, just as there's nothing wrong with me
    using the superior WebDAV solution since it's partly user preference.

    But please don't get Occam's Razor wrong with respect to "simple solutions"
    as it's not the simplest solution that's likely best, but the simplest solution that solves all the problems that is likely best.

    WebDav is superior to FTP in all respects (as far as I can tell).

    If you think that statement is incorrect, you're welcome to think so, but
    you first would need to answer this obvious question for me to believe it:
    Q: What does FTP do better than WebDav in terms of Android:Windows
    filesystem interoperability (on a Local LAN, in a home environment)?
    A: ?
    --
    Note we've had this same discussion for years, where I don't see a single advantrage of FTP over WebDAV but that's why the answer is so important .
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Herbert Kleebauer@klee@unibwm.de to comp.sys.mac.system,alt.comp.os.windows-10,misc.phone.mobile.iphone on Fri Oct 30 07:30:11 2026
    From Newsgroup: alt.comp.os.windows-10

    On 10/30/2026 4:49 AM, Maria Sophia wrote:
    Herbert Kleebauer wrote:

    What I love about this brilliantly elegant solution, is a tiny FOSS utility allows almost any app to "save as" from the "share to" menu.

    It's ingenious. It's brilliant. It's simple. It's robust. It just works!
    But if people don't like it, that's fine. It's just yet another method.

    Primitive FTPd not only provides the "save as" function as your app,
    but also an FTPd server. This way you don't have to use WhatsApp for
    the file transfer but can do it by a simple drag&drop with the mouse
    in Windows explorer. Primitive FTPd is a replacement for your suggested
    app and you also can use it as FTPd server.

    Now, I'm NOT saying FTP doesn't work. It does work. It works fine.
    But other solutions are FAR BETTER for many reasons, than FTP, IMHO.

    You misunderstood. I didn't suggest to install an FTP sever because
    then you don't need a "save as" app. I just said, there is at least
    one other "save as" app (and maybe many, many more) and that is https://f-droid.org/en/packages/org.primftpd/

    Now, if there are many apps for the same purpose, you have to
    make the decision, which one to install. And here primitiveFTPd
    has an big advantage, it not only provides the "save as" function
    but also is an ftpd server (which is it's main purpose). And a
    ftp server on a smartphone (I suppose an ftp server is also
    available for the iPhone) is very useful, because you can copy
    files from and to the phone by a simple drag&drop with the
    mouse in Windows explorer. Again, this doesn't mean an ftp
    server is the only or best way to copy files to the smartphone.
    But when you want to install a "save as" app, why not use one
    which offers this additional feature.







    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan@nuh-uh@nope.com to alt.comp.os.windows-10,comp.sys.mac.system,misc.phone.mobile.iphone on Sat Oct 31 14:38:21 2026
    From Newsgroup: alt.comp.os.windows-10

    On 2026-10-29 19:57, Maria Sophia wrote:
    Nick Charles wrote:
    On Oct 29, 2026 at 4:13:05rC>PM EDT, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-10-28 20:26, Maria Sophia wrote:

    I don't use WhatsApp on my iPads so I ask the iPhone users if the WhatsApp >>>> on iOS can save directly to the device outside of WhatsApp storage?

    Probably not...

    As usual, Arlen/Andy/Maria/(too many nyms to count) is wrong:

    A PDF file sent to me via WhatsApp.

    I open it to view it.

    Then use the Share icon (the ubiquitous square with the upward facing
    arrow)...

    ...and choose "File".

    It was easy.

    But! IT is a self-proclaimed EXPERT on iOS!!! Just ask IT and IT will tell >> you. Over and over.

    Nevermind that IT:

    Did not know that iOS has a built-in music playing app.

    Does not know how to use the Notes app.

    Does not know how to use the Files app.

    Did not know that the Files app can network to any computer.

    Thinks that Android is more secure than iOS.

    Thinks that every iOS update is the ENTIRE 10GB (or whatever size) iOS, even >> if just a single line of code was changed. Because he thinks that iOS is
    monolithic. Nevermind that you can see the exact size of EVERY iOS update. >> Which explains why x.0.0 versions take more time to DL/install than x.x.1
    versions.

    Thinks that all apps will stop working if you are not logged into the "Apple >> Mainframes".

    Common Knowledge. Its not what you know. Its what you THINK you know.

    <https://www.youtube.com/watch?v=e0HGEZXTy8Y>

    Why do they Apple religious nutcases have to prove me right about them.
    Every time they post.
    I love the gracious way you acknowledge you were completely wrong when
    you claimed that under iOS you could "Probably not..." "save directly to
    the device outside of WhatsApp storage".

    Oh, right!

    You completely ignored the facts presented to you...

    ...again!
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nick Charles@none@none.none to misc.phone.mobile.iphone,alt.comp.os.windows-10,comp.sys.mac.system on Sat Oct 31 22:09:58 2026
    From Newsgroup: alt.comp.os.windows-10

    Alan <nuh-uh@nope.com> wrote:
    On 2026-10-29 19:57, Maria Sophia wrote:
    Nick Charles wrote:
    On Oct 29, 2026 at 4:13:05rC>PM EDT, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-10-28 20:26, Maria Sophia wrote:

    I don't use WhatsApp on my iPads so I ask the iPhone users if the WhatsApp
    on iOS can save directly to the device outside of WhatsApp storage?

    Probably not...

    As usual, Arlen/Andy/Maria/(too many nyms to count) is wrong:

    A PDF file sent to me via WhatsApp.

    I open it to view it.

    Then use the Share icon (the ubiquitous square with the upward facing
    arrow)...

    ...and choose "File".

    It was easy.

    But! IT is a self-proclaimed EXPERT on iOS!!! Just ask IT and IT will tell >>> you. Over and over.

    Nevermind that IT:

    Did not know that iOS has a built-in music playing app.

    Does not know how to use the Notes app.

    Does not know how to use the Files app.

    Did not know that the Files app can network to any computer.

    Thinks that Android is more secure than iOS.

    Thinks that every iOS update is the ENTIRE 10GB (or whatever size) iOS, even
    if just a single line of code was changed. Because he thinks that iOS is >>> monolithic. Nevermind that you can see the exact size of EVERY iOS update. >>> Which explains why x.0.0 versions take more time to DL/install than x.x.1 >>> versions.

    Thinks that all apps will stop working if you are not logged into the "Apple
    Mainframes".

    Common Knowledge. Its not what you know. Its what you THINK you know. >>>
    <https://www.youtube.com/watch?v=e0HGEZXTy8Y>

    Why do they Apple religious nutcases have to prove me right about them.
    Every time they post.
    I love the gracious way you acknowledge you were completely wrong when
    you claimed that under iOS you could "Probably not..." "save directly to
    the device outside of WhatsApp storage".

    Oh, right!

    You completely ignored the facts presented to you...

    ...again!

    Because IT is never wrong. Just ask IT and IT will tell you. Over and
    over.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Hank Rogers@Hank@nospam.invalid to alt.comp.os.windows-10,comp.sys.mac.system,misc.phone.mobile.iphone on Sat Oct 31 17:46:01 2026
    From Newsgroup: alt.comp.os.windows-10

    Alan wrote on 10/31/2026 4:38 PM:
    On 2026-10-29 19:57, Maria Sophia wrote:
    Nick Charles wrote:
    On Oct 29, 2026 at 4:13:05rC>PM EDT, "Alan" <nuh-uh@nope.com> wrote:

    On 2026-10-28 20:26, Maria Sophia wrote:

    I don't use WhatsApp on my iPads so I ask the iPhone users if the
    WhatsApp
    on iOS can save directly to the device outside of WhatsApp storage?

    Probably not...

    As usual, Arlen/Andy/Maria/(too many nyms to count) is wrong:

    A PDF file sent to me via WhatsApp.

    I open it to view it.

    Then use the Share icon (the ubiquitous square with the upward facing
    arrow)...

    ...and choose "File".

    It was easy.

    But!-a IT is a self-proclaimed EXPERT on iOS!!! Just ask IT and IT
    will tell
    you. Over and over.

    Nevermind that IT:

    Did not know that iOS has a built-in music playing app.

    Does not know how to use the Notes app.

    Does not know how to use the Files app.

    Did not know that the Files app can network to any computer.

    Thinks that Android is more secure than iOS.

    Thinks that every iOS update is the ENTIRE 10GB (or whatever size)
    iOS, even
    if just a single line of code was changed.-a Because he thinks that
    iOS is
    monolithic.-a Nevermind that you can see the exact size of EVERY iOS
    update.
    Which explains why x.0.0 versions take more time to DL/install than
    x.x.1
    versions.

    Thinks that all apps will stop working if you are not logged into the
    "Apple
    Mainframes".

    Common Knowledge.-a-a Its not what you know.-a-a Its what you THINK you >>> know.

    <https://www.youtube.com/watch?v=e0HGEZXTy8Y>

    Why do they Apple religious nutcases have to prove me right about them.
    Every time they post.
    I love the gracious way you acknowledge you were completely wrong when
    you claimed that under iOS you could "Probably not..." "save directly to
    the device outside of WhatsApp storage".

    Oh, right!

    You completely ignored the facts presented to you...

    ...again!

    Poor Arlen will never understand the core apple cult. It works well for
    us members, but not others. They are outsiders. We should pity them.


    --- Synchronet 3.22a-Linux NewsLink 1.2