• AuroraBorealis@pawb.social
    link
    fedilink
    arrow-up
    16
    arrow-down
    4
    ·
    1 year ago

    This is probably a result of that dumb crypto currency that uses proof of storage and people were just using Dropbox for it

    • Moonrise2473@feddit.it
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      But I wonder: doesn’t it need to be accessible to be read locally? If I mine like 1 petabytes of stuff, then I can upload somewhere else and forget about it?

      Otherwise they could mine on a disk, then wipe, start again.

      IMHO they found a scapegoat, everyone (me included) loves to blame crypto bros for anything bad, but I don’t see how here can happen

      • thews@lemmy.world
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        1 year ago

        Emulate a block device and reference it to the cloud api, unless im missing something.

        • Moonrise2473@feddit.it
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          Yes but it should be needed to read it constantly, otherwise it would download petabytes of stuff

          And that mined file would be accessed slowly

    • notnotapotato@lemmy.world
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      1 year ago

      That’s… Not how that works?.. You just need to show you have physical hard drive space on your computer. Dropbox doesn’t magically give you extra storage…

      • rastilin@kbin.social
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        There was an API floating around ages ago that let you mount a Gmail instance as a virtual hard drive and use it like block device. Dropbox does have an API for file access, so it’s entirely possible to write a miner that talks to Dropbox and not your local drive.