• circuscritic@lemmy.ca
    link
    fedilink
    English
    arrow-up
    93
    arrow-down
    1
    ·
    9 months ago

    This is actually hilarious, in a very dark tragic comedy sort of way.

    The feature scans and categorizes important documents e.g. passports, IDs, etc., and it’s a feature of Google’s official Files app.

    Instead of dropping support and phasing it out, they’re going to kill it and DELETE all of those critical documents for users.

    JFC. Awesome.

    • Carighan Maconar@lemmy.world
      link
      fedilink
      English
      arrow-up
      36
      ·
      9 months ago

      Note that this is only about the copy made into the important tab. I do still agree it’s a stupid way if doing it, but they’re not deleting the original that was imported, just the import-copy.

      • narrowide96lochkreis@lemmy.world
        link
        fedilink
        English
        arrow-up
        25
        arrow-down
        1
        ·
        9 months ago

        Could it happen that you already deleted the original file because you thought, well I have it in the important tab, but now will lose that copy when Google removes that tab and be left empty handed? Not sure how this tab works

    • AwkwardLookMonkeyPuppet@lemmy.world
      link
      fedilink
      English
      arrow-up
      12
      arrow-down
      1
      ·
      9 months ago

      Google: hey, let us scan all of your most important documents. We’ll mark them as important for you.

      You: um… Okay. I guess that could be useful. I just hope you don’t record all of that information.

      Google: okay, we recorded all of your most important documents, so now we’re deleting them. Ta ta!

  • lemmylommy@lemmy.world
    link
    fedilink
    English
    arrow-up
    12
    ·
    9 months ago

    Why delete them, though? Just create a new folder „files previously in Important“ and move them there.

    • voxel@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      9 months ago

      probably don’t want to accidentally create an attack surface by dumping previously encrypted sensitive files into unencryped storage at a known location