• unknowing8343@discuss.tchncs.de
    link
    fedilink
    arrow-up
    79
    ·
    5 months ago

    Don’t worry, they’ll kill the project after naming it Chrome Recall, Google Recall, Google Watcher, GWatch (with chat), Chat&Watch, Google Watch (new) in the span of a year.

    • Zorsith@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      1
      ·
      5 months ago

      Nah, they’ll kill it after a year due to hard drive costs. Enough screenshots at a resolution high enough to know wtf you’re looking at and still have vaguely usable data would be absurd.

      I could see it rebranded for enterprise usage for businesses and schools though, at an extra cost.

      • TheAnonymouseJoker@lemmy.ml
        link
        fedilink
        arrow-up
        4
        ·
        5 months ago

        If they compress screenshots like Microsoft does, or like Instagram does (73% quality JPG), they can store 4 screenshots in the space of a regular 100% quality JPG, which means 90-100 KB per. Assuming a screenshot every 10 minutes, in a span of 8 hour computing per day, each day takes up a mere 5 MB. This is close to what SOG/Mutahar demonstrated on YouTube recently, 8 MB per day. A month of screenshots is merely 250 MB. And this does not even account for MS having a LLM model to sort through screenshots and discard useless ones, which might give roughly 30% more efficiency. We are looking at about 1.2 GB storage for 6 months of screenshots.

        Recall allocates 25 GB on 256 GB storage, so that is 10 years of screenshots. If MS decides they can ramp up speed of screenshots and grab even more information.